Impinj FAQs

Overview

Impinj offers the followingproduct warranty options:

Initial Limited Hardware Warranty

Extended Warranty

Firmware Updates

Limited Hardware Warranty and Disclaimer

Impinj warrants to Buyer that the Impinj product hardware will substantially conform to Impinjs then-current published specifications for such product hardware. This limited warranty lasts:

(a) 1 year from the date of shipment to Buyer for finished semiconductor products (including but not limited to chips, inlays or inlets), but in no event for more than 15 months from the date of shipment by Impinj;

(b) 180 days from the date of shipment by Impinj for products sold in die or wafer form (excluding die adhesion claims) provided Buyer performs incoming inspections specified by Impinj; otherwise, 90 days;

(c) 90 days from the date of shipment by Impinj for products sold in die or wafer form with respect to claims related to die adhesion on the wafer carrier tape;

(d) 90 days from the date of shipment to Buyer for cables, power supplies, antennas and other accessories provided as part of or that work with an Impinj RFID reader product (excluding any software), but in no event for more than 6 months from the date of shipment by Impinj; and

(e) 1 year from the date of shipment to Buyer for all other portions of an Impinj RFID reader product, but in no event for more than 15 months from the date of shipment by Impinj.

A Buyer for a finished semiconductor product and products sold in die or wafer form is defined as an OEM who purchases directly from Impinj or indirectly through an authorized Impinj distributor. A Buyer for Impinj RFID reader products and accessories is defined as an end user who purchases directly from Impinj or a reseller/OEM who purchases directly from Impinj or indirectly through an authorized Impinj distributor. The date of shipment by Impinj is set forth on the packaging material in which the Impinj product is shipped. This limited warranty extends only to Buyer, except that a reseller/OEM purchasing an Impinj RFID reader product or accessory may pass through this limited warranty to its direct end user customer of the product or accessory (with the shipment date to Buyer corresponding to the shipment date to reseller/OEM).

Download the Initial Limited Hardware Warranty terms and conditions for details.

Extended Warranty

The Extended Warranty extends the limited hardware warranty for one (1), two (2), or three (3) years after expiration of the Initial Limited Hardware Warranty. Warranty benefits include access to major and minor firmware maintenance releases.

Download the Extended Warranty terms and conditions for details.

Firmware Updates

Octane firmware updates for all Speedway readers and gateways for one (1) year. Purchase this for continued firmware updates after the hardware warranty has expired.

Download the Firmware Update terms and conditions for details.

Ordering Information

An Extended Warranty must be purchased 90 days prior to the expiration of the Initial Limited Hardware Warranty. Extended Warranty will apply to a specific reader and is not transferable to other readers.

The extended warranty is only offered on Impinj reader and gateway products. It is not available for finished semiconductor products, products sold in die or wafer form, or cables, power supplies, antennas and other accessories.

The firmware-only upgrade takes advantage of product enhancements and stability improvements. The firmware-only offer provides Octane firmware updates for one (1) year and should be purchased only after the product warranty has expired.

SKU

Description

IPJ-C2011

Warranty Extension - Speedway Readers - 1-Year

IPJ-C2012

Warranty Extension - Speedway Readers - 2-Year

IPJ-C2013

Warranty Extension - Speedway Readers - 3-Year

IPJ-C2021

Warranty Extension - xPortal Gateway - 1-Year

IPJ-C2022

Warranty Extension - xPortal Gateway - 2-Year

IPJ-C2023

Warranty Extension - xPortal Gateway - 3-Year

IPJ-C2031

Warranty Extension - xSpan Gateway - 1-Year

IPJ-C2032

Warranty Extension - xSpan Gateway - 2-Year

IPJ-C2033

Warranty Extension - xSpan Gateway - 3-Year

IPJ-C2041

Warranty Extension - xArray Gateway - 1-Year

IPJ-C2042

Warranty Extension - xArray Gateway - 2-Year

IPJ-C2043

Warranty Extension - xArray Gateway - 3-Year

IPJ-C2001

Firmware Updates - All Products - 1-Year

Download Impinj M730 & M750 Product Brief

Download Impinj M730 & M750 Datasheet

Impinj M700 series RAIN RFID tag chips provide high performance, fast inventory capability, and advanced features for next-generation, universal RAIN RFID tags. The Impinj M700 series of performance endpoint ICs, containing the Impinj M730 and M750 tag chips, can be attached to or embedded in nearly any item, globally, to enable solutions for high-speed inventory counting, loss prevention with frictionless self-checkout, and embedded tagging with seamless product returns.

This article describes what to do when configuring Impinj Speedway Connect on-reader software including hardware setup and software installation. Impinj Speedway Connect is compatible with Impinj Speedway RAIN RFID readers (R120, R220, R420) and also with the Impinj xArray RAIN RFID gateway, Impinj xSpan RAIN RFID gateway, and Impinj xPortal RAIN RFID gateway.

Step 1) Start by setting up your Speedway reader or Impinj gateway hardware

Speedway (R120/22/420) and xPortal

xArray and xSpan

Attach antennas to the Speedway reader as desired. Take care not to cross thread the antenna cable.

Connect the Speedway reader to a PC either directly or via router or switch using a standard Ethernet cable (no crossover required).

(Optional) Connect USB host-to-device cable and/or RS-232 cable between Speedway reader and PC

The flat USB Host end will connect to the PC.

The more square USB device end will connect to the USB Device port on the Speedway reader.

RS-232 pins are located on the Speedway readers 15 pin GPIO port. See the SpeedwayR Installation and Operations Guide for details on the GPIO port.

Pin 2 Receive

Pin 3 Transmit

Pin 7 - Ground

Connect power to the Speedway reader and wait for the Speedway reader to boot. (~90 sec).Use AC Adapter or PoE.

here Speedway reader's Ports

Connect the Impinj xSpan or Impinj xArray to a PC either directly or via router or switch using a standard Ethernet cable (no crossover required).

(Optional)Connect USB host-to-device cable and/or RS-232 cable between the gateway and PC

The flat USB Host end will connect to the PC.

The more square USB device end will connect to the USB Device port on the Impinj gateway.

Connect AC Adapter or PoE to the Impinj gateway and wait for it to boot. (~90 sec).

xArray's Ports

xSpan's Ports

Step 2) Load Impinj Speedway Connect on your Speedway reader or Impinj gateway

If you received Impinj Speedway Connect in a .upg file format, simply load it on the Speedway reader or Impinj gateway in the exact same way firmware is loaded. Please upgrade to the latest firmware version before installing. Firmware upgrade files are available from your Impinj authorized partner and are very easy to load using the Speedway reader's or the Impinj gateway's WebUI (http://speedwayr-xx-xx-xx, http://xarray-xx-xx-xx,http://xspan-xx-xx-xx, etc.).

When Impinj Speedway Connect is successfullyinstalled, the Speedway reader's or the Impinj gateway's WebUI will display 'Application SW Version' information.

Follow the links to get more information on connecting to the Speedway reader and using the WebUI to upgrade firmware.

For more advanced installation/upgrade option for Impinj Speedway Connect, click .

Step 3) Configure the Speedway reader and/or Impinj gateway and start reading tags

If the Speedway reader or Impinj gateway is connected via a router, point your PC web browser to:

Impinj Product

URL

Impinj Speedway reader

https://speedwayr-xx-xx-xxor https://<IPaddress>

Impinj xPortal gateway

https://speedwayr-xx-xx-xxor https://<IP address>

Impinj xArray gateway

https://xarray-xx-xx-xxor https://<IPaddress>

Impinj xSpan gateway

https://xspan-xx-xx-xxor https://<IPaddress>

Note 1: In the above table, "xx-xx-xx" are the last 6 characters of the MAC address of your device.

If the Speedway reader or Impinj gateway is connected directly to the PC, point your PC web browser to:

Impinj Product

URL

Impinj Speedway reader

https://speedwayr-xx-xx-xx.local or https://<IPaddress>

Impinj xPortal gateway

https://speedwayr-xx-xx-xx.local orhttps://<IP address>

Impinj xArray gateway

https://xarray-xx-xx-xx.local orhttps://<IPaddress>

Impinj xSpan gateway

https://xspan-xx-xx-xx.local orhttps://<IPaddress>

Note 2: In the above table, "xx-xx-xx" are the last 6 characters of the MAC address of your device.

Note 3: Web browsers supported are: Chrome, Firefox, and Edge.

As an example, if connecting to the Speedway reader with a MAC address of 00:16:25:10:54:F9 on the network, the URL to enter in your web browser would be:https://speedwayr-10-54-f9

Be sure to use the HTTPS (secure HTTP), not HTTP.

A warning message may appear as shown below:(Exact message and continue option will vary depending on the web browser. In the above case, click "Advanced, then click Proceed...option)

Enter the user name and password. The default is:

Username: root

Password: impinj

Configure the Impinj Speedway Connect as desired.

Enter the license key if available and click [Save]. The license keys are loaded in the "Speedway Connect Administration" section of the Speedway Connect configuration page.If you need a license key for Impinj Speedway Connect 2.X, please purchase SKUIPJ-S4001.

TheImpinj Speedway Connect will start running after the [Save] button is clicked. Once configured, the Speedway reader does notneed to remain connected to the Ethernet network unless it is sending tag data out that port.

Speedway Connect Configuration Page

For help on specific features of the Impinj Speedway Connect, click on the question mark icons along the right side of the Speedway Connect configuration page.

Demo Mode or Use of License Key

Impinj Speedway Connect, downloadable from impinj.support.com is a fully functional "demo" version. This software will only run for 500 tag reports without a license key and then the program is disabled. To continue to use Impinj Speedway Connect in this mode, you can go to the Speedway Connect configuration page on the reader or gateway and click "Save". This will provide an additional 500 tag reports.

Once you are ready to use Impinj Speedway Connect (SKUIPJ-S4001)in an uninterrupted (non-demo) mode, you will need to purchase a Speedway Connect license from your authorized Impinj reseller or distributor. They willprovide you with a license key (one key is required per Speedway reader). Each Speedway reader must have its own unique license key (which is based on the Speedway reader's serial number) loaded in the Speedway Connect configuration page.

The license key does not persist if a new version of Speedway Connect is installed so it isvery importantto save the license key in a safe place.

The Octane ETK is a bundle of libraries, tools, and examples for creating an embedded application on Impinj Speedway Revolution readers and gateways. Development is supported with Ubuntu Operating System version 14.04 and 16.04*. The documentation and training videos we provide explain how to setup this environment, cross compile libraries for the ARM processor **, and use VSCode to perform remote debugging **.

* - Ubuntu 16.04 will require you to downgrade gnu tools to version 4.8 ** - Training Videos Only

Download Octane Embedded Tool Kit (ETK)

[MD5/SHA-1 Checksums]

Documentation:

Latest Released Version: 6.0.0

Recommended Reader / Gateway Firmware Version: - Octane FW 6.0.0 or later : Download Here (For Impinj Partners)

Development Environment: Ubuntu 14.04 / 16.04 (64-bit recommended)

Download Files Contain: - Cross-compiler Toolchain (ARM and x86) - Cap File Generator Tool - File System Image from Directory Tool - Kernel Headers - Cap File for Enabling Ftp and System Shell - Tag Reading Example - Makefile to Build the Example

Gnu Toolchain: 4.8

Embedded Developers Guide

Instructions for Development Environment Setup: - Read this article and/or watch the Training Videos

Octane ETK Training Videos (For Impinj Partners) cover: - An overview of Octane ETK Development - How to install an Ubuntu 16.04 environment for Octane ETK Development - How to install the Octane ETK tools and sample - How to run the Octane ETK Sample application on an Impinj reader or gateway - How to remotely debug the Octane ETK Sample from the Ubuntu 16.04 host using VSCode. - How to cross compile other libraries and applications to use in your application.

Sample Application

The Octane Embedded Development Tools provided in the Downloads section above contains a sample application that will show how to read tags. The following output is what should be seen when tags are in the Field of View:

Tag report ----------------------------------- Antenna ID : 1 EPC : 3008-33B2-DDD9-0140-0000-0006 Timestamp : 1419097603747553 Peak RSSI : -41 FastID : E28011052000205CDEAF0000 TID : 1020E280 User memory (Word 0) : ABCD

Recommended Development

We recommend you do most of your development and debug on the host PC, rather than cross-compiling your application and transferring it to the reader every time. This will allow you to develop applications much quicker using a debugger of your choosing. You can periodically transfer your application to the reader for performance testing or final deployment via FTP or CAP installation.

Setting Up ETK Development Environment

Run these commands to set up your Linux development environment. NOTE: We test with Ubuntu 14.04.

sudo apt-get updatesudo apt-get install g++-multilib g++-4.8-multilibsudo apt-get install lib32z1sudo apt-get install libc6:i386sudo apt-get install libc6-dev-i386sudo apt-get install libssl-dev:i386sudo apt-get install build-essentialln -s /usr/bin/g++-4.8 /usr/bin/g++

Installing an FTP client

Most Linux distributions include a command line FTP client by default.

If you would rather use a graphical FTP client, you can install gFTP using your package manager.

The following is the command for Debian and Ubuntu distributions:

sudo apt-get updatesudo apt-get install gftp

GNU Toolchain Installation Instructions

If your Linux machine doesnt have the GNU toolchain (gcc compiler) installed, you should do so using your distributions package manager.

The following is the command for Debian and Ubuntu:

sudo apt-get updatesudo apt-get install build-essential

Installing the ARM cross-compiler toolchain

To start installing the Octane Embedded Toolkit, unzip the download and ensure the following two files are in your HOME directory

octane_etk-5.12.0.240.tar.gz (file names will change with version)

octane_etk_sample-5.12.0.240.tar.gz (file names will change with version)

Extract the Speedway Revolution Embedded Development Tools (octane_etk-5.12.0.240.tar.gz) to a directory (~/) on your computer.

cd ~

tar xvfz ~/octane_etk-5.12.0.240.tar.gz

The above commandswill extract the contents of the file into directory octane_etk-5.12.0.240.

For the purposes of this tutorial, we will assume the directory is beneath your home directory (~/octane_etk-5.12.0.240).

Note: If using an ETK version prior to 6.0, then you will need to unpack the arm-toolchain using the steps below. If using version 6.0 or later, you should be okay to skip to the PATH change in the next section, as the arm-toolchain is already unpacked.

cd octane_etk-5.12.0.240 tar xvf arm-2013.11-33-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2ln -s arm-2013.11 arm-toolchain

The abovecommands will extract the arm toolchain into the directory "octane_etk-5.12.0.240".

It is now time to update your system PATH either in ~/.bash_profile (or .profile on Ubuntu or .bashrc on other flavors of unix) or on the command line prior to compilation to include the following folders:

~/octane_etk-5.12.0.240

~/octane_etk-5.12.0.240/arm-toolchain/bin

~/octane_etk_sample-5.12.0.240

PATH=$PATH:$HOME/octane_etk-5.12.0.240:$HOME/octane_etk-5.12.0.240/arm-toolchain/bin:$HOME/octane_etk_sample-5.12.0.240

You may need to re-login for this change to take effect.

Verify the PATH is updated properly with the following command:

echo $PATH-or-which arm-none-linux-gnueabi-gcc

Installing the Sample Application and LTK Libraries

Extract the Speedway Revolution Embedded Development Tools sample (octane_etk_sample-5.12.0.240.tar.gz) to a directory (~/) on your computer.

cd ~tar xvfz ~/octane_etk_sample-5.12.0.240.tar.gz

This will extract the contents of the file into directory octane_etk_sample-5.12.0.240.

For the purposes of this tutorial, we will assume the directory is beneath your home directory (~/octane_etk_sample-5.12.0.240).

The sample application is configured for a four port reader (R420, xPortal).

Note: If you are using a reader with a different number of antenna ports (R220, Antenna Hub) please change the NUM_ANTENNAS constant in the example source code file (speedway_embedded_example.cpp).

The Sample Application has a versionof the C++ LTK libraries stored in directories ~/octane_etk_sample-5.12.0.240/lib (.a object files) and ~/octane_etk_sample-5.12.0.240/include (.h headers).

The ~/octane_etk_sample-5.12.0.240/lib folder should contain the following files:

libcrypto_atmel.a

libdl_atmel.a

libltkcpp_atmel.a

libltkcppimpinj_atmel.a

libltkcppimpinj_x86_64.a

libltkcppimpinj_x86.a

libltkcpp_x86_64.a

libltkcpp_x86.a

libssl_atmel.a

libxml2_atmel.a

libxml2_x86_64.a

libxml2_x86.a

The ~/octane_etk_sample-5.12.0.240/include folder should contain the following files:

impinj_ltkcpp.h

ltkcpp_base.h

ltkcpp_connection.h

ltkcpp_frame.h

ltkcpp.h

ltkcpp_platform.h

ltkcpp_xmltext.h

out_impinj_ltkcpp.h

out_ltkcpp.h

version.inc

The version.inc file has the version of the ltk installed. It should indicate "10.26.1".

Building the Sample Application

Switch to the ~octane_etk_sample-5.12.0.240 directory:

cd ~/octane_etk_sample-5.12.0.240

The included makefile can build three different targets:

x86 (host PC)

ARM (Speedway Revolution)

CAP (loader for Speedway Revolution)

To clean your folder you can type:

make clean

To build both the x86 and arm executable, type:

make

To build just the x86 version, type:

make x86

To build an ARM executable that can run directly on Speedway Revolution, type:

make arm

Building these two targets will create the following files

~/octane_etk_sample-5.12.0.240/bin/speedwayr_arm

~/octane_etk_sample-5.12.0.240/bin/speedwayr_x86

To have your program start automatically after reboot on a reader, rename the application (e.g. speedwayr_arm) to a file named start.

Note: The reader will execute file '/cust/start' from the root folder '/'. Please create a script that changes to the appropriate folder and then calls your application referring to relative files.

Note: Please disregard the following warning messages: lib/libcrypto_atmel.a(dso_dlfcn.o): In function `dlfcn_globallookup': (.text+0x10): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking lib/libcrypto_atmel.a(b_sock.o): In function `BIO_get_host_ip': (.text+0x10c): warning: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking lib/libcrypto_atmel.a(b_sock.o): In function `BIO_get_port': (.text+0x290): warning: Using 'getservbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

To build the CAP, copy the binary over to the CAP folder:

cp ~/octane_etk_sample-5.12.0.240/bin/speedwayr_arm ~/octane_etk_sample-5.12.0.240/cap/

To create the CAP with the arm version of the app (~/octane_etk_sample-5.12.0.240/speedwayr_cap.upg), type:

cd ~/octane_etk_sample-5.12.0.240make cap

Executing the Host PC Sample Application

Switch to the ~/octane_etk_sample-5.12.0.240 directory (if not already there)

cd ~/octane_etk_sample-5.12.0.240

Execute the Host PC Sample Application against a target reader (<reader_address>):

bin/speedwayr_x86 <reader_address>

Replace <reader_address> with either the ip address or hostname of the reader you want to read from.

The output should look similar to the following if tags are in the Field of View:

Tag report ----------------------------------- Antenna ID : 1 EPC : 3008-33B2-DDD9-0140-0000-0006 Timestamp : 1419097603747553 Peak RSSI : -41 FastID : E28011052000205CDEAF0000 TID : 1020E280 User memory (Word 0) : ABCD

Tag report ----------------------------------- Antenna ID : 1 EPC : 3008-33B2-DDD9-0140-0000-696E Timestamp : 1419097603775686 Peak RSSI : -38 FastID : E280110520002556DE920000 TID : 1020E280 User memory (Word 0) : ABCD

Press Ctrl + C to stop running the sample application.

Reader Deployment Options

When you are ready to deploy the sample solution to the reader, there are several files that should be copied over at a minimum:

bin/speedway_arm

cap/sys/reader.conf

The files must be placed beneath the /cust folder on the reader:

/cust/speedway_arm

/cust/sys/reader.conf

Refer to the Impinj Reader and Gateway Embedded Developers Guide to learn more about the contents of the reader.conf file.

The sample application sets the Linux shell (named OSShell) password to "developer" and starts the FTP server.

Please disable these features for a production application if your application does not require them.

There are two ways the application can be deployed to one or more readers.

FTP the application to the reader once the reader FTP and OSShell are enabled.

Create a CAP file for multiple reader deployment.

Enabling FTP and OSShell on the Reader

OSShell and FTP access are disabled by default on Speedway Revolution.

To enable these features, you can do one of the following:

Create a Custom Application Partition (CAP) image.

Use the pre-built CAP file (see below for accessing "~/octane_etk_sample-5.12.0.240/cap") that is included with the Speedway Revolution embedded development tools.

(FTP only) Connect to RShell by SSH'ing to the reader and issuing the command:

config network ftp enable

Installing a CAP File On the Reader via Web UI

You can load the pre-built (or any other) CAP file on to the reader by opening up a web browser and navigating to the following URL:

http://<reader_address>/

(<reader_address> should be replaced with the actual reader hostname or ip address. E.g. http://speedwayr-10-25-32 )

You will be prompted to login. The default login information is:

Username: root

Password: impinj

Click the Browse button (next to the "Select Upgrade File") and select the pre-built CAP file (or any other one you just created).

Click the Upgrade button.

Wait until the 'Reboot Status' indicator on the Web UI reads Ready to Reboot.

Click the reboot button to restart the reader.

Once the reader reboots, system shell and FTP access will be enabled.

FTP the Application to the Reader

To have your program start automatically rename it to a file named start so that it will reside as file "/cust/start" on the reader.

Using an FTP client, connect to the reader using its IP address or hostname.

ftp <reader_address>

(<reader_address> should be replaced with the actual reader hostname or ip address. E.g. http://speedwayr-10-25-32 )

You will be prompted to login (Default username is root and password impinj)

Once connected, navigate to folder /cust and binary transfer the executables there.

cd /cust

bin

put bin/speedwayr_armmkdir syscd sysput cap/sys/reader.conf

Building a CAP (Installation) File

If you would like to deploy your application across multiple readers, you can create an installation file, also known as a CAP file.

Creating a CAP file will take care of creating directories and copying all the files for your application over to the reader.

First, create a working directory to build the CAP file in.

The sample application already has a cap folder (~/octane_etk_sample-5.12.0.240/cap).

You can put the CAP files wherever you like.

Update the ~/octane_etk_sample-5.12.0.240/cap_description.in file with the following contents:

# CAP Description File # This file contains the settings used by the CAP generation tool # when a CAP partition upgrade file is produced. [Description] # Version is a 4 part number in decimal with each part limited to # 0-255. It is the version of the CAP to be generated. Version = 1.0.0.0 # Valid Reader Hardware is a 3 part number in decimal representing # the reader model and major/minor revisions on which the CAP may be # loaded. Each field may be replaced by a '*' to mean 'all'. # Format = aaa.bbb.ccc # aaa - Model number # bbb - Major revision # ccc - Minor revision Valid Reader Hardware = 240-*-* Valid Reader Hardware = 250-*-* Valid Reader Hardware = 260-*-* Valid Reader Hardware = 270-*-* # File System Layout is a value used by the reader to determine how # the CAP partition should be loaded to flash. Currently the only # supported layout version is 10. File System Layout = 10 # All the files in this directory will be loaded on the reader under /cust. # Specify this directory using an absolute path. Input Directory = /home/notroot/cap/input

Modify the entries above to suit your needs.

E.g. Change the version number that shows up on the reader's web UI.

Now copy all of your application files to the cap directory (~/octane_etk_sample-5.12.0.240/cap)

cd ~/octane_etk_sample-5.12.0.240/capchmod a+rx ~/octane_etk_sample-5.12.0.240/bin/speedwayr_arm

cp ~/octane_etk_sample-5.12.0.240/bin/speedwayr_arm .

Change the "." to "start" in the line above if you want this program to start immediately after a reader reboot.

Execute the following to generate the "speedwayr_cap.upg" CAP file:

cd ~/octane_etk_sample-5.12.0.240/make cap

Now that you have created the CAP file (~/octane_etk_sample-5.12.0.240/speedwayr_cap.upg), you can load it on to the reader.

Follow the instructions in section Installing a CAP File On the Reader above for installing this CAP file on the reader.

Please refer to the Firmware_Upgrade_Reference_Manual.pdf file in the Octane Documentation suite for how to upgrade multiple readers simultaneously using a single CAP file.

Your application should start once the reader has finished rebooting if you named it start, otherwise follow the instructions below for running the application manually.

Running the Application Manually

Open up RShell by connecting to the reader via ssh.

The default user name is "root" and the default password is 'impinj".

At the RShell prompt, enter the following command to open a system shell:

osshell developer

From the Linux shell prompt, you can navigate to /cust and execute your application.

cd /cust

chmod a+rx speedwayr_arm

./speedwayr_arm

The output should look something like:

Tag report ----------------------------------- Antenna ID : 1 EPC : 3008-33B2-DDD9-0140-0000-0006 Timestamp : 1419097603747553 Peak RSSI : -41 FastID : E28011052000205CDEAF0000 TID : 1020E280 User memory (Word 0) : ABCD

Tag report ----------------------------------- Antenna ID : 1 EPC : 3008-33B2-DDD9-0140-0000-696E Timestamp : 1419097603775686 Peak RSSI : -38 FastID : E280110520002556DE920000 TID : 1020E280 User memory (Word 0) : ABCD

Impinj announced the end of support and availability for our MultiReader software on July 2, 2018. It is no longer available for download from the Impinj http://support.impinj.com website and our support team will stop assisting with any issues this software contains.

Additionally, we will not be releasing any new versions of MultiReader.

We recommend customers migrate or begin using our ItemTest software, available for download here. We have also created a document to aid customers switching from MultiReader to ItemTest available for download here and on the ItemTest download page.

If you have any questions please contact our Support team ( mailto:[email protected] ).

Impinjs Speedway fixed RFID readers deliver the performance, quality and reliability thatis necessary to ensure visibility for your business. With the largest installed base of fixedreaders across a diverse range of applications, high mean time between failure, and asuite of supporting productsand tools, you can count onSpeedway readers gatheringthe data you need.

Download Speedway Family Product Brief

Download Speedway Family Datasheet

Supported Regions or Geographies

If you are experiencing problems with your Impinj RAIN RFID reader or gateway and are having difficulty pinpointing the cause, it is often useful to return the Impinj reader/gateway to a known state (in this case, the factory default configuration) and try again.There are two ways to return the Impinj reader/gateway to its factory default configuration - issuing an Rshell command or pushing the Factory Default Reset (FDR) button on the device itself. This article addresses using both approaches.

One use-case where it may be necessary to return the Impinj reader/gateway to the factory default configuration is if someone has set a static IP address on the device which you are unaware of. In this situation, you would want to perform a factory configuration reset to force the reader's networking to be switched from 'static' to 'DHCP' as this will cause the reader to obtain an available IP address automatically on startup. When using an Impinj reader, you can then connect using thespeedwayr-xx-yy-zz.localalias (where xx-yy-zz are the last three octets, or groups of numbers, in the MAC address of the Impinj reader). If using an xSpan or xArray, you would use the xarray-xx-yy-zz.local or xspan-xx-yy-zz.local alias instead.

Since DHCP is the default setting of the Impinj readers, performing a factory reset will enable this mode.

When performing the factory configuration restore through the physical FDR button, please note a few key points illustrated in this video.

Be sure to be pressing the FDR button with the power unplugged and continue to do so while plugging in power to the Impinj reader or gateway

Timing is important - be sure to release the FDR button when the power light blinks red, after about 3 seconds (seen at 1:25 in the video).

If the status light blinks alternately between green and red before going solid green, then you have performed the reset successfully. If it goes solid green without blinking, then the reset was not successful (most likely the FDR button was released too soon).

Warning!Pressing the FDR button for longer than 3 seconds can cause a factory default restore to occur. Unlike a factory configuration restore, the factory default restore removes the Speedway readers custom application partition (CAP), if one exists, returning the unit to its state as shipped from the factory. Although there may be situations in which this removal is necessary, its important to avoid accidentally removing the CAP.

The second approach for restoring the Impinj reader's default settings is through issuing an RShell command. This command will cause a factory configuration restore. Once logged into the RShell terminal, you will want to issue the following command:config image defaultThe config image default command restores the configuration to the default settings. Whencomplete, the command is automatically followed by a reboot. It's important to note that running this command will not uninstall any custom application installed on the reader. The custom application (if installed) is notified after the reboot, so that configuration specific to the custom application (if any) can also be restored to the defaults. This command takes no additional parameters.If looking to also uninstall the custom application through RShell, the following RShell command can perform this: config image removecap

Note:When factory resetting an Impinj xArray or Impinj xSpan, it can be difficult to follow the procedure for pressing the FDR button, as you aren't able to see the front status lights of the reader to determine when to stop pressing the button. If unable to reset through RShell and require using the FDR button approach, we would suggest holding the reset button in, then plugging in the power, and continue holding the reset button for two minutes. After two minutes, the unit should be factory reset.

Impinj RAIN RFID Readers and Gateways can be configured using many settings to handle various use-cases. Two important configuration settings are "Session" and "Search Mode". Impinj software (e.g. ItemTest, ItemSense) and libraries (e.g. Octane SDK, LTK and Speedway Connect) allow you to change these settings. Here is an example of where these settings can be changed in ItemTest:

article

This article discusses more details about these two settings.

Sessions

The EPC GEN 2 standard allows for inventorying up to four sessions; these sessions serve two purposes:

Determines when a tag will respond to a query from the reader

Allows tags to maintain independent states when communicating with multiple readers at the same time.

As defined in the EPC Gen2 Standard, the session is an inventory process comprised of the reader and an associated tag population. The Impinj reader chooses one of four sessions and inventories tags within that session. The Impinj reader and tag population will operate in one and only one session for the duration of an inventory round.

The EPC GEN 2 compliant tag has two states for each session represented by Session Inventory Flags, 'A' and 'B'.

The tags will always power up into the 'A' state for each session. The Impinj reader controls when the tag will go from 'A' to 'B' state. Although the Impinj reader can control when the tag is moved back to the 'A' state, it is commonly controlled by what we call the tag's persistence.

Persistence

When the Impinj reader inventories a tag, the session flag state is changed from 'A' to 'B' - how long the tag stays in the 'B' state before reverting back to the 'A' state is called "persistence". It is important to realize that exact persistence times cannot be set by the user; they can only be approximated according to the Search Mode and Session. Below is a table from the EPC Gen2 Specification showing more details on the persistence period for each of the four sessions (denoted by their session flags as S0, S1, S2, and S3):

Next let's look at Search Modes and how they work with the Session setting to establish the persistence.

Search Modes

There are currently five search modes available on the Impinj readers:

Dual Target

Single Target

Single Target with Suppression (TagFocus)

Dual Target Select BA

Single Target Reset

Each of the modes contains the word "Target" in the name. "Target" refers to whether the reader will singulate (select) only tags that are in a single state, either 'A' or 'B' (Single Target) or if it will singulate tags in both 'A' and 'B' state (Dual Target). The following describes each of these modes in more detail. For this discussion, we are referencing a system using a single Impinj reader and a single antenna.

Dual Target:

In Dual Target the Impinj reader

Reads A tags one at a time and moves them into the B state.

Reads B tags one at a time and moves them into the A state

Repeats the above activities over and over.

In this search mode, the session has no influence as the Impinj reader will immediately 'push' tags back into the 'A' state.

Usage: Dual Target generates many reads and is good for small populations or static environments (i.e smart shelf), though Dual Target can also be used in dynamic environments. In dynamic environments, Dual Target can also be good at detecting when a tag enters, stays, and leaves the Field of View of the antenna. This dynamic use-case is also applicable with Dual Target Select B-> A as described in the next section.

Single Target:

In Single Target, the Impinj reader:

Reads A tags one at a time and moves them into the B state

Those tags will remain in the 'B' state depending on the persistence of the session used, before reverting back to the 'A' state.

Repeats the above two activities over and over

* - The amount of time that the tags stay in the 'B' state is based on the rules associated with the session configured. Refer to the "Putting It All Together" section below for further details on session configuration.

Usage: This mode is good for high population, dynamic environments where you only want to inventory the tag a single time when it enters the reader's field of view. It provides the deepest possible scan when there is a large tag population in a static environment.

Single Target with Suppression (TagFocus):

This search mode is exactly the same as Single Target, except provides the advantage of Sessions 2 and 3, in that the tag will remain quiet while in the read field once inventoried.

Usage: This allows other tags that might be quieter (not reflecting as much power) to be read.It also provides the advantage of Session 1 in that it will revert the tag almost immediately back to the A state and be available for a reader query upon leaving the read field.

Tag State Behavior

Before we continue with the remaining search modes, let's put what we've covered so far together to see the behavior these settings have.

Note: Single Target Session 0 may act differently than what is depicted above. Please read the section about Single Target Session 0 below for more details. In Dual Target, the tag will be read continuously regardless of tag state 'A' or 'B'; the Session setting has little to no influence.

In Single Target with Session set to '0', the tag will behave similarly to Dual Target, though the underlying process is a little bit different. The EPC GEN 2 standard defines Session 0 as having an indefinite TS0 value. The reason that this does not appear to be the case in the actual implementation of Single Target Session 0 on the Impinj reader is that the reader will channel hop. This will cause a new inventory of the tag on a different channel, starting the tag persistence over. This will result in multiple reads similar to Dual Target as shown in the diagram above. If you were to use a battery-assisted RFID tag, then using Single Target Session 0 would show the indefinite TS0 value, as described in the EPC Gen2 Standard, as the tag would never become de-energized, even while channel hopping.

As antenna/channel hopping requirements vary between regions, it's possible to see some odd behavior when operating in this configuration. An example of odd behavior is that tags can remain in state B for four seconds when performing inventory with an ETSI model of the Impinj reader. Due to this, we often recommend other search modes/sessions such as Single Target Session 1, or Dual Target B A Select (described in further detail in the next section).

In Single Target with Session set to '1' the tag will be read and then moved to the 'B' state. After some period of time (TS1) it will revert back to the 'A' state and be read again. This TS1 value is defined in the EPC GEN 2 standard as being between 500ms and 5 seconds; again it cannot be expressly set, only approximated. The TS1 value will vary depending on the tag IC manufacturer and even the specific tag IC model. For example, the Impinj Monza S1 persistence is approximately 1 second. So, if we set the reader for Single Target, Session 1, we will see the same Impinj Monza tag being read around every second; if a different tag IC model is used, the TS1 value may differ. If the Impinj reader Search Mode is set to Single Target and the Session to either '2' or '3' then the tag will be read once then switch to 'B' state and remain quiet the entire time it is in the read field.Once the tag leaves the read field, it will have a persistence (stay in the 'B' state) for a time period of TS2/3. This persistence time is defined by the EPC GEN 2 standard to be a minimum of 2 seconds with no maximum specified. Remember that during this time, the tag will not respond to a query from any reader using Single Target and the same Session. Using Single Target with Suppression (also known as "TagFocus") provides the advantage of Sessions 2 and 3 in that the tag will remain quiet while in the read field once inventoried thus allowing other tags which may be "quieter" (not reflecting as much power) to be read. It also provides the advantage of Session 1 in that it will revert almost immediately back to the 'A' state and be available for any reader query upon leaving the read field.

Note: Single Target Session 0 may act differently than what is depicted above. Please read the section about Single Target Session 0 above for more details.

One of the settings that is closely related to these two settings is the Reader Mode. If you are unfamiliar with the Reader Modes and would like to learn more, please read the following .

Remaining Search Modes

Dual Target Select B - > A:

In Dual Target Select B A, the Impinj reader

Reads all A tags one at a time and moves them into the B state.

Moves all B tags at once into the A state with a single GEN 2 Select command. The Select command communicates with all the tags in the field of the view.

Repeats the above two activities over and over

Using the select command to quickly change all of the tags to the 'A' state allows for faster and more efficient reading with multiple antenna configurations. The amount of time for sending the GEN 2 Select command is far shorter than performing the second inventory on each individual tag to change state from 'B' to 'A'. This causes the reader to switch antennas faster because the tags are back in the 'A' state earlier. When compared with standard Dual Target, you will see improvements in speed, as there is often time saved by performing the Select command rather than a second inventory.

It also allows for better handling of unique tags entering the field of view. In Dual Target, if a new 'A' tag was to enter the field of view and the Impinj reader was performing an inventory on the 'B' state, that tag would not be reported until the Impinj reader performs the next 'A' state inventory. With Dual Target Select B A, the tag would be reported sooner due to the reader skipping the 'B' state inventory.

Usage: We see this mode as most beneficial when there are repeated tag observations with multiple antennas or a medium to high tag count (>50 tags). Another useful use-case for this search mode is when monitoring moving tags to know more precisely when tags enter and exit the field of view from an antenna. An example of this is shipment verification.

Single Target Reset:When using this search mode, the Impinj reader inventories state 'B' tags and resets the tag's inventory flag back to state 'A'.

Consider using for high-throughput applications when you want to control when the tag goes back to state 'A'. For example, when your Impinj reader is configured with Single Target session 2 or 3 (which have long persistence decay periods), you can reconfigure the reader to use Single Target Reset to bring the tag back to state 'A' in a more controlled/timely fashion.This search mode enables the continuous reading of a large set of tags.

Usage: A pseudo-code sample to describe how you could use Single Target Reset in conjunction with Single Target to inventory continuously is shown below: While (true) {

Inventory SingleTarget and Session 2 for 10 seconds (A->B)

Inventory SingleTargetReset and Session 2 for 10 seconds (B->A)

SentLatestInventory(ListOfInventoriedTags)

}It's also possible to use Single Target Reset in conjunction with Single Target from two separate readers, rather than switching search modes on a single reader.

Examples

Scenario 1: There are a number of tagged items being continuously inventoried on a RFID-enabled "smart shelf". Selecting either of the Dual Target for the search mode will allow for the fastest update of tag status and be able to provide an update alert should a tagged item be put on, or taken off, the shelf.

Scenario 2: A fixed reader portal is performing an inventory on incoming items as they come off the delivery truck using Single Target, Session 2. Now, let's say you want to do a quick inventory sweep with a handheld reader (perhaps to encode the storage location). If the handheld reader uses the same session, it might miss some of the tags, or have a slow tag read rate, due to the fact that the tags were 'pushed' into the 'B' state by the fixed reader and have not yet flipped back to the 'A' state. Setting the handheld reader to a different Search Mode (i.e. Dual Target or Single Target w/ Suppression) or to Session 3, will allow the tagged items to be inventoried.

Another option would be to use Single Target with Suppression (assuming use of Impinj Monza tags) so that the large population of tags can be quickly inventoried with high probability of 100% count and still allow the tags to be re-inventoried almost immediately after leaving the portal read zone.

Scenario 3: Two Impinj readers want to simultaneously inventory a population of tags and then confirm they have the same count as a way of reducing missed tags. In this case, setting one reader to Single Target, Session 2 and the other to Single Target, Session 3 will allow this to happen. This is possible as the inventories are occurring on two separate sessions.

Scenario 4: You have a large tag population, and are trying to perform a continuous reading of these tags, while also utilizing session 2 and 3.Initially, the tags would be placed into the 'B' State through the Single Target inventory using Session 2 or 3. Then, by periodically changing the reader's search mode to "Single Target Reset" and performing an inventory, the tags would be changed back to the 'A' state, allowing them to be inventoried the next time the Single Target inventory is run. This allows the user to have better control of the frequency in which the tags are reported.

Scenario 5: You have a high throughput environment, where you need as many reads as possible. This could be either Inventory, Location, or Direction as there are applications requiring high throughput in each mode. In this case, you will want to implement the Dual Target BA search mode, as this mode can provide faster and more efficient reads than usual with Dual Target by sending a Select command, causing the tags to be reverted to state A for an even quicker inventory. This is faster than compared to just waiting for Dual Target to assign the tags back to state B by using a second inventory, therefore improving the overall read rate and the handling of new unique tags coming into the field of view.

The following methods are available for installing / upgrading Impinj Speedway Connect on-reader software:

1. Using the Web Management UI (Reader Web UI)

2. Automatically via Metafile

Install / Upgrade Impinj Speedway Connect software through the Impinj Management Web UI

Impinj Speedway RAIN RFID readers and gateways support installing / upgrading Impinj Speedway Connect software using the Impinj Management Web UI.

Connect to the Impinj reader/gateway using a web browser http://<reader hostname or IP address> Examples: http://speedwayr-10-00-dd.local/, http://xarray-11-00-dd.local, http://xspan-11-00-dd.local, orhttp://10.0.10.44

Log in to the reader.

Click the gray "Choose File" button and then select the Impinj Speedway Connect software .upg file.

Click the red Upgrade button.

After the upgrade is complete, click the red Reboot button.

Install / Upgrade Impinj Speedway Connect Software Automatically via Metafile

This is an automatic install / upgrade method that, after it has been configured, allows an Impinj reader or gateway to:

periodically retrieve an Install / Upgrade Configuration Metafile

determine from the configuration data if an install / upgrade needs to be performed

This mode also allows simultaneous installs / upgrades of Impinj Speedway Connect software through the use of a single Upgrade Configuration Metafile. For this method, the user creates a custom Upgrade Configuration Metafile (Metafile). The Metafile is stored on a remote server. The user configures the location of the Metafile as a URI. The Impinj reader or gateway downloads the Metafile at a configurable periodic interval, called the retrieve period. The Impinj reader then uses the content of the Metafile to make automatic install / upgrade decisions. The Impinj reader remembers the retrieve mode, retrieve period, and URI across power cycles. This allows the Impinj reader to resume the auto method after a system reboot. Typically, when the Impinj reader retrieves the Metafile, it finds that no install / upgrade is needed. In the absence of any Metafile changes on the server, the Impinj Speedway Connect software version that is running and the Metafile versions are the same.

Example of Metafile

- Installing / Upgrading Speedway Connect 2.6.0 on R420 - Auto retrieval period = 60 min - Metafile is stored on an HTTP serve at xxx.xxx.xxx.xxx as an example

reader-model: "Speedway R420" retrieve-mode:auto;retrieve-period=60 upgrade-mode:auto commit-mode:immediate img-type:10 upgrade-file-uri:"http://xxx.xxx.xxx.xxx/SpeedwayConnect-2.6.0.0.upg" partition:2;version="2.6.0.0"

You can simply copy the above, paste into Notepad, modify the URI according to your environment, save it as metafile.txt, and place it on a file server of your choice.

For more detail about this upgrade method, please consult the Firmware Upgrade Reference Manual available here.

Overview

The following tables provide additional detail on common messages you might receive when using Impinj Software.If you encounter an error message not listed on the following table please contact our support team.

If you use our ItemTest and Speedway Connect application(s), we put messages you might see in the table below.

Software Messages

Application

Version

Message

Meaning

Action to Take

*

*

A client initiated connection already exists

Another application is already connected to the reader on the configured LLRP port.

Please check the Web UI to determine from what machine the connection is happening from. If it shows "127.0.0.1" you will either need to disable or remove the embedded application (e.g. Speedway Connect) running on the reader.Otherwise a client application or ItemTest will need to be closed to release the LLRP connection.You might be able to get away with a reboot of the reader to relinquish the control.

*

*

Error connecting to the reader (<reader name>): Timeout.

Communication with the reader is down.

Please go through our Reader/Gateway Troubleshooting Connectivity Guide ( https://support.impinj.com/hc/en-us/articles/202756488-Troubleshooting-Reader-Connectivity-Issues )?

Overview

The following tables provide additional detail on common messages you might receive when using Impinj Software.If you encounter an error message not listed on the following table please contact our support team.

Follow the instructions in article How do I capture logging events from my reader? to determine how to acquire the logs from our Readers and Gateways. Some of the messages obtained could be explained using the table below.

Note: Benign messages should be disregarded since they have no impact on the operation of the reader.

Reader/Gateway System Logs:

Message

Meaning

Action to Take

MC4: Insufficient keepalives, closing connection

The application that connected to the reader/gateway setup keepalives and Link Monitor Mode. This message says the keepalives were not responded to by the connected application and the reader decided to close the LLRP (5084) connection.

Please check the connected application for why it did not respond to the reader's keepalive messages in time.

MC4: LLRP-OSM: Failed to validate ROSpec (-3177 - LLRP [420] : //RFTransmitter/TransmitPower : out-of-range)

The Transmit Power Index is out of range.

Please issue a Get Reader Capabilities call to find out what transmit powers (and indexes) are available for the reader you are connecting to. Using the values provided by the reader, please set the transmit power value (index) properly.

enableAdvancedGpo failed, LLRP [4697] : //ImpinjAdvancedGPOConfiguration/GPOPortNum : out-of-range

The Advanced GPO Setting is out of range.

Please set the Advanced GPO Setting to a valid value. Our readers only have 4 GPO ports: 1,2,3, and 4. Please set the port number to one of those.

mDNSResponder: mDNSPlatformSendUDP got error 101 (Network is unreachable) sending packet to xxx.xxx.xxx.xxx on interface yyy.yyy.yyy.yyy/eth0/2

Note: xxx.xxx.xxx.xxx and yyy.yyy.yyy.yyy both represent IP addresses reported by the reader.

The reader's DNS and/or DHCP settings are probably not setup correctly.

Please check the DNS and DHCP settings of the reader.Please check the DNS and DHCP servers to make sure they are setup correctly.

You can find the commands for DNS and DHCP reader operations here:

https://support.impinj.com/hc/en-us/articles/202756488-Troubleshooting-Reader-Connectivity-Issues

netconf: Failed to get OperatingRegion, using 1.3.6.1.4.1.25882.2.1.2.2 as sysObjId

The region has not been specified.

Please connect to the Reader's WebUI (http://<reader hostname or ip address>/), specify the region, and click Update Region.

https://support.impinj.com/hc/en-us/articles/115001233464-Speedway-Connect-Troubleshooting-Techniques

When instructed, click the "Reboot" link:

ntpd_intres[2780]: host name not found: xxxxx.xxx.xxx

Note: xxxxx.xxx.xxx represents some host the system is trying to access.

The reader's DNS and/or DHCP settings are probably not setup correctly.

Please check the DNS and DHCP settings of the reader.Please check the DNS and DHCP servers to make sure they are setup correctly.

You can find the commands for DNS and DHCP reader operations here:

https://support.impinj.com/hc/en-us/articles/202756488-Troubleshooting-Reader-Connectivity-Issues

A client initiated connection already exists

Another application is already connected to the reader on LLRP port 5084.

Please check the Web UI to determine from what machine the connection is happening from. If it shows "127.0.0.1" you will either need to disable or remove the embedded application (e.g. Speedway Connect) running on the reader.Otherwise a client application or ItemTest will need to be closed to release the LLRP connection.You might be able to get away with a reboot of the reader to relinquish the control.

vmunix: INFO: task bottlerocket:252 blocked for more than 120 seconds.'

The Octane Firmware is reporting Speedway Connect hasn't responded in more than 120 seconds.

Increase the logging levels on the reader to enable Speedway Connect to output where it is getting hung up. You can find the commands to do that here:

vmunix: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.'

This is a benign message.

Please disregard

MC4: MC starting'

This is a benign message.

Please disregard

thttpd[xxx]: bind 0.0.0.0 - Address already in use'

This is a benign message.

Please disregard

linkmonitor: Failed to start GPS data retrieval over ethernet: Status='"'"'7,Unsupported-Command'"'"''

This is a benign message.

Please disregard

MC4: Layer1: Unexpected FPGA timer expiry (non-critical)

This is a benign message.

Please disregard

Overview

Several customers have reported getting an unknown USB Input Device, Unknown Device, and/or Device not recognized error message when plugging an Impinj Device (reader or gateway) into the USB port of a Windows 10 machine.

[email protected]

Many of the issues can be addressed by the "Troubleshooting Readers Connectivity Issues" article. Inthis article we will provide additional troubleshooting steps to connect to an Impinj Reader via USB.

Troubleshooting Steps

#

Troubleshooting Steps

Details

1

Disable any security scanner software on your system

It is possible a security scanner or anti-virus software has disabled the USB port.

2

Check for Windows Updates

We have seen customers successfully connect via USB after Updating Windows.

3

Connect to a USB 2.0 port

On some PCs with USB 2.0 and 3.0 ports we have seen USB 2.0 ports work reliably.

4

Verify the USB port is working by plugging in a flash drive in that port.

Customers have reported that when they used a USB storage device, removed it, and plugged in the Impinj reader right after, the device manager will see the reader.

5

Disable Fast Startup

Some customers have resolved their USB issues by disabling Fast Startup.

6

Compare the files in your system to see if they match the ones on a working Windows 10 system:

Please download the WINDOWS.zip file, open it, and verify if any or all of these files exist on your system.The main two files to check are USBHUB3.SYS and USBPcap.sys. If these are different then it is likely these files that are preventing you from communicating with the reader via the USB drive:

The following controllers can be seen in the Device Manager for our systems that work:

7

Read and Implement solutions from searching online articles

As of 10/1/2019: We have done a search online for some possible solutions to windows 10 usb issues:

https://windowsreport.com/windows-10-doesnt-recognize-usb/

https://www.drivereasy.com/knowledge/fix-issue-after-upgrade-system-to-windows-10-usb-ports-dont-work/

https://www.reddit.com/r/Windows10/comments/3fnfy7/usb_devices_randomly_losing_connection/

https://h30434.www3.hp.com/t5/Notebook-Hardware-and-Upgrade-Questions/Fix-for-Unknown-USB-Device-Device-Descriptor-Request-Failed/td-p/5973953

https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware-winpc/the-usb-device-returned-an-invalid-usb/93f11e2d-5d63-496a-a323-66bdbfacf796

https://www.drivereasy.com/knowledge/solved-unknown-usb-device-device-descriptor-request-failed-for-windows-10/

https://www.diskgenius.com/how-to/unknown-USB-device-descriptor-request-failed.php

This is not an endorsement but rather a resources we found useful.

8

Try an alternative solution

If there is any option to drop the USB connection and use ethernet instead, you can directly connect the reader to the machine.

One could potentially write an adapter that takes input from the reader via ethernet and transmits it to the target application via keyboard input.

If these steps did not work for you, please submit a support ticket. Make sure to include as much information about your setup (hardware, software, versions, etc) to help us to reproduce this issue. If you have any information that can help improve this article, please email us at, reference this article, and provide the information you found useful in resolving the USB Connectivity issue.

The following information summarizesthe latest releases of

Octane firmware,

Utilities,

Development Libraries, and

Tools

R120 / R220 / R420

R640

R660

R680

(SpeedwayR)

(xPortal)

(xSpan)

(xArray)

Firmware**

6.2.1

6.2.1

6.2.1

6.2.1

Speedway Connect Software

2.8.0

2.8.0

2.8.0

2.8.0

ItemTest Software Utility

1.14.0

1.14.0

1.14.0

1.14.0

Octane SDK Library (.NET and Java)

3.0.0

3.0.0

3.0.0

3.0.0

Impinj LLRP Tool Kit (LTK) Library (.NET, Java, C++, and C)

10.34.0

10.34.0

10.34.0

10.34.0

Embedded Development Tools and Sample Application (ETK)

6.0.0

6.0.0

6.0.0

6.0.0

** - For Authorized Partners only!

The Vonets VAP11G-300 is an example of a low cost Wi-Fi bridge that connects to the Speedways Ethernet portand powers offthe Speedways USB port.

The Vonets bridge is presented because of its:Compact size (90 x 45 x 15 mm), ruggedness, powered by Speedway USB (avoids additional AC power source, mobile friendly), 802.11b/g/n support, security support, and it is economical. The bridge is available for around US$20 online by vendors such as www.amazon.com.

ReaderConnectivity

How to install theVonets VAP11G-300

Step 1: Follow the Installation Manual Instructions

Follow the VAP11G-300 installation manual provided on how to configure the VAP11G-300 into Intelligent Wi-Fi bridge mode.

Notes that may help while following the installation manual:

You will have the option to configure the VAP11G-300 overyour PC's Wi-Fi or Ethernet adapter. Wi-Fi was an easy option.

Performing a factory reset by pressingthe reset button down with a paperclip for more than 5 seconds is a quick wayto start over if ever needed.

We used the PC to power the VAP11G-300 over USB during the configuration phase.

When the instructions ask to turn off and reboot VAP11G-300 after entering the SID and WPA2password (see below), we performed this by unplugging the VAP11G-300 from the USB and re-pluggingit back in.

Step 2: Connect Speedway to the VonetsVAP11G-300

Once the VAP11G-300 isconfigured, connect it to your Speedway by powering it from the USB host port and connecting the Ethernet cable as shown in the photo at the top ofthis article.

Step 3: Find IP address of Speedway

With the Wi-Fi bridge now communicating with your access point,you will need to findthe IP address assigned to the Speedway. I used the Web UI on my ASUS RT-N66W Dual-Band Wireless-N900 Gigabit Router, see image below. 192.168.1.21 is the IP for mySpeedway, 192.168.1.103 is the IP for my PC, and 192.168.1.251 was assigned to the VAP11G-300.

Step: 4: Best Practice, Map the Speedway MAC address to a static address

Manually assigning an IP address to the Speedway will allow you to consistently access your readerwith the same IP. The image below from the ASUSaccess point UI shows how to instruct itsDHCP Server to map theSpeedway'sMAC address to the static IP 192.168.1.21.

Further Comments and Recommendations

This article serves as an example. Other Wi-Fi bridge options are available that can be configured in a similar manner.

We separated the Access Point with theVAP11G-300 by about 80 feet (25 meters) in ourtypical office environment which is a large room with cubicles, desks, and chairs. Throughput was more than adaquate to read tags atover 1,100 reads per second.

Use the keepalive and link monitor facilities shown in the "Keepalives" Octane SDK and example. You will want to monitor the TCP/IP based LLRPconnection, reconnecting whenever there is a network hiccup.

The" Scan Hotspots" tab will let you select and connect to a Wi-Fi network to connect to regardless of the authentication type. After, you will need to enter a passcode. See below:

This article will cover the "Hello World" LLRP application in C# .NET Framework 4.6.1. It will show how to setup an Impinj Speedway RAIN RFID readerwith minimal configuration and start reading tags. To keep things concise, much of the error handling required in a production application has been omitted.First, you'll need to download the LLRP Toolkit (LTK) for .NET. It's available at the following link as well as through NuGet.

If using Visual Studio, you can add the NuGet package through the solution explorer by right clicking on the solution's name and selecting "Manage NuGet Packages..". You should then be able to switch to the 'Browse' tab and search for "Impinj", which should show the following NuGet package listed:

You will then want to click on this NuGet package and select the "Install" button after ensuring you've selected the latest stable version from the dropdown, example shown below:

Assuming you are on .Net Framework 4.6.1 or greater, this should install without issue, and you should now be able to use the LTK libraries in your application to communicate with your Speedway reader.

If manually installing the libraries instead, after downloading the libraries to your system, create a new sub-directory called 'lib' in your project and extract these four LTK files to it:LLRP.dllLLRP.Impinj.dllLLRP.Impinj.pdbLLRP.pdbOpen up your project in Visual Studio and add references to these libraries by selecting "Project->Add Reference" from the menu.

Add the library import statements at the top of your class.An ROSpec tells the Speedway reader what data you want to read and when you want to read it. The Speedway readers support one ROSpec on the reader at a time. Before you can add a new ROSpec, you must delete any existing ones. This can be done by sending a DELETE_ROSPEC message.

using Org.LLRP.LTK.LLRPV1;

using Org.LLRP.LTK.LLRPV1.DataType;

using Org.LLRP.LTK.LLRPV1.Impinj;

static void Delete_RoSpec()

{

MSG_DELETE_ROSPEC msg = new MSG_DELETE_ROSPEC();

msg.ROSpecID = 0;

MSG_ERROR_MESSAGE msg_err;

MSG_DELETE_ROSPEC_RESPONSE rsp =

reader.DELETE_ROSPEC(msg, out msg_err, 2000);

if (rsp != null)

{

// Success

Console.WriteLine(rsp.ToString());

}

else if (msg_err != null)

{

// Error

Console.WriteLine(msg_err.ToString());

}

else

{

// Timeout

Console.WriteLine("Timeout Error.");

}

}

Now you can add a new ROSpec using the ADD_ROSPEC message.

static void Add_RoSpec()

{

MSG_ERROR_MESSAGE msg_err;

MSG_ADD_ROSPEC msg = new MSG_ADD_ROSPEC();

// Reader Operation Spec (ROSpec)

msg.ROSpec = new PARAM_ROSpec();

// ROSpec must be disabled by default

msg.ROSpec.CurrentState = ENUM_ROSpecState.Disabled;

// The ROSpec ID can be set to any number

// You must use the same ID when enabling this ROSpec

msg.ROSpec.ROSpecID = 123;

// ROBoundarySpec

// Specifies the start and stop triggers for the ROSpec

msg.ROSpec.ROBoundarySpec = new PARAM_ROBoundarySpec();

// Immediate start trigger

// The reader will start reading tags as soon as the ROSpec // is enabled

msg.ROSpec.ROBoundarySpec.ROSpecStartTrigger =

new PARAM_ROSpecStartTrigger();

msg.ROSpec.ROBoundarySpec.ROSpecStartTrigger .ROSpecStartTriggerType = ENUM_ROSpecStartTriggerType.Immediate;

// No stop trigger. Keep reading tags until the ROSpec is disabled.

msg.ROSpec.ROBoundarySpec.ROSpecStopTrigger = new PARAM_ROSpecStopTrigger();

msg.ROSpec.ROBoundarySpec.ROSpecStopTrigger.ROSpecStopTriggerType =

ENUM_ROSpecStopTriggerType.Null;

// Antenna Inventory Spec (AISpec)

// Specifies which antennas and protocol to use

msg.ROSpec.SpecParameter = new UNION_SpecParameter();

PARAM_AISpec aiSpec = new PARAM_AISpec();

aiSpec.AntennaIDs = new UInt16Array();

// Enable all antennas

aiSpec.AntennaIDs.Add(0);

// No AISpec stop trigger. It stops when the ROSpec stops.

aiSpec.AISpecStopTrigger = new PARAM_AISpecStopTrigger();

aiSpec.AISpecStopTrigger.AISpecStopTriggerType =

ENUM_AISpecStopTriggerType.Null;

aiSpec.InventoryParameterSpec = new PARAM_InventoryParameterSpec[1];

aiSpec.InventoryParameterSpec[0] = new PARAM_InventoryParameterSpec();

aiSpec.InventoryParameterSpec[0].InventoryParameterSpecID = 1234;

aiSpec.InventoryParameterSpec[0].ProtocolID =

ENUM_AirProtocols.EPCGlobalClass1Gen2;

msg.ROSpec.SpecParameter.Add(aiSpec);

// Report Spec

msg.ROSpec.ROReportSpec = new PARAM_ROReportSpec();

// Send a report for every tag read

msg.ROSpec.ROReportSpec.ROReportTrigger =

ENUM_ROReportTriggerType.Upon_N_Tags_Or_End_Of_ROSpec;

msg.ROSpec.ROReportSpec.N = 1;

msg.ROSpec.ROReportSpec.TagReportContentSelector =

new PARAM_TagReportContentSelector();

MSG_ADD_ROSPEC_RESPONSE rsp = reader.ADD_ROSPEC(msg, out msg_err, 2000);

if (rsp != null)

{

// Success

Console.WriteLine (rsp.ToString());

}

else if (msg_err != null)

{

// Error

Console.WriteLine (msg_err.ToString());

}

else

{

// Timeout

Console.WriteLine("Timeout Error.");

}

}

When an ROSpec is added, it is disabled by default. Before it can be used, it must be enabled with the ENABLE_ROSPEC message.

static void Enable_RoSpec()

{

MSG_ERROR_MESSAGE msg_err;

MSG_ENABLE_ROSPEC msg = new MSG_ENABLE_ROSPEC();

msg.ROSpecID = 123;

MSG_ENABLE_ROSPEC_RESPONSE rsp =

reader.ENABLE_ROSPEC(msg, out msg_err, 2000);

if (rsp != null)

{

// Success

Console.WriteLine (rsp.ToString());

}

else if (msg_err != null)

{

// Error

Console.WriteLine (msg_err.ToString());

}

else

{

// Timeout

Console.WriteLine("Timeout Error.");

}

}

Since we set our ROSpec start trigger type to "immediate", the Speedway reader will begin reading tags as soon as the ENABLE_ROSPEC message is sent. In order to receive tag reports you must specify an event handler to call when data is ready. Here's an example of what that function should look like.

static void OnReportEvent(MSG_RO_ACCESS_REPORT msg)

{

// Loop through all the tags in the report

for (int i = 0; i < msg.TagReportData.Length; i++)

{

if (msg.TagReportData[i].EPCParameter.Count > 0)

{

string epc;

// Two possible types of EPC: 96-bit and 128-bit

if (msg.TagReportData[i].EPCParameter[0].GetType() ==

typeof(PARAM_EPC_96))

{

epc = ((PARAM_EPC_96)

(msg.TagReportData[i].EPCParameter[0])) .EPC.ToHexString();

}

else

{

epc = ((PARAM_EPCData)

(msg.TagReportData[i].EPCParameter[0])) .EPC.ToHexString();

}

Console.WriteLine("epc = " + epc);

}

}

}

Now that we have all of the basic functions written, let's write the main function that will connect to the reader and send all of the messages.

static LLRPClient reader;

static void Main(string[] args)

{

// Create a LLRPClient instance.

reader = new LLRPClient();

/*

Connect to the reader.

Replace "SpeedwayR-10-25-32" with your reader's hostname.

The second argument (2000) is a timeout value in milliseconds.

If a connection cannot be established within this timeframe,

the call will fail.

*/

ENUM_ConnectionAttemptStatusType status;

reader.Open("SpeedwayR-10-25-32", 2000, out status);

// Check for a connection error

if (status != ENUM_ConnectionAttemptStatusType.Success)

{

// Could not connect to the reader.

// Print out the error

Console.WriteLine(status.ToString());

// Do something here.

// Your application should not continue.

return;

}

/*

If you successfully connect to the reader, the next step is to

create a delegate. The delegate determines which function gets

called when a report event occurs.

*/

reader.OnRoAccessReportReceived += new

delegateRoAccessReport(OnReportEvent);

// Send the messages

Delete_RoSpec();

Add_RoSpec();

Enable_RoSpec();

// Keep reading tags until the user presses return

Console.ReadLine();

// Cleanup the reader by deleting the ROSpec

Delete_RoSpec();

}

Documentation for the latest Octane firmware release including the following:

Download Reader Installation & Operations Guide

Download Reader and Gateway Embedded Developers Guide

Download Octane SNMP Guide & MIBs

Download Reader How-To: Health Monitoring

Download Octane LLRP Guide

Download Impinj LTK Programmers Guide

Download Impinj RShell Reference Manual

Download Octane Firmware Upgrade Reference Manual

Download Reader CAD Drawings

View Reader and Gateway FAQ

Overview

We encounter many requests for support around connectivity to our readers, gateways, and embedded applications (e.g. Speedway Connect).

The purpose of this article is to discuss techniques for troubleshooting and resolving communication connectivity issueswith our readers and gateways. Each one of the troubleshooting steps mentioned are grouped into their appropriate section and can be done individually.

Table of Contents

Overview

Table of Contents

Ways to Connect

Connecting to the reader or gateway via the Ethernet port.

Basic Troubleshooting Steps

Cannot connect when directly connecting a singlereaderor gateway to the Host PC via Ethernet:

Cannot connect when using Ethernet through a router, switch or hub:

Cannot connect when using Windows Virtual Machine:

RShell related checks

Cannot connect when using either Ethernet setup:

Cannot connect when another Ethernet connection already exists

"Connection Denied" Errors:

Connecting to the reader or gateway via the Console port.

Basic Troubleshooting Steps

Communication issues from the reader to the outside

Some less frequent issues

Ways to Connect

There are two ways to connect to the Impinj readers and gateways:

Connecting to the reader or gateway via the Ethernet port.

Reader or gateway connected directly to a PC via Ethernet cable

Reader or gateway connected to a network (e.g. via hub/switch)

Connecting to the reader or gateway via the Console port for configuring the system.

Reader or gateway connected directly to a PC via serial console cable ( Here's how )

NOTE: Use this connection to access the device's RShell command line interface;

NOTE: Controlling and configuring the reader for LLRP and getting tag reads are not available via this connection.

Several different applications can help you connect to your readers and gateways. A program named Putty (You can download and install PuTTY from http://www.putty.org/ ) on Windows based systems or ssh commands on UNIX based ones are a few examples.

There are also system configuration settings that should be setup correctly for on-reader applications to work with outbound communications:

Via DNS

Via NTP

Connecting to the reader or gateway via the Ethernet port.

Basic Troubleshooting Steps

#

Troubleshooting Steps

Details

1

Confirm the Ethernet cable is in the right port

Take a look at the back of the reader or gateway and make sure the Ethernet cable is in the Ethernet port and NOT the Console port, which are both RJ45 connectors: Ethernet cross-over cable

The Ethernet port has LEDs which should light up when a valid connection exists while the console port does not.

2

Ping the reader/gateway

Open a Command prompt.

Ping the reader/gateway over the network via their hostname and ip address.

Consider pinging both IPv4 and IPv6 addresses if on a dual IPv4/IPv6 network. E.g.

ping -4 speedwayr-XX-XX-XX

ping -6 speedwayr-XX-XX-XX

Note: Please remember to replace the XX-XX-XX with the last three (3) HEX characters of the MAC address. (If the MAC address is 00:16:25:11:FA:E1 then the hostname will be speedwayr-11-FA-E1)

Note: Please try adding ".local" or ".local.<tld>" to the end of the reader hostname if the pings do not work. Note: If the ping command does not initially succeed, flush the DNS cache per the directions further down this page.

Note: We are assuming your network is configured with a router, DHCP and DNS server.

3

Telnet to the reader/gateway

There are multiple ways to accomplish this activity. One such way is PuTTY on Windows based systems or telnetcommands on UNIX based ones.

Launch PuTTY. If prompted, run it as administrator.

In a WINDOWS environment, setup a Telnet connection in Putty to your reader's hostname or IP address on port 5084 (the default port used for LLRP communication on the reader) or 5085 (if encrypted). It will look like the example shown below:

Or In a UNIX environment, you will issue the command: telnet <READER HOSTNAME OR IP> 5084

After issuing that command, you should see a screen like the examples below. The first example is the response you will see from a Windows based system using PuTTY, while the second is from issuing the command from a UNIX based system. This shows that there is communication between the computer and reader port 5084.

4

SSH to the reader or gateway

Launch PuTTY. If prompted, run it as administrator.

In a WINDOWS environment, setup a SSH connection in Putty to your reader's hostname or IP address on port 22. It will look like the example shown below:

Or In a UNIX environment, you will issue the command: ssh -l root <READER HOSTNAME OR IP>

Login as user root with the default password of "impinj" (unless it was previously changed to something else)

5

Check DNS on the network

In Windows Command prompt, issue:

> nslookup speedwayr-XX-XX-XX,

> nslookup <reader/gateway IP address>.

Both commands should resolve correctly to each other.

6

Connect when your PC Wifi is disabled.

The PC may be attempting to access the reader via its' wireless (WiFi) port instead of its' Ethernet port 1. Turn off PC's WiFi port, remove Ethernet cable and then re-insert allowing the Acquiring Network Address message (in lower, right-side Windows toolbar) to time out and then re-attempt 2. Once connection is established, you can re-enable WiFi

Note: Here is a link to a Microsoft article on how to change the network adapter priority to eliminate the need for turning off the Wi-Fi connection:

https://support.microsoft.com/en-us/help/2526067

Cannot connect when directly connecting a singlereaderor gateway to the Host PC via Ethernet:

#

Troubleshooting Steps

Details

7

Re-install Bonjour

Uninstall Bonjour from your machine

D ownload Bonjour print services if not already done

Install Bonjour print services on your PC

Make sure Bonjour is installed on the PC via Control Panel > Add or Remove Programs.

Note: If you are unable to use Bonjour, please configure a hostto have a 169.254.1.x (255.255.255.0 mask) ip address and then access the reader via 169.254.1.1.

8

Check .local name

Bonjour is used to access the reader/gateway by hostname when you are directly connected to it, but it may not help when the reader/gateway is on the network.

Add .local to the end of the reader/gateway host name. For example, try pinging speedwayr-XX-XX-XX.local

Note: Using .local depends on the tld assigned for your company. For instance, tld could be .local.tld, or something else.

Note: We recommend that you register DNS names for the top-most internal and external DNS namespaces with an Internet registrar.

9

Check the default IP Address

The reader/gateway defaults to the following fixed IP address: 169.254.1.1

Try connecting to 169.254.1.1

Try to ping 169.254.1.1

Cannot connect when using Ethernet through a router, switch or hub:

#

Troubleshooting Steps

Details

10

Use Wireshark to determine network issues

Download and Install Wireshark from https://www.wireshark.org/.

Run wireshark,

Select the appropriate network connections,

Filter by "llrp"

Watch the messages as you try to connect to the reader/gateway.

The messages should give an indication of what is wrong with the connection.

Note: We are assuming your network is configured with a router, DHCP and DNS server.

11

Check the default IP Address

If your network does not support DHCP, the reader/gateway defaults to the following fixed IP address: 169.254.1.1.

If this address is already in use, the reader/gateway will select a random fixed IP address in the 169.254.xxx.xxx link local address range.

Connect to 169.254.1.1

If the prior step does not work, scan for other readers/gateways on 169.254.xxx.xxx

Commands like "arp" can assist with this search.

12

Flush the DNS cache on the PC

http://www.tech-faq.com/how-to-flush-dns.html

Cannot connect when using Windows Virtual Machine:

From time to time we get connectivity issue questions from customers using Windows Virtual Machines to run ItemTest.

#

Troubleshooting Steps

Details

13

Verify the Windows Virtual Machine network settings are setup properly.

Try using different network settings until it works. Here is an example of how that might look in Virtual Box when selecting a Bridged Adapter:

It should be roughly the same in similar applications.

RShell related checks:

You may be able to access the reader or gateway either via ssh or console cable. If so, it is important to run thru the following RShell activities:

#

Troubleshooting Steps

Details

14

Ensure Dynamic (DHCP) mode set

RShell (SSH or via serial/console cable) into the reader or gateway and issue these commands:

show network summary

If ipAddressMode does not equal Dynamic, issue the following RShell commands:

config network ip dynamic

reboot

Check to see if the ip address is specified.

The following would be a sign that the reader has not been assigned an IP address via DHCP, or assigned itself a link-local address (169.254.xxx.xxx).

The following would be a sign that the reader did receive the ip address from dhcp Notice how an ip address is actually specified.

15

Setup the reader/gateway with a static IP address

1. Ensure the IP address of the reader/gateway is using same subnet mask as the PC 2. Check for duplicate IP addresses assigned on the same network. One way to do this is to turn off the reader/gateway and ping the ip address to see if another system is using it.

RShell (SSH or via serial/console cable) into the reader or gateway

Find out the reader's IP address by typing the following at the RShell prompt:

show network summary

The results (as shown below) indicate a couple of things:

ipAddressMode = 'Dynamic' means this reader is set to acquire its IP address via DHCP. If this reader was set to a static IP address, it would say 'Static'.

ipAddress = '192.168.0.20' indicates this is the IP address for this reader.

To change the IP address, type the following at the RShell prompt:

config network ip static xxx.xxx.xxx.xxx("xxx"s are values between 1 and 255. For example, "config network ip static 192.168.0.20") Or use the following format:

config network ip static xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx (for example, if you type: > config network ip static 192.168.0.20 255.255.255.0 192.168.0.1 192.168.0.255 you are configuring the IP address, Netmask, Gateway, and Broadcast Address respectively, separated by a space character) NOTE: consult the RShell Reference Manual for additional details.

Reboot the reader with RShell command:

reboot

16

Check the logs

An explanation for how to acquire the reader/gateway logs can be found here: https://support.impinj.com/hc/en-us/articles/202756238-How-do-I-capture-logging-events-from-my-reader-

If you encounter an "Assert" error message in the logs this most likely means one of the reader/gateway programs has crashed and could be the reason the port is not open.

Here is an example message from the logs that may occur:

Event9='May 9 14:07:10 (none) MC4: Layer1: Assert - File: /mnt/work/firmware/reader/apps/mc4/layer1/spaceman/rfmux_common.c, Function: RFMux_updateFirmware, Line: 1308'

2. These type of issues would require you to send the logs to [email protected] so they can determine what is going on and check whether your reader/gateway is still under warranty.

17

Check port configuration settings

1. Run the following RShell commands to see if the configurable ports are enabled:

show network telnet

show network ssh

show network http

show network ftp

show network sftp

2. Now that you know what is enabled or disabled, configure the system for what you need using the following commands:

config network telnet enable

config network ssh enable

config network http enable

config network ftp enable

config network sftp enable

Note: Telnet is being removed as of Octane Firmware version 5.12

Cannot connect when using either Ethernet setup:

#

Troubleshooting Steps

Details

18

Check whether the reader/gateway ports are responding.

There are multiple ways to accomplish this activity. One such way is Putty on Windows based systems (Shown below) or ssh commands on UNIX based ones.

Launch PuTTY. If prompted, run it as administrator.

Enter the reader/gateway address.

Try connecting with putty to port 5084 and 5085 and send us the output? It should look like:

A working system would output something similar to:

19

Perform a factory reset on the reader/gateway

https://support.impinj.com/hc/en-us/articles/202756458-Performing-Factory-Reset-on-the-Speedway-Revolution-Reader-VIDEO-

20

Try connecting via POE

If you are currently powering the reader/gateway via a power adapter to the wall and have the capability to power the reader/gateway over POE, then try switching the reader/gateway to POE.

21

Try connecting via Wall Outlet

If you are currently powering the reader/gateway via a POE and have the ability to connect with non-POE, then try switching the reader/gateway to wall outlet power via a Impinj power adapter.

22

Change Switch/Router Ports

When connected via POE, please move the current port on the switch/router the reader/gateway is connected to a different one.

23

Disable PoE on the Switch

The reader/gateway specification dictates that when both the power adapter and Ethernet cable with PoE are connected to the reader, the reader then uses the power adapter to draw power and uses the Ethernet for network communication.

We've received reports in the past where if customers were using a certain type of Cisco switch and the network communication did not work.

The Cisco switches have a behavior of disabling port operation if the PoE device doesnt draw any current. The following Cisco support page explains the details of configuring PoE :

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/12-2/31sg/configuration/guide/conf/PoE.html

When the reader/gateway is plugged into both power (wall.. aka brick) and PoE port, then disable PoE on the switch/router.

One possible way to do this is:

(In this example slot 5, port 2 is being set to PoE = never.) Switch# configure terminal Switch(config)# interface fastethernet 5/2 Switch(config-if)# power inline never Switch(config-if)# end

24

Confirm power capabilities of PoE switch

Confirm that you are not exceeding the power capabilities of the PoE switch.

The Speedway Revolution draws 11.5W max so be sure that the switch supports the number of connected readers and any other powered devices.

Note: If the power level is too low, the reader will begin rebooting if not powering down.

The xArray has been measured to draw 13.6W

Note: If the power level is too low, the gateway can become highly erratic without rebooting or show the red fault LED remaining lit perpetually.

Note: All of our readers and gateways are compliant with the PoE 802.3af standard maximums of 15.4 watts. All PoE ports should be configured to support the maximum current draw.

Note: Most PoE switches will have a maximum power budget that can be exceeded if there are too many PoE devices connected.

25

Check the PoE cable length

Confirm that the Ethernet cable run from PoE source to reader does not exceed 100m (~330 feet).

26

Swap readers/gateways

Swap known good readers/gateways with the one(s) that might not be working.

27

Swap Ethernet cables

Swap known good cables with the one(s) that might not be working. This will identify any Defective Ethernet (RJ45) cable(s).

Cannot connect when another Ethernet connection already exists

#

Troubleshooting Steps

Details

28

Uninstall existing on reader/gateway applications.

Visit http://<reader/gateway name or ip address>/

Check to see if the LLRP Status is Disconnected or not.

In the case above, a program on the reader (127.0.0.1) is connected to the LLRP Port (5084 default).

2. Check "Application SW Version" in the "Details" section.

Note: If "Application SW Version" is missing, then nothing is installed on the reader/gateway.

3. If an on reader application is taking over the LLRP port, you can uninstall an on-reader application by issuing the following RShell command:

config image removecap

29

Disable Speedway Connect

An alternative to uninstalling the cap, it may be you have Speedway Connect installed and running so it will be necessary to disable it.Speedway Connect will consume the 5084 LLRP port if enabled. You can disable Speedway Connect by:

1. Visiting https://<reader/gateway name or ip address>/ and

2. Click the Green Tags Status button to Red Tags Status and click the "Apply" button:

30

Check for other applications connected to this reader/gateway

Visit http://<reader/gateway name or ip address>/

Check to see if the LLRP Status is Disconnected or not.

In the case above, an application on host 10.200.30.46 is connected to the LLRP Port.

1. Locate this system and get the application terminated.

2. Rebooting the reader/gateway may also be an option.

"Connection Denied" Errors:

#

Troubleshooting Steps

Details

31

Update the firewall rules

If a firewall is between your host and reader/gateway, it is highly likely the communication is being prevented from there.

Add the reader/gateway IP address and/or host name to your firewall program as safe or allowed.

Alternatively, add the following ports for communication to the firewall:

Port

Description

Direction

21

FTP Port (If Enabled)

To Reader

22

SSH (RShell) Port

To Reader

23**

Telnet Rshell Port (If Enabled)

To Reader

80

Speedway Reader Web UI

To Reader

123

Reader NTP Protocol

From Reader

162*

UDP Port for SNMP Trap

From Reader

443

Speedway Connect UI (If installed)

To Reader

5084 *

Unsecurred LLRP Port

To Reader

5085 *

Encrypted LLRP Port

To Reader

These can be enabled and disabled * These ports are changeable ** Telnet is being removed from the reader with Octane FW version 5.10.2

32

Ensure you have the latest and appropriate region firmware installed.

Visit http://<reader/gateway name or ip address>/

Check to make sure you have the latest installed (6.2.0.240 as of 11/19/2019):

Impinj Partners can get the latest firmware here: https://support.impinj.com/hc/en-us/articles/202755438-Octane-Firmware-for-Readers

2. Check to make sure the Regulatory Region is correct:

Connecting to the reader or gateway via the Console port.

Basic Troubleshooting Steps

#

Troubleshooting Steps

Details

33

Confirm the Console cable is in the right port

Take a look at the back of the reader or gateway and make sure the Console cable is in the Console port and NOT the Ethernet port, which are both RJ45 connectors:

An example of a cable that can be used is located here:

https://www.amazon.com/gp/product/B01AFNBC3K

34

Check modem settings are correct

Expect the following settings to be used: Bits per second = 115200 Data bits = 8 Parity = None Stop Bits = 1 Flow Control = None

35

Connect to the Reader or Gateway

Here is an example of how to connect using Putty on a Windows Environment:

After you click the "Open" button, you should get an RShell login prompt.

If you see a blank screen, hit the "Enter" key once to get the login prompt.

Type the following login and password information: a) Login: root b) Password: impinj (the password maynot be shown as you type them)

36

Try Different Cables

Use DB9-to-RJ45 (or DE9-to-RJ45) cable from Impinj (part # IPJ-A4000-000) or,

If using different cable, ensure pin out matches the ones defined in section 2.8 of the Impinj Reader Gateway Embedded Developers Guide:

https://support.impinj.com/hc/en-us/articles/202755298-Reader-Documentation

https://support.impinj.com/hc/en-us/articles/203627878-xArray-Documentation

37

Ensure Adapter using FTDI chip

If using a USB-Serial adapter,

Ensure the adapter is using an FTDI chip: http://www.ftdichip.com/Products/EvaluationKits/UC232R.htm

Note: There are some integrated cables now available that have the USB to serial converter built-in, E.G.:

https://www.amazon.com/gp/product/B01AFNBC3K

38

Find the COM port number

How to find COM port number

Press the Windows key and R at the same time. Run dialog opens.

Enter devmgmt.msc and click OK button. If prompted, choose Yes.

In Device Manager, expand Ports (COM & LPT).

Find "USB Serial Port (COMx) entry. Use this COM port number in PuTTY's serial connection (in the example below, it is COM4).

Communication issues from the reader to the outside:

You may be able to access the reader or gateway either via ssh or console cable but there are issues with on-reader applications from communicating with the outside world. If so, it is important to run thru the following RShell activities:

#

Troubleshooting Steps

Details

39

Make sure dns is setup properly

When switching to Static IP it has been brought up that on-reader applications cannot reach remote systems.

Make sure your dns settings are correct. show network dns

If not, add (and/or remove) the dns servers. config network dns add <ip of dns server> config network dns del <ip of dns server>

reboot

Another check is to see if the on-reader application can connect to the remote systems via IP Address.

40

Make sure ntp is setup properly

For NTP, it is important to understand that the time does not change immediately, and the rate of change is influenced by how big the time difference is between the current reader time and the timestamp provided by your NTP server; the bigger the difference, the more gradual the change. This is to limit any errors that might occur in the system by a rapid time change (log file timestamps, for example).

Make sure your ntp settings are correct.

show system summary

show network ntp

a. Note: If the NTP Reach metric (NtpServerStatic1Reach) is zero then the reader has been unable to reach an NTP server at the IP address you have specified.

2. if not, add (and/or remove) the ntp servers.

config network ntp disable

config network ntp add <ip of ntp server>

config network ntp del <ip of ntp server>

config network ntp enable

3. reboot

41

Update your application to use 127.0.0.1 instead of localhost

Octane firmware versions prior to 5.12 cause our readers to resolve hostname localhost via dns instead of the /etc/hosts file. If someone or something adds localhost to the dns server that points to a machine on the network then all attempts to connect to the reader via llrp port 5084 will fail to work.

The workaround for this is to update your embedded application to connect via IP address 127.0.0.1 instead of localhost.

Some less frequent issues:

1) Routing table issue 2) ARP cache is corrupt 3) Most modern PCs have an auto-crossover network card so that you can connect directly between your PC and the reader/gateway. However, if using an older PC or have tried everything else, you should try either connecting through a switch, hub or router or else use an. 4) DNS server cache not updated issue.

ItemTest is a simple, easy-to-use, Windows-compatible application for evaluating the functionality and performance of one or more Impinj readers and gateways. ItemTest supports Inventory, Location, and Direction mode use cases. Additionally, it can perform rudimentary tag memory access operations.

Download Impinj ItemTest Software & Release Notes

Documentation:

Latest Released Version: 1.14.0

Supported Hardware: Speedway Revolution readers (R120, R220 and R420) and Gateways (xPortal R640, xSpan R660, and xArray R680)

Recommended Reader / Gateway Firmware Version: - Octane FW 6.2 or later : Download Here (For Impinj Partners) - Older versions may not support certain features

Required OS: Windows 10

User Guide: Accessible from the Help Menu within ItemTest. It describes how to install, configure, and perform basic testing on an Impinj reader and gateway. It includes detailed procedures that explain each feature and how it should be used to help you test and verify an Impinj reader and/or gateway.

Customers switching from MultiReader to using ItemTest should read this guide.

Training Videos (For Impinj Partners): Many capabilities are explained by the training videos we provide.

Related Material: Understanding EPC Gen2 Search Modes and Sessions Reader Modes Made Easy How to disable and Re-enable AutoTune for Monza 6 Use Monza X to Trigger an Interrupt or Blink an LED Capturing Debug Data (aka RDD)

Download Older Versions

To mount an xArray, consider using the off-the-shelf products described in this document. Each is compatible with the xArrays Vesa 200mm based mounting plate and rated to hold the xArrays 18 pound weight. The products you choose will depend on your deployment scenario. We outline the following scenarios:

Installing an xArray in a dropped ceiling

Hanging the xArray with a hangingmount

Installing the xArray directly onceiling

Hanging the xArray from a pipe or steel rod

This document is not a substitute for the installation materials that come with these products. Please follow the mounting hardware product-specific instructions carefully when mounting an xArray.

NOTE: We recommend using Loctite 242 forevery install (per Loctite's installation requirements). This eliminates the need to specify lock washers or lock nuts.

Washers and bolts were ordered from the McMASTER web site per the requirements for the M6 machine screw. Length requirements are listed in the xArray Installation and Operations Guide. Also, McMASTER provides useful navigation tools to find the right sizes.

All mounting options described below that are third-party products are neither sold nor warrantied by Impinj. Impinj is not responsible for any defects in these third-party products.

You must validate that your installation meets all safety requirements and building codes. Improper installation could result in the appliance falling, which in turn could cause property damage, bodily injury or death.

Third-party mounts described have NOT been tested by UL for the installation of the appliance.

Dropped 2' X 2' Ceiling Mount Option

When installing to a dropped ceiling (2 X 2 ceiling tiles), Impinj offers a solution designed specificallyfor xArray called the Gateway Suspended Ceiling Mounting Kit.

Download xArray Ceiling Mounting Kit Installation Guide

This kitcontains:

Acustom-drilled 2 foot x 2 foot steel plate to attach the xArray

Anchors and cables required to securely support both the weight of the steel plate and xArray

Other required hardware including screws, nuts, pipe clamps, and cable quick locks

For more information on what's included in the kit and mounting instructions please download the Installation Guide.

Manufacturer/Model

Description

Impinj / IPJ-A680-000

NOTE: The grey mounting bracket shown in the above picture is NOT included in this kit. This bracket is included when purchasing the xArray.

Hanging Mount Options

Hanging mounts are much cheaper than dropped ceiling mounts. However, they are very noticeable, and they reduce the amount of overhead space between the xArray and possible tag positions. With an open cement ceiling, you may need to lower the xArray due to obstructing objects such as HVAC equipment or lighting can have a negative impact on the tag read performance of the xArray. The following hanging mounts are good choices for this scenario.

Figure 11: HVAC and Lighting required lowering the xArray

Cable Matters

This under $30 solution provides an HDMI cable. Difficulty: Relatively Easy

Manufacturer/Model

Description

Cable Matters / 106009

Figure 12

CableMatters106009

Vertical Distance: 43cm to 66cm

McMaster / 92005A423

Figure 13

Metric Pan Head Phillips Machine Screw Zinc-PlatedSteel,M6Size,14mmLength,1mm Pitch

McMaster / 91166A250

Figure 14

Zinc-Plated Steel Flat Washer, M6 Screw Size, 6.4mm ID, 12.0mm OD

VideoSecu

This under $30 solution is very similar to the cable matters above with a slightly longer vertical distance. Difficulty: Relatively Easy

Manufacturer/Model

Description

VideoSecu / PJ2B

Figure 15

VideoSecu PJ2B

Vertical Distance:46cm to 71cm

McMaster / 92005A423

Figure 16

Metric Pan Head Phillips Machine Screw Zinc-PlatedSteel,M6Size,14mmLength,1mm Pitch

McMaster / 91166A250

Figure 17

Zinc-Plated Steel Flat Washer, M6 Screw Size, 6.4mm ID, 12.0mm OD

On Ceiling Mount Options

Direct to Ceiling

On-ceiling options are low-cost and provide good vertical clearance. They are less conspicuous than hanging mounts. They work well on an open cement ceiling where there is no need to lower the xArray to adjust the height above the tags or to avoid other equipment.

Figure 18: xArray Mounting plate directly bolted to a dropped ceiling

Uses Configuration 2 outlined in the xArray Installation and Operations Guide (download available at xArray Documentation )

Vertical Distance: 0 cm

Silver Ticket

This solution costs under $30 allowing you to adjust the tilt and has a nice small vertical distance of 7cm. Difficulty: Easy

Manufacturer/Model

Description

Silver Ticket Products / STR-MOUNTSB

Figure 19

STR-MOUNTSB

Vertical Distance:7 cm to 7.62 cm

McMaster / 92005A423

Figure 20

Metric Pan Head Phillips Machine Screw Zinc-PlatedSteel,M6Size,14mmLength,1mm Pitch

Note: The test in the photo above was performed without a washer. To use a washer a longer machine screw than the 14mm tested will be required.

Amer

This one costs approximately $60 and allows you to adjust the tilt. It is the most noticeabledirect-mount option, as it is a large mount with 20 cm of vertical distance. Difficulty: Relatively Easy

Manufacturer/Model

Description

Amer / AMRP100

Figure 21: AMRP100 + xArray mounting plate

AMRP100

Vertical Distance:20 cm

This is the same hardware used for the AMRDCP100KIT false dropped ceiling system.

McMaster / 92000A428

18-8Stainless Steel Metric Pan Head Phillips Machine Screw M6 Size,20mmLength,1mm Pitch

These machine screws project mount to the xArray mounting plate as shown above

Pipe or Steel Rod Mount Options

We only recommend one steel pipe mount option. It requires an overhead steel pipe to support the xArray. Somewhat noticeable, good vertical clearance, but more work to install than other options.

Pro Signal

The pipe mounting solution is under $50 but requires the 75mm adapter resulting in more parts to order and assemble. Difficulty: Medium

Manufacturer/Model

Description

Pro Signal / Bracket Pole Mount VESA75/100

Figure 22: Bracket pole mount

Rugged bracket fits any 30mm ~ 60mm diameter pole

Parts Express / Parts Express Universal TV Mount Adapter Plate VESA 75 to 100 x 200 or 200 x 200

Figure 23: Vesa 75mm to 200mm adapter

Connects the Bracket Pole mount 75mm to the xArray which is Vesa 200mm

McMaster / 93625A150

Type 18-8 Stainless Steel Nylon-Insert Locknut, M4x0.7 Thread Size, 7mm Wide, 5mm High

McMaster / 92000A222

18-8 Stainless Steel Metric Pan Head Phillips Machine Screw, M4 Size, 12mm Length, .7mm Pitch

McMaster / 92005A423

Figure 24

Metric Pan Head Phillips Machine Screw Zinc-PlatedSteel,M6Size,14mmLength,1mm Pitch

McMaster / 91166A250

Figure 25

Zinc-Plated Steel Flat Washer, M6 Screw Size, 6.4mm ID, 12.0mm OD

GPIOs (general purpose inputs/outputs) are used to do simple digital communication between the Impinj Revolution-based reader platform and external peripherals. Here is an excellent write-up on GPIO using the Impinj OctaneSdk C# framework and an Impinj GPIO box: https://support.impinj.com/entries/30535853-Connecting-GPIO-Devices-to-Speedway-Revolution-Reader

Impinj reader products based on the Impinj Revolution architecture, specifically models

420 (4 antenna port Reader) 220 (2 antenna port Reader) 640 (marketing name is xPortal)

have 4 GPI AND 4 GPO pins available for your use. They are exposed via the 15-pin multi-purpose port on the back of the reader. NOTE: IF YOU ARE USING THE IMPINJ ANTENNA HUB YOU WILL **NOT** HAVE ACCESS TO THESE GPIO PORTS AS THEY ARE USED BYTHE ANTENNA HUB FOR SPECIAL SIGNALLING PURPOSES. Also, please note that this port will not work with a VGA cable!

In addition to the standard way of explicitly reading/writing the state of the digital IOs, the GPIOs can be tied to certain discrete events occurring within a typical RFID environment. Examplesinclude starting stopping the reader when a particular input goes high/low. In the field, this high/low input might come from a photo-eye which asserts the line high when an object is in the field of view and conversely sets it low when thereisn't.These use-models are well-defined within standard LLRP and many reading this article are likely familiar with them.

LLRP also allows for custom "extensions" that allow reader vendors to incorporatespecial functionality, over and above that provided in base LLRP. In the GPIO realm, Impinj does this via it's Advanced GPOConfiguration.

From this note on Impinj Advanced GPO :

This custom parameter controls the advanced GPO feature of the readers. When set to Normal (default) the GPO is set via the regular LLRP SET_READER_CONFIG message. When set to Pulsed, the GPO changes state based on the SET_READER_CONFIG message, and will change to the opposite state after GPOPulseDurationMSec milliseconds. When set to Reader_Operational_Status, LLRP_Connection_Status*, or Reader_Inventory_Status, the GPO status acts like a Boolean value. When high (true, 1), the corresponding status is true, meaning the reader is operating, has a LLRP connection, or is inventorying. When low (false, 0), the opposite is the case.

Whenever a GPO has been associated with a specific reader status, it cannot be set via the normal LLRP protocol. If a SET_READER_CONFIG message is received that attempts to change the state of a GPO associated with a specific reader status, the message will be rejected by the reader.

Remember to run Enable_Impinj_Extensions() prior to using these commands.

*If using an xArray reader the LLRPConnection status is not functional.

So, if you want a GPO to be asserted when any,some or all of these RFID events:

1. The reader is operational

2. The reader has an LLRP connection established

3. The reader is actively emitting RF and trying to read tags

occur, you can do so easily with the Impinj Advanced GPO settings.

OK, so let's do some examples:

Example: Get the current GPIO values -- C++

/* Get the Current State of a GPIO Pin If argument isOutput = false then it's an implied Input pin. Pin is a number in the range 1-4*/int QuickWebSample::getGpi(int port){ int state = 0; CGET_READER_CONFIG *pConfig = NULL; CMessage *pMsg = NULL; CGET_READER_CONFIG_RESPONSE *pGRCRsp = NULL; list<CGPIPortCurrentState*>::iterator curr; CGPIPortCurrentState *pState; pConfig = new CGET_READER_CONFIG(); pMsg = transact(pConfig); delete pConfig; /*don't need this anymore so free as we go*/ /* Leap of faith - we should only get back a GET_READER_CONFIG_RESPONSE so just blindly cast it for this demo; check the type and safely cast and evaluate in production code */ pGRCRsp = (CGET_READER_CONFIG_RESPONSE *)pMsg; curr = pGRCRsp->beginGPIPortCurrentState(); while ( curr != pGRCRsp->endGPIPortCurrentState() ) { if ( (*curr)->getGPIPortNum() == port ) { state = (*curr)->getState(); break; } curr++; } delete pGRCRsp; return state;}

Download Impinj Support Welcome Guide

INTRODUCTION

Thank you for using Impinj products. Impinj recognizes that support is crucial to the success of our customers and we are dedicated to helping them succeed and get the most value out of their Impinj products. This guide provides useful information about our support resources and instructions for requesting help.

GETTING HELP

Self-Help Resources

Impinj customers can find technical documentation and downloads on our Support Portal. Resources include sample code, troubleshooting guides, educational videos, and support articles about various other topics. To access content, please visit https://www.impinj.com/support. Most self-help content is available without logging in.

There is a small subset of content that is only available to select customers based on the following guidelines:

Content

Requirements for Access

Reader/Gateway

Octane firmware

Reader or Gateway covered under warranty or firmware update plan. Firmware is distributed via Impinj Authorized Partners. End users should contact their Impinj Authorized Partner for access.

Software

ItemSense software

Valid ItemSense license. Contact your Impinj Regional Sales Manager for more details.

ItemEncode firmware and development libraries

Impinj Authorized Partners must have signed ItemEncode Integrator Agreement. Contact your Impinj Regional Sales Manager for more details.

Monza

Wafer specifications

This is available to customers who purchase Monza products in wafer form and have signed NDA with Impinj. Contact your Impinj Regional Sales Manager for more details.

Antenna reference designs

This is available to customers who have signed our Antenna License Agreement. Contact your Impinj Regional Sales Manager for more details.

If you meet the criteria above and cannot access content, please sign in and visit this page to request restricted access.

Requesting Support

Impinj Customer Support Engineers (CSEs) are available between 4:00am 5:00pm Pacific Time.

Customers can submit a support request for products under warranty via these two methods:

Fill out the " Submit a request form.

Send an email to Impinj Support.

Either method will generate a numbered ticket in our Support database.

Requests submitted in this manner will ensure the appropriate Impinj Customer Support Engineer responds in a timely manner.

We currently do not offer a Customer Support phone number to call for assistance, however once a ticket has been established, the CSE is able to coordinate a phone call through the ticket. Customers can expect an initial response within 2 business days after creating a support case. The time to full resolution of a case depends on the level of technical complexity.

Note: For certain customer requests, we may ask the customer to contact their Impinj Authorized Partner first. We rely on our partner network to be the first line of support for their customers since they are in the best position to help answer questions and troubleshoot their solutions which include Impinj products. If the Impinj Authorized Partner needs help to resolve their end-customer requests, they should contact Impinj Support for assistance.

PRODUCT RETURNS (RMA)

Impinj utilizes the support process to handle all requests for product returns. Once a customer has created a new support case, a CSE will work with the customer to jointly troubleshoot the issue for products under warranty.

Initial Limited Hardware Warranty and Extended Warranty

If the product is determined to be faulty, the CSE will authorize the customer to ship it back to Impinj. Once we receive and verify that the product is defective, we will either send the customer a new replacement product, credit the customers account, or ship the product back to the customer after it is repaired. We currently do not offer a repair service for products whose warranty has expired. The standard RMA process generally takes 2-4 weeks to complete.

END OF SUPPORT/END OF LIFE

As products reach their End of Life (no longer for sale) and End of Support (no longer supported by Impinj), notices will be posted in the Customer Notifications section of each product family on the Support Portal. For more details, please visit the appropriate link below:

Reader/Gateway Customer Notifications

Software Customer Notifications

Monza Customer Notifications

Indy Customer Notifications

SUMMARY OF SUPPORT OFFERINGS

The following tables outline our current support offerings:

Reader/Gateway

Software

Category/Item

Standard Warranty

Extended Warranty

ItemSense/ ItemEncode

Term

1 year

1, 2, or 3 year

1-year Subscription

Reader/Gateway RMA

RMA request initial response time

48 hours (Mon-Fri)

48 hours (Mon-Fri)

N/A

Part replacement shipped

After defective unit is received by Impinj and analysis completed

After defective unit is received by Impinj and analysis completed

N/A

Firmware/Software/Licenses

Development library updates (e.g. Octane SDK, LTK, ItemSense libraries)

Included

Included

Included

ItemSense/ItemEncode updates

N/A

N/A

Included

Minor firmware updates (e.g. 5.10 to 5.12)

Available through Impinj Authorized partner

Available through Impinj Authorized partner

Included

Major firmware updates (e.g. 4.12 to 5.0)

Available through Impinj Authorized partner

Available through Impinj Authorized partner

Included

Speedway Connect license

Not Included

Not Included

N/A

Round Rock license

Not Included

Not Included

N/A

Support

Support portal self-help access

Included

Included

Included

Email support (in English)

4:00am-5:00pm PT (Mon-Fri)

4:00am-5:00pm PT (Mon-Fri)

4:00am-5:00pm PT (Mon-Fri)

Initial response time for non-RMA requests

48 hours (Mon-Fri)

48 hours (Mon-Fri)

48 hours (Mon-Fri)

Supported firmware, development libraries, and software versions

Current release only

Current release only

Current release only

Monza

Indy

Category/Item

Wafer

Packaged Parts

Chip/Module

Term

See terms and conditions

1 year

1 year

RMA

RMA request initial response time

48 hours (Mon-Fri)

48 hours (Mon-Fri)

48 hours (Mon-Fri)

Part replacement shipped

After defective unit is received by Impinj and analysis completed

After defective unit is received by Impinj and analysis completed

After defective unit is received by Impinj and analysis completed

Firmware/Software/Licenses

Development library updates (e.g. IndyMAC, IRI )

N/A

N/A

Included

Minor firmware updates

N/A

N/A

Included

Major firmware updates

N/A

N/A

Included

Support

Support portal self-help access

Included

Included

Included

Email support (in English)

8:30am-5:00pm PT (Mon-Fri)

8:30am-5:00pm PT (Mon-Fri)

8:30am-5:00pm PT (Mon-Fri)

Initial response time for non-RMA requests

48 hours (Mon-Fri)

48 hours (Mon-Fri)

48 hours (Mon-Fri)

Supported firmware, development libraries, and software versions

Current release only

Current release only

Current release only

When you configure and run Impinj Speedway Connect on-reader software, as described in Support Article: Speedway Connect System Configuration,data is outputted as tags are read by the reader or gateway. Here we describe the data format to enable you to develop your application to consume the data stream. Because of the portable nature of the data format, your code can be rewritten in virtually every modern programming language and development tool.

Impinj Speedway Connect outputs RAIN RFID data in two different formats, JSON or Key-Value Pair. As of Impinj Speedway Connect release 2.4.0, all three different operating modes are supported, namely, Inventory, Location, and Direction.

Depending on the output format and the operating mode, the data created by Impinj Speedway Connect will vary. To illustrate this, sample data was captured reading 3 tags with EPC's999908290000000000000004,999908290000000000000003, and999908290000000000000001by runningan Impinj xArray RAID RFID gateway in each of the 3 operating modes.

In Location mode, confidenceData provides a list of key/values. Only the values for key=130 and key= 136 are used by applications. These applications calculate the location of a tag when read by multiple Impinj xArrays.

These data formats are common among all types of Impinj Speedway Connect output channels, namely, HTTP Post, TCP/IP socket, Serial, keyboard emulation, and USB Flash Drive.

Operating Mode

Output Data Format: JSON

Output Data Format: Key-Value Pairs

Inventory (All Models)

{"antennaPort":7,"epc":"999908290000000000000004","firstSeenTimestamp":"2018-06-14T00:15:54.36879Z","peakRssi":-51,"isHeartBeat":false}

{"antennaPort":23,"epc":"999908290000000000000003","firstSeenTimestamp":"2018-06-14T00:15:54.373293Z","peakRssi":-50,"isHeartBeat":false}

{"antennaPort":25,"epc":"999908290000000000000001","firstSeenTimestamp":"2018-06-14T00:15:54.410799Z","peakRssi":-62,"isHeartBeat":false}

Format:

<AntennaPort>,<EPC>,<FirstSeenTImestamp>,<PeakRSSI>

Example:

44,999908290000000000000003,2018-06-14T00:19:31.289654Z,-5

34,999908290000000000000001,2018-06-14T00:19:31.523961Z,-58

19,999908290000000000000004,2018-06-14T00:19:31.845250Z,-52

Location (xArray)

{"epc":"999908290000000000000004","lastSeenTime":"2018-0614T00:54:18.305623Z","type":"update","xCm":23,"yCm":189,"confidenceWeight":9842,"confidenceData":[130,2519697,131,2519697,132,12,133,19,134,42565,135,6,136,6]}

{"epc":"999908290000000000000001","lastSeenTime":"2018-06-14T00:54:23.269842Z","type":"update","xCm":-7,"yCm":187,"confidenceWeight":4247,"confidenceData":[130,1087483,131,1087483,132,12,133,17,134,76099,135,13,136,13]}

{"epc":"999908290000000000000003","lastSeenTime":"2018-06-14T00:54:23.272192Z","type":"update","xCm":22,"yCm":226,"confidenceWeight":19769,"confidenceData":[130,5061030,131,5061030,132,12,133,17,134,74480,135,13,136,13]}

999908290000000000000004,2018-06-14T00:52:41.483983Z,update,24,201,23249,130,5951772,131,5951772,132,12,133,20,134,53800,135,13,136,13

999908290000000000000001,2018-06-14T00:52:46.485955Z,update,-4,185,4535,130,1161084,131,1161084,132,12,133,17,134,60387,135,13,136,13

999908290000000000000003,2018-0614T00:52:46.516607Z,update,25,233,21337,130,5462377,131,5462377,132,12,133,17,134,31382,135,13,136,13

Direction

(xArray) -

the 3 tags transitioned between sectors 4 and 8

{"epc":"999908290000000000000004","type":"exit","tagPopulationStatus":"ok","firstSeenTime":"2018-06-14T21:44:44.541582Z","lastSeenTime":"2018-06-14T21:44:50.162242Z","firstSeenSector":4,"lastSeenSector":8}

{"epc":"999908290000000000000003","type":"exit","tagPopulationStatus":"ok","firstSeenTime":"2018-06-14T21:44:44.866000Z","lastSeenTime":"2018-06-14T21:44:50.276220Z","firstSeenSector":4,"lastSeenSector":8}

{"epc":"999908290000000000000001","type":"exit","tagPopulationStatus":"ok","firstSeenTime":"2018-06-14T21:45:07.15372Z","lastSeenTime":"2018-06-14T21:45:11.558981Z","firstSeenSector":8,"lastSeenSector":4}

999908290000000000000003,2018-06-14T21:53:03.545328Z,2018-06-14T21:53:06.860999Z,exit,4,8,ok

999908290000000000000004,2018-06-14T21:53:03.97411Z,2018-06-14T21:53:07.471791Z,exit,4,8,ok

999908290000000000000001,2018-06-14T21:53:31.725254Z,2018-0614T21:53:36.758286Z,exit,8,4,ok

When sending data over HTTP, additional data is provided for the HTTP server to identify which reader or gateway is communicating with it.

JSON

Key-Value Pairs

{ "reader_name": "xarray-xx-xx-xx","mac_address":"XX:XX:XX:XX:XX:XX","tag_reads":[ <data stream described above> ]}

The POST variables sent by Speedway Connect:

reader_name: The name assigned to the reader in Speedway Connect

mac_address: The MAC address of the reader

line_ending: Line ending character specified in Speedway Connect

field_delim: Field delimiter character specified in Speedway Connect

field_names: A list of field names, separated by the specified delimiter

field_values: <data stream described above>

Testing the Output

Once Impinj Speedway Connect is configured and before developing your application, you will want to see the data as it is generated. Here are a few options to try when testing Impinj Speedway Connect and developing software to consume data.

1) TCP/Socket Output

The simplest method is to open a TCP/IP connection to the reader using an SSH program such as PuTTY.

Step 1) Make sure that in the Speedway Connect configuration page, under "Output: Connection" has the following setup. For how to access the Speedway Connect configuration page, see Support Article: Speedway Connect System Configuration. Also select the data output format: JSON or Key-Value Pairs.

server-side php script

"Output: Connection" in the Speedway Connect configuration page

"Output: Data" in the Speedway Connect configuration page

Step 2) Start Impinj Speedway Connect and make sure that the "Status" string at the top is green after the "Apply"string is clicked.

Top bar - Speedway Connect configuration page

Step 3) Connect to Impinj Speedway RAIN RFID readers or gateways using an SSH client program. Here we use PuTTY:

Step 4) Press the "Open" button to start the SSH session and now you should see the live data stream assuming that there are tags in the antenna's field of view.

2) HTTP Post in JSON Output Data Format

To examine the HTTP Post output sent from Impinj Speedway Connect, please try the following:

Step 1) In the Impinj Speedway Connect configuration page, under "Output : Connection", turn on the HTTP Post checkbox, and under "Output : Data", select the JSON output format.

"Output : Connection" in the configuration page

"Output: Data" in the configuration page

Step 2) Use the following Python program to display the HTTP post data

You can view HTTP post traffic from Impinj Speedway Connect with a short python script.

1) Install Python 2.7 or greater

2) Install Flask by typing command: pip install Flask

3) Save this file shown below as PostServer.py

from flask import Flask, request

app = Flask(__name__)

@app.route('/connect', methods = ['POST', 'GET'])

def message():

if request.method == 'POST':

app.logger.info('Request received.')

app.logger.info('Url: %s', request.url)

app.logger.info('Data: %s', request.data)

app.logger.info('Is JSON: %s', request.is_json)

else:

app.logger.info('GET request received.')

return 'OK\n'

if __name__ == '__main__':

app.run(host='0.0.0.0', port='5000', debug=1)

PostServer.py

4) run command:python PostServer.py to see the HTTP post output.

Best Practices

Make sure that the port (default 5000) accepts inbound traffic so adjusting the firewall on your computer may be necessary.

The HTTP post interval (default 300 seconds) can be lowered to say 10 seconds so you will not have to wait very long for the data to appear.

3) Parsing Key Value Pair HTTP Post Data

Thisparses the POST data and insert it into a relational database.

To output Key-Value Pairs data, remember to set the output format correctly in "Output : Data" in the Speedway Connect configuration page.

"Output : Data: in the Speedway Connect configuration page

Developing an Application

The most popular method today is to develop an application that receives HTTP posts in JSON format. This method is supported by all major programming languages and a wide variety of programming tools are available. Since HTTP post is a standard approach to sending data over the internet, Impinj Speedway Connect can post data up to a cloud application without the concern of being blocked by a firewall.

Download Speedway Revolution GPIO Box Datasheet

Overview

Impinj designed the Speedway Revolution GPIO Box for usewith the Speedway Revolution reader to provide convenientaccess to the readers GPIO (General Purpose Input/Output)port. The GPIO Box interfaces with the reader via a suppliedHD15 cable, and separates each input and output signal toeasy-access screw terminals. Neighboring ground and powerterminals accompany each signal terminal to easily connectthree-wire devices. The GPIO Box also includes an on-boardrelay to interface with devices require high wattage or anopen/short signal.

Features

Easy-access screw terminals

Power and ground terminals for each input and output

Each output can provide 250mA at 24V with optionalexternal universal power supply

SPDT Relay output capable of 5A at 240VAC

Ability to use reader-supplied 5V for low power digitalapplications, including the SPDT Relay

Highly visible LED indicators for each input andoutput eases troubleshooting and diagnostics

Access to readers RS-232 serial interface

ETSI EN 302 2018-1 v3.1.1, Radio Frequency Identification Equipment operating in the band 865 MHz to 868 MHz with power levels up to 2 W and in the band 915 MHz to 921 MHz with power levels up to 4 W, will be revised to allow UHF RFID operation using three channels over 916.1-918.9 MHz with 4 W ERP and 400 kHz TX bandwidth and without using DAA (detect and avoid). The changes are documented in Commission Implementing Decision (EU) 2018/1538 of 11 October 2018 and will be incorporated into ETSI EN 302 208-1 v3.2.1 targeted for release in 4Q 2019.

Acceptance of EU 2018/1538 varies by country. The following table summarizes Impinjs understanding of country acceptance as of June 2019. Impinj recommends contacting the countrys communications ministry for confirmation.

Status

Country List

Accepted

Bulgaria, Croatia, Czech Republic, Denmark, Finland, Hungary, Lithuania

Accepted with special conditions

Austria (lower 2 channels only), Belgium (lower 2 channels only), Switzerland (pending decision)

Acceptance anticipated in 2019

Estonia, France, Ireland, Latvia, Luxembourg, Malta, Poland, Portugal, Romania, Spain, Sweden, UK

Under consideration

Cyprus, Greece, Italy

Not accepting

Germany, Netherlands

Speedway Connect is licensed software that runs on the Impinj Speedway Revolution readers and gateways to enable users to easily plug-in RFID technology extending the reach of this powerful data collection technology. The simplified graphical user interface enables even those unfamiliar with RFID to set basic reader configurations. Data is passed to the PC application in keystrokes (English only) via USB-HID, serial, Ethernet or Web delivery for RFID deployment without costly software development or middleware expenses.

Download Speedway Connect Latest Release

Documentation:

Latest Released Version: 2.8.0

Required Reader / Gateway Firmware Version: - Octane FW 5.12.3 or later : Download Here (For Impinj Partners)

Supported Browsers: - Google Chrome - Mozilla Firefox - Microsoft Edge - Internet Explorer 11

Product Brief

Product Capabilities

Installing / Upgrading

Getting Started

Training Videos (For Impinj Partners)

Troubleshooting Steps

Data Integration

User Guide:

The user guide is embedded in the application. To access, click on the "?" icon on the right side of each section within the application. Here's an example:

HTTP Post Demonstration:

Keyboard Wedge Demonstration:

Download Indy Development Platform Quick Start Guide

This guide provides steps and tips to help you quickly begin operating your Indy Reader Development Platform. All the components necessary to begin inventorying RFID tags are included in the kit.

The remainder of the development platform files are available here.

Out of the box, Impinj doesn't provide a Windows 7 64bit native USB driver for the Indy Development Platform. So in the event that you receive a development board configured for USB, you will not be able to communicate to it from a Windows 7 machine. In this video we will demonstrate the procedure to convert the Indy Development Platform from the USB mode to the UART mode so that it will operate properly on a Windows 7 64 bit operating system.

You will need to download the UART.bin file below.

Download UART.bin

Sam-Ba can be downloaded here:

Download Sam-Ba

(For following along with these instructions, we'd advise using an older version of Sam-Ba as the latest versions don't include a GUI. We have used version 2.16 without issue).

Use this table to find the RoHS/REACH documentation available for each Impinj product.

Reader ChipsReader ModulesDevelopment Kits

Product

RoHS

REACH

Document

Impinj R2000 (IPJ-R2000)

Download

Impinj R500 (IPJ-R500)

Download

Product

RoHS

REACH

Document

Impinj RS2000 (IPJ-RS2000-GX, IPJ-RS2000-EU)

Download

Impinj RS1000

Download

Impinj RS500 (IPJ-RS500-GX, IPJ-RS500-EU)

Download

Product

RoHS

REACH

Document

Impinj R2000 and R500 Development Kits (IPJ-E3002, IPJ-E3003)

Download

Impinj RS2000, RS1000, and RS500 Development Kits

Not Available

Download Indy RS1000 Hardware User's Guide

Indy RS1000 is a completely integrated surface-mount RAIN RFID reader module. The Indy RS1000 surface-mount module improves on the Indy RS500s capabilities with a significant increase in read performance. Existing Indy RS500 users will be able to quickly offer higher performance with their existing hardware due to RS1000's drop-in compatibility. It can be easily added to an embedded system, requiring only connections to a power source, digital communication with a host, and an antenna. The package design allows it to be attached to a PCB using standard surface mount technology (SMT), with no need for additional connectors or mounting hardware. The Indy RS1000 is the easiest way to embed RAIN RFID reader capability.

This is the Indy RS1000 Hardware User's Guide. It provides detailed descriptions of the RS1000's behavior, including IOs and state diagrams. It also describes the operation of the RS1000 Development Kit and applicable regulatory information. The most recent version of this document is version 1.0.

For an overview of the RS1000, see the RS1000 Datasheet.

For more of the files associated with the RS1000 Development Kit, see the RS1000 Development Kit Files.

The Octane SDK is a development library that support C# and Java applications for Impinj RAIN RFID readers and gateways. This library uses the Octane LTK as a base library. The Octane SDK enables a much easier software development experience than the Octane LTK and is highly recommended to be installed and used for your customized RAIN RFID applications.

Documentation:

Latest Released Version: 3.0.0

Download, Install, and/or Upgrade

Required Reader / Gateway Firmware Version: - Octane FW 6.0 or later : Download Here (For Impinj Partners)

Supported Versions: - .NET Standard 2.0 (for which .NET Core 2.0 is a popular runtime) - Java 8

Setting up Octane SDK Java with Eclipse

Setting up Octane SDK Java with Netbeans

.NET Example for properly connecting to our readers and gateways

Training Videos (For Impinj Partners)

Download Older Versions

This page explains how to install the Octane SDK for .NET and the Octane SDK for Java.

Additional Octane SDK information can be found on the Octane SDK Product Page.

Click the tabs below to read how to install the Octane SDK .NET and Java versions of the library.

Octane SDK .NET Octane SDK Java

Octane SDK .NET

Download Octane SDK .NET

Download Octane SDK .NET Release Notes

Current release:

3.0.0

Starting with the Octane SDK .NET version 2.26.1 and LTK .NET version 10.26.1, Impinj is providing these libraries via NuGet.org. NuGet is the package manager for the Microsoft development platform.

The .NET SDK supports .NET Standard 2.0 for which .NET Core 2.0 is a popular runtime.

The examples showing how to use the library are included with the library package.

In order to download the latest Octane SDK .NET and LTK .NET, choose a method and follow the steps outlined below.

Method 1: Download libraries directly from Visual Studio

Method 2: Download libraries via web browser

Method 1: Download Octane SDK and Impinj LTK libraries directly from Visual Studio

Note: If your Visual Studio is older than 2012, please upgrade to the latest version or use Method 2.

1) Launch Visual Studio and open your current SDK or LTK project. If this is the first time downloading the SDK or the LTK, create a new project in Visual Studio.

2) In Solution Explorer, right click on the project name and select Manage NuGet Packages...

3) In the next page, click on Browse at the top left corner, enter "llrp" in the search field, and press the Enter key.

Download previous Octane SDK Java Releases

You will see the Octane SDK and the LTK packages, such as below.

4) Click on the library you want to download. Install button becomes activated toward right. You can confirm the contents of the package, as shown below.

Note: Make sure to check Dependencies(in the red rectangle above) before you install the Octane SDK or the LTK.

In this example, the Octane SDK requires .NET framework4.6.1or newer. If your current project is using .NET framework that is older than 4.6.1, you may receive an error as below.

If you receive an error similar to the above screenshot, you will need to change your project's Target framework to 4.6.1 or newer.

5) Click Install button to start installation.

6) You will be asked to accept the license terms. Review the license then click the I Accept button to proceed.

7) When successful, you will see a message similar to the following screenshot in the Output window:

Successfully installed 'OctaneSDK x.xx.x' to 'your_project_name'

Note: Now that you have installed the Library, you can navigate to the packages folder and load the example package into Visual Studio so you can run them if that was what you were intending to do.

Changing Project's Target Framework

1) In the Solution Explorer, right click on your project name and select Properties.

2) Select Application in the left column.

3) In Target framework dropdown, select .NET Framework 4.6.1

Method 2: Download Octane SDK and Impinj LTK libraries via web browser

If you want to download the Octane SDK Nuget package without Visual Studio to obtain the libraries, sample code, and documentation, you will need to download the following 3 packages:

Octane SDK package

LLRP LTK.NET package

SSH.NET package

Note: If you use Visual Studio, we recommend that you use method 1 above.

To download these packages, follow the steps below.

1) Visit the Impinj NuGet page andclick OctaneSDK link. Octane SDK package page opens.

2) Click Manual Download link in Info section to download the nupkg file (e.g. octanesdk.2.28.0.nupkg) to your computer.

3)On the same page, click onSSH.NETlink under Dependencies section. SSH.NET package page opens.

4) ClickManualDownloadlink in Info section to download the nupkg file to your computer (you may choose to download newer version of the SSH.NET package, which is compatible with the Octane SDK).

5)Go back to the Impinj NuGet page page, and clicklibltknet-sdklink. LLRP LTK.NET page opens.

6)ClickManualDownloadlink in Info section to download the nupkg file to your computer.

7) Once you downloaded all 3 package files,open the archives using 7-Zip or similar zip utility (e.g. 7-Zip is available on http://www.7-zip.org/ ).

8) Once unzipped, the content of the Nuget package should be similar to the following:

octanesdk.x.xx.x.nupkg

libltknet-sdk.xx.xx.x.nupkg

ssh.net.xxxx.x.x.nupkg

9) Copy 'Docs', 'Examples', and 'lib' folders inoctanesdk.x.xx.x.nupkg file into the desired folder on your PC.

10)Open 'lib' folder, then open 'net461' folder, copy and paste the following 2 files into the parent folder (=lib folder), and delete 'net461' folder: - Impinj.OctaneSdk.dll - Impinj.OctaneSdk.XML 11) Open libltknet-sdk.xx.xx.x.nupkg, and open 'lib' folder, then open 'net461' folder. 12) Copy and paste the following 2 files into the 'lib' folder in step 10 above. - LLRP.dll - LLRP.Impinj.dll 13) Open ssh.net.xxxx.x.x.nupkg. 14) Open 'lib' folder, then open 'net40' folder. 15) Copy and paste the following 2 files into the 'lib' folder in step 10 above. - Renci.SshNet.dll - Renci.SshNet.xml

At this point, you should have something similar to the following:

Now you are ready to start using the latest Octane SDK .NET.

Download previous Octane SDK .NET Releases

Octane SDKJava

Download Octane SDK Java Bundles and Examples

Current release:

3.0.0

This is the latestreleasedversion of Octane SDK libraries for Java. Please read EULA prior to using software.

The Java SDK supports Java 8.

Instructions for using Octane SDK Java with one of the following IDE:

Eclipse

Netbeans

Using Octane SDK Java with Command Line:

1) Open a command window and check the Java JDK Version to ensure you have version 1.8.

2)Download Octane SDK Java zip file. Download into a folder on your system (e.g. c:\temp\JavaSDK)

3) Extract the zipfile

4) Buildthe Octane SDK Java Samples:

Note: For linux systems, replace the semicolon (;) with a colon (:) in the classpath

c:\temp\javaSDK\samples> javac com\example\sdksamples\*.java -classpath ..\lib\OctaneSDKJava-1.22.0.30-jar-with-dependencies.jar;.

5)Execute the SDK Java Samples:

XX-XX-XX is based on your Reader's Mac address

Make sure to specify the full name of the jar file and stay away from wildcards.

Note: For linux systems, replace the semicolon (;) with a colon (:)in the classpath

c:\temp\javaSDK> java -Dhostname=speedwayr-XX-XX-XX -classpath ..\lib\OctaneSDKJava-1.22.0.30-jar-with-dependencies.jar;. com.example.sdksamples.ReadTags

The output will look like:

Connecting

log4j:WARN No appenders could be found for logger org.apache.mina.filter.executor.ExecutorFilter).

log4j:WARN Please initialize the log4j system properly.

Applying Settings

Starting

Press Enter to exit.

EPC: 3008 33B2 DDD9 0140 0000 0000 Reader_ip: xarray-XX-XX-XX.impinj.com antenna: 1

EPC: 3008 33B2 DDD9 0140 0000 0000 Reader_ip: xarray-XX-XX-XX.impinj.com antenna: 1

EPC: 3008 33B2 DDD9 0140 0000 0000 Reader_ip: xarray-XX-XX-XX.impinj.com antenna: 1

5)Get rid of the log4j warning messages:

Create a log4jproperties file (e.g. c:\temp\javaSDK\samples\log4j.properties) with the following contents to save to a log file:

# Root logger option

log4j.rootLogger=INFO, file

# Direct log messages to a log file

log4j.appender.file=org.apache.log4j.RollingFileAppender

log4j.appender.file.File=C:\\temp\\javaSDK\\log.out

log4j.appender.file.MaxFileSize=10MB

log4j.appender.file.MaxBackupIndex=10

log4j.appender.file.layout=org.apache.log4j.PatternLayout

log4j.appender.file.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n

Define log4j.configuration on the java command line:

c:\temp\javaSDK\samples> java -Dlog4j.configuration=file:log4j.properties -Dhostname=speedwayr-XX-XX-XX -classpath ..\lib\OctaneSDKJava-1.22.0.30-jar-with-dependencies.jar;. com.example.sdksamples.ReadTags

6)Look at all of the Octane SDK for Java Samples

All of the Octane Java SDK samples can be seen by doing a directory listing on the samples folder:

C:\temp\JavaSDK\samples> dir com\example\sdksamples\*.java

Now you are ready to develop Octane SDK Java applications!

Download xArray Gateway Product Brief

Download xArray Gateway Datasheet

xArray RAIN RFIDGateway

The Impinj xArray gateway is a fixedinfrastructure RAIN RFID reader system thatprovides always-on, wide-area monitoring, location, and direction of items.

Real-time Item IntelligenceImproves Visibility

Designed for large-scale, item-level applications inretail, healthcare, and manufacturing, the xArray gateway provides real-time Item Intelligence eventsincluding an items identity, location, and movement.Improve customer service, increase employeeproductivity, and make better business decisions.

Supported Regions or Geographies

Download xSpan Gateway Product Brief

Download xSpan Gateway Datasheet

The Impinj xSpan gateway reduces business operational costs and maximizes salesby providing constant, accurate inventory visibility, reducing loss and minimizing timespent locating and tracking items.

Ideal for inventory management, asset tracking anddock door solutions in retail, healthcare, and supplychain, the xSpan gateway simplifies RAIN RFID readerinstallation and management, lowering the totalcost of infrastructure ownership.

xSpan Use Cases

Movement Detection -enhances front store and back storeinventory management enabling lossprevention and exit detection solutions

Asset Tracking -increases asset availability while reducinglabor costs and inefficiencies due tomanual cycle counts

Production Monitoring -improves efficiency by ensuring accuratematerial flow from receiving, throughproduction, and out dock doors

xSpan Benefits

Easy to Deploy and Use -suite of configuration anddevelopment tools simplifiesreader management

High Performance -continuous peak performancethrough built-in automation

Reduces Operational Costs -provides constant visibility ofinventory and asset movement

Support Regions and Geographies

Download xPortal Gateway Product Brief

xPortal RAIN RFIDGateway

The Impinj xPortal fixed-infrastructure RAIN RFIDreader system provides hands-free inventory monitoring and asset tracking within linear spaces.

Inventory Management,Always-On Asset Tracking

The lightweight and low profile xPortal gatewaysolves the size and mounting limitations of traditionalportals, making it ideal for monitoring items, pallets or equipment passing through doorways, hallways, dockdoors or other zonal coverage areas.

Supported Regions or Geographies

The Impinj LLRP Toolkit (LTK) provides Microsoft .NET, Java, C++, and C libraries for development of applications requiring low level control of Impinjreaders and gateways using the EPCglobal Low Level Reader Protocol (LLRP) v1.0.1.

This library is intended for use as a base library with the Octane SDK. For a much easier software development experience, it is highly recommended that you use the Octane SDK instead.

Click to download the specific library:

Download LTK .NET (v10.34.0) via NuGet.org*

Download LTK Java (v10.34.0)

Download LTK C++ Linux (v10.34.0)

Download LTK C (v10.34.0)

Download LTK Definion Files (v10.30.0**)

Notes

*NuGet instructions here

**LTK definition files (v10.30.0) are compatible with all LTK 10.34.0 releases.

For the LTK C and C++ Linux libraries, we support Ubuntu 14.04 only.

Documentation for the latest Octane firmware release including the following:

Download Reader Installation & Operations Guide

Download Reader and Gateway Embedded Developers Guide

Download Octane SNMP Guide & MIBs

Download Reader How-To: Health Monitoring

Download Octane LLRP Guide

Download Impinj LTK Programmers Guide

Download Impinj RShell Reference Manual

Download Octane Firmware Upgrade Reference Manual

Download Reader CAD Drawings

View Reader and Gateway FAQ

Download Speedway Revolution Quick Start Guide

This guide provides simple steps to quickly start using your newSpeedway Revolution reader. For a full description of connectionmethods, reader configuration and system setup options, pleaseconsult the latest Speedway Installation and Operations Manual and other documentation.

The Speedway Revolution reader is suitable for use in Environmental Air Handling Space (EAHS) in accordance with Section 300-22(c) of the National Electric Code.

Cables, antennas, power adaptors, PoE (Power Injectors), or other devices shall not be installed in the Environmental Air Handling Space unless they are suitable for use in the EAHS per UL 2043.

LTK .NET LTK Java LTK C++ LTK C LTK Def

Here are previous versions of released LTK .NET libraries.

Download LTK .NET (10.16.0)

Download LTK .NET (10.20.0)

Download LTK .NET (10.22.0)

Download LTK .NET (10.24.1)

Download LTK .NET (10.26.0)

Download LTK .NET (10.26.1)

Download LTK .NET (10.28.0) and later via NuGet

Here are previous versions of released LTK Java libraries.

Download LTK Java (10.16.0)

Download LTK Java (10.20.0)

Download LTK Java (10.22.0)

Download LTK Java (10.24.1)

Download LTK Java (10.26.0)

Download LTK Java (10.26.1)

Download LTK Java (10.28.0)

Download LTK Java (10.30.0)

Download LTK Java (10.32.0)

Here are previous versions of released LTK C++ libraries.

Linux

Download LTK C++ Linux (10.20.0)

Download LTK C++ Linux (10.22.0)

Download LTK C++ Linux (10.24.1)

Download LTK C++ Linux (10.26.0)

Download LTK C++ Linux (10.26.1)

Download LTK C++ Linux (10.28.0)

Download LTK C++ Linux (10.30.0)

Windows*

Download LTK C++ (10.16.0)

Download LTK C++ Windows (10.20.0)

Download LTK C++ Windows (10.22.0)

Download LTK C++ Windows (10.24.1)

Download LTK C++ Windows (10.26.0)

*NOTE: LTK C++ Windows library is now End of Life

Here are previous versions of released LTK C libraries.

Download LTK C (10.16.0)

Download LTK C (10.20.0)

Download LTK C (10.22.0)

Download LTK C (10.24.1)

Download LTK C (10.26.0)

Download LTK C (10.26.1)

Download LTK C (10.28.0)

Download LTK C (10.30.0)

Here are previous versions of released LTK Impinj Definition Files.

Download LTK Impinj Definition Files (1.14)

Download LTK Impinj Definition Files (10.20.0)

Download LTK Impinj Definition Files (10.22.0)

Download LTK Impinj Definition Files (10.24.1)

Download LTK Impinj Definition Files (10.26.0)

Download LTK Impinj Definition Files (10.26.1)

Download LTK Impinj Definition Files (10.28.0)

For the latest supported libraries, please visit this page.

Note:

For the LTK C and C++ Linux libraries, we support Ubuntu 14.04 only.

Here are the previous released versions of Octane SDK.

For the latest supported libraries, please visit this page.

Octane SDK .NET Octane SDK Java

Previous Octane SDK .NET versions:

Download Octane SDK for .NET version 2.0.2

Download Octane SDK for .NET version 2.2.0

Download Octane SDK for .NET version 2.20.0

Download Octane SDK for .NET version 2.24.1

Download Octane SDK for .NET version 2.26.0

Download Octane SDK for .NET version 2.26.1

Download Octane SDK for .NET version 2.28.1 and later (via NuGet)

Previous Octane SDK Java versions:

Download Octane SDK for Java version 1.20.2

Download Octane SDK for Java version 1.24.1

Download Octane SDK for Java version 1.26.0

Download Octane SDK for Java version 1.26.1

Download Octane SDK for Java version 1.26.2

Download Octane SDK for Java version 1.28.0.1

Download Octane SDK for Java version 1.30.0.0

Download Octane SDK for Java version 1.32.1

Summary:

Impinj, Inc. (Impinj) has signed a license agreement with Round Rock Research, LLC (Round Rock). Under the terms of the agreement, Impinjs FCC UHF RFID Speedway Revolution readers (Readers) purchased after October 1, 2013 may be licensed under RFID patents and applications owned by Round Rock as of October 1, 2013 (Round Rock Patents). This license extends to Impinjs xPortal and xArray Portals (Portals) which include Readers (collectively, Readers or Portals).

To obtain a license under the Round Rock Patents for Readers or Portals:

(1) U.S. Retail Between October 1, 2013 and April 1, 2015: If you purchased a Reader or Portal after October 1, 2013 but before April 1, 2015, and the Reader or Portal is used at a retail or brand-owner site in the U.S., then those specific Readers and Portals are already licensed under Round Rock Patents. You will need to provide Impinj with the serial numbers of the Readers and Portals to complete registration.

(2) U.S. Retail After April 1, 2015: If you purchased a Reader or Portal after April 1, 2015, and the Reader or Portal is used at a retail or brand-owner site in the U.S., then you are required to purchase from Impinj a license under Round Rock Patents for that specific Reader or Portal. Contact Impinj for details.

(3) U.S. but outside U.S. Retail, after October 1, 2013: If you purchased a Reader or Portal after October 1, 2013 and the Reader or Portal is used within the U.S. but outside U.S. Retail then you may (but are not required to) purchase, from Impinj, a license under Round Rock Patents for that specific Reader or Portal. Contact Impinj for details.

(4) Outside U.S.: Round Rocks license agreement with Impinj neither specifically addresses nor requires licenses for Readers or Portals used outside the U.S. Consequently, Impinj does not offer licenses under the Round Rock Patents for Readers or Portals used outside the U.S.

(5) Prior to October 1, 2013: Round Rocks license agreement with Impinj neither specifically addresses nor requires licenses for Readers or Portals purchased prior to October 1, 2013. Consequently, Impinj does not offer licenses under the Round Rock Patents for Readers or Portals purchased prior to October 1, 2013.

The Round Rock license agreement additionally requires the end user (U.S. retailer, U.S. brand owner, or other user) to use at least 80% licensed UHF RFID readers and at least 80% licensed UHF RFID tags. Inlay manufacturers may obtain a license from Round Rock for the Round Rock Patents.

Frequently Asked Questions:

Does the license purchase requirement or opportunity apply equally to Readers and Portals?

Yes. For the purpose of licensing, you should treat Readers and Portals identically.

Am I required to purchase a license for Readers or Portals purchased after April 1, 2015 for use in U.S. Retail?

Yes. In addition, failure to purchase a license is a breach of your reseller agreement with Impinj and cause for termination. Impinj is not responsible for any Round Rock infringement claims relating to unlicensed Readers or Portals purchased after April 1, 2015.

Am I required to purchase a license for Readers or Portals purchased after October 1, 2013 but before April 1, 2015 for use in U.S. Retail?

No. Your Reader or Portal is already licensed under Round Rock Patents. However, you are required to provide Impinj with the serial numbers of the applicable Readers and Portals to complete registration.

Am I required to purchase a license for Readers or Portals purchased after October 1, 2013 for use in the U.S. but outside U.S. Retail?

No. Impinjs agreement with Round Rock does not require that Readers or Portals used within the U.S. but outside U.S. retail be licensed. However, if you want a license then you may purchase one as described above. Unlicensed usage is at your organizations and the end users sole risk.

Can I purchase a license for Readers or Portals purchased prior to October 1, 2013?

No. Round Rocks license agreement with Impinj neither specifically addresses nor requires licenses for Readers or Portals purchased prior to October 1, 2013.

Can I purchase a license for Readers or Portals used outside the U.S.?

No. Round Rocks license agreement with Impinj neither specifically addresses nor requires licenses for Readers or Portals used outside the U.S.

Can I use unlicensed UHF RFID tags with licensed Readers or Portals?

Yes, but you are responsible for ensuring that tags, systems, and methods do not infringe the Round Rock Patents. If your use of unlicensed UHF RFID tags in systems or methods infringe the Round Rock Patents then your use of licensed Readers or Portals with the tags is unlicensed by Round Rock. Impinj advises using licensed tags with license Readers or Portals in U.S. retail applications.

Do I need to obtain a separate license from Round Rock?

You should obtain advice from legal counsel and may contact Round Rock directly. As of the date of this FAQ, Round Rock was offering licenses to reader and inlay manufacturers.

How will I know whether my UHF RFID tags are licensed under the Round Rock Patents?

You will need to contact your tag or inlay supplier.

How can I check whether my Impinj Reader or Portal is licensed under the Round Rock Patents?

Contact Impinj Support to check the license status of your Reader or Portal.

How long are U.S. retail applications expected or required to use licensed readers and licensed tags under the Round Rock patents?

Until the last of the licensed Round Rock patent expires, anticipated some time in 2019.

Do I have to sign a new reseller agreement with Impinj?

If you are an existing North American partner as of 01-April-2015 then our Channel Team will assist you with signing an updated reseller agreement. For new partners signing after 01-April-2015, the reseller agreement will address Round Rock licensing directly.

Disclaimer:

The foregoing information is provided by Impinj in good faith and is not legal advice. Other than identifying which individual Impinj Readers or Portals have been licensed under Round Rock Patents, nothing in the foregoing shall be construed as any representation, warranty, liability or obligation of Impinj.

Certified Reader ProductsCertified Gateway Products

The following table outlines the different regions and geographies where each Impinj reader is certified. [Note 1]

Approved Reader Part Numbers

Region

R120 (1-port)

R220 (2-port)

R420 (4-port)

Australia

N/A

N/A

GX3

Brazil

N/A

GX1

GX1

Canada

USA

USA

USA

China

GX2

GX2

GX2

European Union

EU1

EU1

EU1 (865-868 MHz) EU2 (915-921 MHz) [Note 2]

Hong Kong

N/A

GX1

GX1

India [Note 3]

EU1

EU1

EU1

Japan

N/A

N/A

JP2

Malaysia

N/A

GX1

GX1

Mexico

USA

USA

USA

New Zealand

N/A

GX1

GX1

Philippines

N/A

N/A

GX1

Saudi Arabia

EU1

N/A

EU1

Singapore [Note 4]

N/A

GX1

GX1

South Africa

GX2

GX2

GX2

South Korea

N/A

N/A

GX2

Taiwan

N/A

GX1

GX1

Thailand

N/A

GX1

GX1

UAE

EU1

EU1

EU1

Uruguay

N/A

GX1

GX1

USA (FCC)

USA

USA

USA

Vietnam

N/A

N/A

GX1

Note 1: Subject to change. Certification means having a LLRP region identification number and a regulatory certificate where required. Regulatory certification is voluntary in some countries. N/A indicates there is no certification for that device and therefore this product cannot be used in that region.

Note 2: Conforms with Article 3.1(b) of EN 301 489-3 v2.1.1 and Article 3.2 of EN 302 208 v3.2.1 Draft 2019-01. Visit this page for more details about the acceptance of this new standard by specific EU countries.

Note 3: Must be purchased from authorized India distributor.

Note 4: Users in Singapore are required to obtain a license for each use case where the radiated power during operation is between 500mW and 2000mW. Contact the local regulatory authority (IDMA or ARFM respectively) to obtain a license.

To ensure regulatory compliance, professional installers / integrators must follow the transmit power setting instructions provided in the Installation and Operations Guide. Impinj recommends readers should be used with the antennas listed in Appendix A of the Installation and Operations Guide or with antenna(s) of the same type with equal or less gain. RFID Integrators should contact the regulatory agency in the country where equipment is to be used to determine if their RFID system requires any additional testing/certification.

The following table outlines the different regions and geographies where each Impinj gateway is certified. [Note 1]

Approved Gateway Part Numbers

Region

R640 (xPortal)

R660 (xSpan)

R680 (xArray)

Australia

GX3

GX3

GX3

Brazil

GX1

GX1

GX1

Canada

FCC

USA

USA

China

GX2

N/A

GX2

European Union

EU1

EU1 (865-868 MHz) EU2 (915-921 MHz) [Note 2]

EU1 (865-868 MHz) EU2 (915-921 MHz) [Note 2]

Hong Kong

GX1

GX1

GX1

India [Note 3]

N/A

EU1

EU1

Japan

N/A

JP2

JP2

Malaysia

GX1

GX1

N/A

Mexico

FCC

USA

USA

New Zealand

GX1

GX1

N/A

Philippines

N/A

N/A

N/A

Saudi Arabia

N/A

EU1

EU1

Singapore [Note 4]

N/A

GX1

GX1

South Africa

GX2

GX2

GX2

South Korea

GX2

N/A

GX2

Taiwan

GX1

GX1

GX1

Thailand

GX1

GX1

N/A

UAE

N/A

EU1

EU1

Uruguay

N/A

N/A

N/A

USA (FCC)

FCC

USA

USA

Vietnam

N/A

N/A

N/A

Note 1: Subject to change. Certification means having a LLRP region identification number and a regulatory certificate where required. Regulatory certification is voluntary in some countries. N/A indicates there is no certification for that device and therefore this product cannot be used in that region.

Note 2: Conforms with Article 3.1(b) of EN 301 489-3 v2.1.1 and Article 3.2 of EN 302 208 v3.2.1 Draft 2019-01. Visit this page for more details about the acceptance of this new standard by specific EU countries.

Note 3: Must be purchased from authorized India distributor.

Note 4: Users in Singapore are required to obtain a license for each use case where the radiated power during operation is between 500mW and 2000mW. Contact the local regulatory authority (IDMA or ARFM respectively) to obtain a license.

To ensure regulatory compliance, professional installers / integrators must follow the transmit power setting instructions provided in the Installation and Operations Guide. Impinj recommends readers should be used with the antennas listed in Appendix A of the Installation and Operations Guide or with antenna(s) of the same type with equal or less gain. RFID Integrators should contact the regulatory agency in the country where equipment is to be used to determine if their RFID system requires any additional testing/certification.

This article contains previously released versions of Impinj ItemTest software.

For the latest supported release, please visit this page.

Please consult the User Guide accessible from Help within the application for detailed documentation on how to use this software.

Download ItemTest Software v1.12.3 & Release Notes

Download ItemTest Software v1.10.0 & Release Notes

Download ItemTest Software v1.8.0 & Release Notes

Download ItemTest Software v1.6.1 & Release Notes

Download ItemTest Software v1.6.0 & Release Notes

Download ItemTest Software v1.4.1 & Release Notes

Download ItemTest Software v1.2.0 & Release Notes

Download Impinj Software End-User License Agreement (EULA)

IMPINJ, INC. - SOFTWARE END-USER LICENSE AGREEMENT

PLEASE READ THIS SOFTWARE END-USER LICENSE AGREEMENT (AGREEMENT) CAREFULLY BEFORE USING THE 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 AND ANY EQUIPMENT PROVIDED BY IMPINJ IN CONNECTION THEREWITH ("EQUIPMENT") UNUSED IN THE ORIGINAL SHIPPING CONTAINER TO THE PLACE OF PURCHASE FOR A FULL REFUND. 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 License Materials, except to the extent: (a) there is a separate signed agreement between you and Impinj governing your use of the Software; or (b) the Software includes a separate click-accept license agreement as part of the installation and/or download process. To the extent of a conflict among the provisions of the foregoing documents, the order of precedence is: (i) the signed agreement; (ii) the click-accept agreement; and (iii) this Agreement.

Software may be provided by Impinj on a standalone basis to be installed on computer hardware that is not provided by Impinj (Standalone Software) or it may be provided as software or firmware embedded in Equipment (Embedded Software).

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 the Standalone Software, in object code format only, on computer hardware for which all corresponding license fees have been paid and only in conjunction with Licensees proper use of Impinjs applicable hardware products (including hardware products branded with Impinjs trademarks) with which the Standalone Software was designed to interface; (ii) use one (1) copy of the Embedded Software, in object code format only, solely as embedded in Equipment, each solely in accordance with the Documentation for Licensees 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 or Equipment, (ii) sell, rent, lease, loan, provide, distribute or otherwise transfer all or any portion of the Licensed Materials (except as set forth in Section 1(f)), (iii) reverse engineer, reverse assemble or otherwise attempt to gain access to the source code of all or any portion of the Licensed Materials or Equipment, (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 or Equipment, (vi) use any component of the Software or Equipment other than solely in conjunction with operation of the Software and as applicable, Equipment, (vii) unbundle any component of the Software or Equipment, (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 or Equipment 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 Standalone 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. Further, use of any Update for Embedded Software is limited to the Equipment for which Licensee holds a valid license to use the Software which is being updated. (e) Impinj shall have the right to inspect and audit Licensees use, deployment, and exploitation of the Licensed Materials for compliance with the terms and conditions of this Agreement. (f) Licensee shall have the right to transfer the Embedded Software as embedded in Equipment in connection with a transfer of all of Licensees right, title and interest in such Equipment to a third party; provided, that, Licensee transfers the Embedded Software and any copies thereof subject to the terms and conditions of this Agreement and such third party agrees in writing to be bound by all the terms and conditions of this Agreement. (g) Licensee acknowledges that the Software contains or is provided with copyrighted software of Impinjs suppliers as identified in associated documentation or other printed or electronic materials ("Third Party Software") which are obtained under a license from such suppliers. Licensees 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 or Equipment shall be Impinjs 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 Licensee and Impinj. In addition, Impinjs 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 Impinjs confidential information in confidence and use the same degree of care, but in no event less than reasonable care, to avoid disclosure of Impinjs confidential information as it uses with respect to its own confidential and proprietary information of similar type and importance. Licensee agrees to only disclose Impinjs confidential information to its directors, officers and employees who have a bona fide need to know solely to exercise Licensees rights under this Agreement and to only use Impinjs confidential information incidentally in the customary operation of the Software and Equipment. Licensee shall not sell, license, sublicense, publish, display, distribute, disclose or otherwise make available Impinjs 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. IMPINJS 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 LICENSEES 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. Licensees 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 IMPINJS 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 EQUIPMENT, OR FOR BREACH OF THIS AGREEMENT. IMPINJS TOTAL LIABILITY ARISING OUT OF OR UNDER THIS AGREEMENT, OR USE OR INABILITY TO USE THE LICENSED MATERIALS OR EQUIPMENT, OR FOR BREACH OF THIS AGREEMENT, WHETHER IN CONTRACT, TORT (INCLUDING WITHOUT LIMITATION NEGLIGENCE), STRICT LIABILITY OR OTHERWISE, SHALL NOT EXCEED THE PRICE PAID FOR THE SOFTWARE (FOR THE STANDALONE SOFTWARE) AND THE PRICE PAID FOR THE EQUIPMENT (FOR THE EMBEDDED SOFTWARE AND EQUIPMENT). 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 (except as expressly set forth in Section 1(f)). 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.

Download Impinj Software Tools License Disclaimer

PLEASE READ THE FOLLOWING LICENSE & DISCLAIMER (AGREEMENT) CAREFULLY BEFORE USING ANY SOFTWARE TOOLS (AS DEFINED BELOW) MADE AVAILABLE TO YOU (LICENSEE) BY IMPINJ, INC. (IMPINJ). BY USING THE SOFTWARE TOOLS, YOU ACKNOWLEDGE THAT YOU HAVE READ AND UNDERSTOOD ALL THE TERMS AND CONDITIONS OF THE AGREEMENT, YOU WILL BE CONSENTING TO BE BOUND BY THEM, AND YOU ARE AUTHORIZED TO DO SO. IF YOU DO NOT ACCEPT THESE TERMS AND CONDITIONS, DO NOT USE THE SOFTWARE TOOLS.

1. PURPOSE OF AGREEMENT. From time to time, Impinj technical personnel may make available to Licensee certain software, including code (in source and object form), tools, libraries, configuration files, translations, and related documentation (collectively, Software Tools), upon specific request or to assist with a specific deployment. This Agreement sets forth Licensee's limited rights and Impinj's limited obligations with respect to the Software Tools. Licensee acknowledges that Impinj provides the Software Tools free of charge. This Agreement does not grant any rights with respect to Impinj standalone software products (e.g., ItemSense, ItemEncode, SpeedwayConnect) or the firmware on Impinj hardware, all of which are subject to separate license terms.

2. LIMITED LICENSE. Subject to the terms and conditions of this Agreement, Impinj hereby grants to Licensee a limited, royalty-free, worldwide, non-exclusive, perpetual and irrevocable (except as set forth below), non-transferable license, without right of sublicense, to (a) use the Software Tools and (b) only with respect to Software Tools provided in source code form, modify and create derivative works of such Software Tools, in each case, solely for Licensees internal development related to the deployment of Impinj products (Purpose). The Software Tools may only be used by employees of Licensee that must have access to the Software Tools in connection with the Purpose.

3. TERMINATION. Impinj may immediately terminate this Agreement if Licensee breaches any provision hereof. Upon the termination of this Agreement, Licensee must (a) discontinue all use of the Software Tools, (b) uninstall the Software Tools from its systems, (c) destroy or return to Impinj all copies of the Software Tools and any other materials provided by Impinj, and (d) promptly provide Impinj with written confirmation (including via email) of Licensees compliance with these provisions. Sections 4-10 will survive termination of this Agreement.

4. OWNERSHIP. The Software Tools are licensed, not sold, by Impinj to Licensee. Impinj and its suppliers own and retain all right, title, and interest, including all intellectual property rights, in and to the Software Tools. Except for those rights expressly granted in this Agreement, no other rights are granted, either express or implied, to Licensee. Impinj reserves the right to develop, price and sell software products that have features similar to or competitive with Software Tools. Licensee grants Impinj a limited, royalty-free, worldwide, perpetual and irrevocable, transferable, sublicensable, license to Licensees derivative works of Software Tools; provided that Licensee has no obligation under this Agreement to deliver to Impinj any such derivative works.

5. CONFIDENTIALITY. In order to protect the trade secrets and proprietary know-how contained in the Software Tools, Licensee will not decompile, disassemble, or reverse engineer, or otherwise attempt to gain access to the source code or algorithms of the Software Tools (unless Impinj provides the Software Tools in source code format). Licensee will maintain the confidentiality of and not disclose to any third party: (a) all non-public information disclosed by Impinj to Licensee under this Agreement and (b) all performance data and all other information obtained through the Software Tools.

6. WARRANTY DISCLAIMER. LICENSEE ACKNOWLEDGES THAT IMPINJ PROVIDES THE SOFTWARE TOOLS FREE OF CHARGE AND ONLY FOR THE PURPOSE. ACCORDINGLY, THE SOFTWARE TOOLS ARE PROVIDED AS IS WITHOUT QUALITY CHECK, AND IMPINJ DOES NOT WARRANT THAT THE SOFTWARE TOOLS WILL OPERATE WITHOUT ERROR OR INTERRUPTION OR MEET ANY PERFORMANCE STANDARD OR OTHER EXPECTATION. IMPINJ EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, QUALITY, ACCURACY, AND FITNESS FOR A PARTICULAR PURPOSE. IMPINJ IS NOT OBLIGATED IN ANY WAY TO PROVIDE SUPPORT OR OTHER MAINTENANCE WITH RESPECT TO THE SOFTWARE TOOLS.

7. LIMITATION OF LIABILITY. THE TOTAL LIABILITY OF IMPINJ ARISING OUT OF OR RELATED TO THE SOFTWARE TOOLS WILL NOT EXCEED THE TOTAL AMOUNT PAID BY LICENSEE TO IMPINJ PURSUANT TO THIS AGREEMENT. IN NO EVENT WILL IMPINJ HAVE LIABILITY FOR ANY INDIRECT, INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF THESE DAMAGES. THESE LIMITATIONS WILL APPLY NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY IN THIS AGREEMENT.

8. THIRD PARTY SOFTWARE. The Software Tools may contain software created by a third party. Licensees use of any such third party software is subject to the applicable license terms and this Agreement does not alter those license terms. Licensee may not subject any portion of the Software Tools to an open source license.

9. RESTRICTED USE. Licensee will comply with all applicable laws and regulations to preclude the acquisition by any governmental agency of unlimited rights to technical data, software, and documentation provided with Software Tools, and include the appropriate Restricted Rights or Limited Rights notices required by the applicable U.S. or foreign government agencies. Licensee will comply in all respects with all U.S. and foreign export and re-export laws and regulations applicable to the technology and documentation provided hereunder.

10. MISCELLANEOUS. This Agreement will be governed by the laws of the State of Washington, U.S.A without reference to conflict of law principles. All disputes arising out of or related to it, will be subject to the exclusive jurisdiction of the state and federal courts located in King County, Washington, and the parties agree and submit to the personal and exclusive jurisdiction and venue of these courts. Licensee will not assign this Agreement, directly or indirectly, by operation of law or otherwise, without the prior written consent of Impinj. This Agreement (and any applicable nondisclosure agreement) is the entire agreement between the parties relating to the Software Tools. No waiver or modification of this Agreement will be valid unless contained in a writing signed by each party.

How can I setup readers or gateways to automatically upgrade their firmware?

You can configure readers and gateways to upgrade automatically using an upgrade configuration metafile stored on your network. Please see Octane Firmware Upgrade Reference Manual for setup.

Do Impinj readers and gateways come pre-loaded with the software that makes them function or do I need to install software after purchase?

Impinj pre-installs all its readers and gateways with a supported version of Impinj firmware called Octane. Application software based on ItemSense software, Speedway Connect, or an Impinj provided library (e.g. Octane SDK ) controls the reader or gateway can be developed toautomatethe users application.

Do readers and gateways function differently based on the region or geography for which they are deployed?

Readers and gateways operate in frequencies and power levels to comply with different regulations from various telecom regions around the globe. In accordance with the GS1 EPC Gen2 specification, UHF RFID operates within the 860 to 960 MHz band worldwide.Frequency allocations, maximum allowed transmit power, and reader to tag communication techniques vary by country. For information about how readers and gateways operate worldwide, please see Regulatory status for using RFID in the EPC Gen2 (860 to 960 MHz) band of the UHF spectrum.

What regulatory standards and regions have Impinj readers and gateways been certified for?

The latest, up-to-date list can be found on the Supported Regions and Geographies page.

What industry standards do the readers and gateways comply with? (e.g. GS1, ISO, etc.)

All Impinj fixed readers and gateways comply with the GS1 Low Level Reader Protocol (LLRP) standard for application interfaces, and with relevant industry standards including the ISO/IEC 18000-63 standard and the EPC Radio-Frequency Identity Protocols Generation-2 UHF RFID specification.

What are some examples of how readers and gateways are used?

For a wide range of solutions from different industries please see: http://www.impinj.com/solutions/

Are your readers and gatewayscompatible with all generation 2 RFID tags?

Yes, readers and gateways are compatible with all EPC Generation-2 UHF RFID based tags.In addition to standard Gen 2 RFID tag functionality, readers and gateways firmware can take advantage of special Impinj Monza tag features such as Fast ID for high performance TID reads, Tag Focus for high performance portal applications, and Margin Read to insure tag encoding quality.

What are the read ranges for readers and gateways?

Read range is primarily a function of the reader, the antenna, and tag.A broad range of antennas and tags are available from Impinj and other third parties to enable nearly any use case. Other factors that can influence tag read range include the transmit power, antenna cable, reader mode, and other readers in the area. See RFID Link Budget Whitepaper.

For example, a Speedway reader paired with a MatchBox antenna and a near-field tag yields a read range of 3.5 cm for very short range use cases. A Speedway paired with a Brickyard antenna and a near-field tag yields a 1 m read range for short range use cases including retail point-of-sale terminals. A Speedway paired with a far-field antenna and a large far-field tag can yield a read range exceeding 10 m.

Impinj gateways feature integrated electronic beam steering that expands the coverage area further. The xArray gateway covers up to 1500 ft^2 (140 m^2), the xSpan up to 1000 ft^2 (93 m^2) and the xPortal gateway up to 700 ft^2 (65m^2).

Do reader and gateways provideenhancedread range capabilities?

Impinj readers and gateways offer industry-leading receive sensitivity and customreader modesthat maximize read range. Also, all gateways have aphased array antenna thatcreates linear polarized beams which obtain superior read range and coverage area over tradition fixed reader antennas.

Which programming languages should I use when developing software applications that communicate with readers and gateways?

The programming language depends on the software or library used. See options in the table below:

ItemSense Software

Octane SDK library

Speedway Connect

LTK Library

ETK Library

StandardsREST and Rabbit MQ

Wide variety of languages based on standards

C# .NET,

Java

StandardHTTP Post, TCP/IP socket, serial port

Wide variety of languagesbased on standards

C, C++, C# .NET, Java

C, C++

On-Reader application example

How do readers and gateways communicate with a host computer or server?

Individual readers and gateways are networked together via Ethernet connections. Each one incorporates a 10/100 BASE-T jack. The LLRP protocol is sent to the reader or gateway over a TCP/IP connection. Additionally, SSH and HTTP based communication is used for reader management.

Can I use Wi-Fi or Bluetooth with readers and gateways?

Neither Wi-Fi or Bluetooth are included in reader or gateway hardware. However, an external Wi-Fi bridge adapter can provide wireless LAN connectivity if the use case requires it. See Using a Wi-Fi bridge with Speedway readers and xPortal gateways.

Can I use any Power Supply that meets the electrical specifications to power a reader or gateway?

No, readers and gateways are to be powered ONLY with our Impinj listed/certified power supply. Use of an alternative power supply will invalidate any approval given to the device and may be dangerous.Alternatively, readers and gateways can be power by PoE switches that meet the IEEE 802.3afstandard. For more information on Impinj Power supplies and PoE switches, please see the xArray/xSpan Installation and Operations Guide and the Speedway Revolution Operations and Installations Guide.

What measures does Impinj put in place to prevent outside parties from reading information on RFID tags?

Several measures are available to secure Impinj readers and gateways: IEEE 802.1x for port-based network access control (MD5, PEAP, MSCHAPv2), encryption of inbound LLRP connections, and SNMP version 3 for remote management for readers and gateways.

What is the read accuracy of readers and gateways?

Read accuracy is a function of many factors including tag choice, environment, as well as placement and configuration of the readers. Most of our case studies cite greater than 95% - 99% read accuracy.

Do readers or gateways also support barcode reading?

No, readers and gateways do not currently support barcode reading.

Do readers and gateways provide the necessary environmental protection to operate outdoors or in a hazardousenvironment?

Readers and gateways are designed to operate in dry temperature-controlled environments. Gateways have an IP 50 rating and Speedway has an IP 52 rating. Also, the Speedway and gateways operating temperature range is -20C to 50C.

Operating in a hazardous environment will require an enclosure that does not interfere with the RF signals.Impinj does not provide any recommendation on specific enclosures at this time.

Besides temperature and moisture, what environmental restrictions should I consider when installing a gateway?

The gateway needs to be installed in a space where the RF signals are not blocked by nearby (within a few feet) metal or lighting. See xArray/xSpan Deployment Guide for more details.

Can readers and gateways send and receive compressed data?

No, the LLRP protocol based data communication sent between the host application and the reader can not becompressed.

How does Impinj provide security patches for readers and gateways?

Impinj typically provides any security patch with a new release of firmware which can be loaded on any reader or gateway.

How are readers and gateways monitored for security violations and system health?

All detected exceptions including security and system errors are captured to a syslog which the user has access to.

What software architectures can I implement using Octane SDK?

Over the years a board range of software architectureshave been implemented by software and systems integratorsranging from on-reader applications, desktop applications that communicate with the gateway, middleware applications that communicate between the reader/gateway and enterprise systems, and cloud applications that collect data sent from a reader or gateway.

What type of hardware warranty does Impinj provide for readers and gateways?

Each Impinj reader and gateway carries an initial limited hardware warranty. The limited warranty lasts 1 year from the date of shipment to the buyer. You may purchase an Extended Warranty to extend the limited hardware warranty for one (1) two (2) or 3 (three) years after the expiration of the initial limited hardware warranty. The extended warranty must be purchased 90 days prior to the expiration of the initial limited hardware warranty; it applies to the specific reader only and is not transferable to other readers. Details are available for download at https://support.impinj.com/hc/en-us/articles/214095408-Product-Warranty-Options.

Use this table to find the EU Declaration of Conformity available for each Impinj product.

ReadersGateways

Product

Declaration of Conformity Document

IPJ-REV-R420-EU1

Download

IPJ-REV-R420-EU2

Download

IPJ-REV-R220-EU1

Download

IPJ-REV-R120-EU1

Download

Product

Declaration of Conformity Document

IPJ-REV-R680-EU1

Download

IPJ-REV-R680-EU2

Download

IPJ-REV-R660-EU1

Download

IPJ-REV-R660-EU2

Download

IPJ-REV-R640-EU1

Download

There are different standards that regulate the use of UHF RFID throughout the world. The two main regulations are: FCC and ETSI. Whilst the protocol remains the same, the frequency and technique to communicate with the tag are different. Here is a summary of the two main regulations:

Standard Name

Primary Regions of Operation

Frequency Range

R-->T Technique

Max Radiated Power

FCC

FCC part 15.247 & 15.249

North America

902-928 MHz

FHSS

4W EIRP

ETSI

EN 302 208-2 v2.1.1

Europe

865-868 MHz

4 channel plan

2W ERP

For more information regarding the regulations worldwide please refer to this EPC Global document. http://www.gs1.org/docs/epcglobal/UHF_Regulations.pdf and for more information about the differences between the measure of power please refer to EIRP and ERP article.

This post discusses the nuances of applications intended for deployment in ETSI regions. Within this region there are 4 transmit channels available (hence the name four channel plan) where the readercan transmit the maximum allowable power from the antenna (namely 2W ERP, 33dBm).

Selecting Specific Channels Using ETSI Regulations

Due to having significantly less channels, less power and less bandwidth per channel than in FCC regions, applications designed for ETSI regions often have toconsider channel selection.

Here are some basic best practice tips:

1.Ensure youre using the correct channels; use all four channels if you can; but this is not always possible due to other readers transmitting in close proximity; (if using ItemTest to test your reader, select Use Specified Frequencies in "Frequency Settings (ETSI Only)" section and select all 4 channels, as shown below)

See also: Selecting Specific Channels Using ETSI Regulations

2. If you have more than one reader in close proximity that will be operating at the same time thenalternate output channels; this can be important for times when two readers are used to create a portal or when two dock door portals are in close proximity. An example would be having reader A use channels 4 and 10 (865.7 & 866.9 MHz), and reader B using channels 7 and 13 (866.3 & 867.5 MHz) as shown in the diagrams below:

When readers are actively transmitting, if this separation of channels is not designed into the system there is a 25% chance that they will be transmitting at the same time; thereby increasing the chances if interference; and with it the chances of not reading tags.

3.Considerations if you have to use a single channel; ETSI regulations dictate that it is only permitted to transmit on a single channel for a certain period of time. 4 seconds if tags are being read and only one second if no tags are being read... if this happens then the reader must stop transmitting for a period of 100ms. The reader ensures it complies with the regulations automatically, therefore, its important, where possible, to ensure more than one channel is selected.

If you have more than two active readers in close proximity; careful consideration must be given to the design of the system. Which channels to use, separation of antennas, angle of antennas and how operation of the reader is triggered are all variables that can affect the operation of the RFID solution.Please also see this post to learn how to select specific channels when using ETSI readers:

The Indy R500, R1000, and R2000 Development Kits were designed to facilitate development of embedded systems using the Indy family of RFID reader chips. The development kits include a CD that contains documentation, software, and firmware to facilitate use of the kits. The contents of the CD are reproduced here for easy access.

Single zip file

Download Indy R500, R1000, & R2000 Development Kit CD Contents Image (Documentation and Software)

Individual files

Download Indy R1000 Development Kit Hardware

Download Indy R500 & R2000 Development Kit Hardware

Download Indy Development Platform Quick Start Guide

Download Indy R500, R1000, & R2000 Development Kit Interface Hardware

Download Indy R2000 PCB Schematic

Download Indy R1000 PCB Schematic

Download Indy R500 PCB Schematic

Download Indy Interface PCB Schematic

Note: The Indy reader Module Development Kits' downloads are documented here: RS500, RS1000, RS2000.

Download Conversion Application Note

Impinj is providing early notice to our Impinj Monza 5 tag chip customers of an upcoming change in product availability. Impinj will end-of-life (EOL) Impinj Monza 5 in 2020. This decision is intended to better match the supply of Impinj Monza 5 ICs with the natural drop in demand for a product that has been in the market since 2011, as most Impinj Monza 5 IC customers have moved to the more advanced Impinj Monza R6-P tag chip. In December 2019, Impinj will distribute a formal Impinj Monza 5 EOL product change notification, which will officially start the EOL process. We will follow the standardsemiconductor EOL process of allowing orders to be placed for the first six months of 2020, with our last shipment occurring at the end of 2020. For the needs of most Impinj Monza 5 customers, Impinj recommends converting existing solutions with Monza 5 tags to Monza R6-P tags, which boast a richer feature set for those applications. There are some exceptions in which the end user may gain more value from a different Impinj Monza 6 family endpoint IC, but for most scenarios, Monza R6-P is the best replacement option for Monza 5. This application note is a technical guide outlining the considerations for end users transitioning from Impinj Monza 5 to Monza R6-P. End customers should work closely with the inlay manufacturers to determine the best strategy for transitioning from Impinj Monza 5 tags to Monza R6-P tags.