Indy RS2000 FAQ

The following is a list of questions and answers about the Indy RS2000 Reader Module.

There is also a Frequently Asked Questions in the ITK Release Documentation, which can be viewed on Impinj's developer site at

  1. What market is Impinj addressing with this product?

    Answer: This product was created to fill a market need for a high performance and easy to use embedded reader solution.  Target applications include: handhelds, POS solutions, smart appliances, shelf/portal/overhead readers and vehicle mounted readers to name a few.  Existing products on the market are either too big, low performance, require expensive mechanical hardware or too hard to use.  The RS2000 will make embedding RAIN RFID easy.

  2. What makes the Indy RS2000 a high performance reader engine?

    Answer: The Indy RS2000 leverages the market-leading performance of the Indy R2000 reader chip with exclusive Self-Jammer Cancellation Technology that ensures optimal receive sensitivity.  It also supports 31.5 dBm output power at up to 4 antenna ports which enables maximum read coverage even with lossy RF cabling or systems with low gain antennas.

  3. How does the Indy RS2000 support all global regions using RAIN RFID?

    Answer: The Indy RS2000 is available in 2 SKUs: IPJ-RS2000-1 (SKU1) and IPJ-RS2000-2 (SKU2).  SKU1 supports all FCC and EU (ETSI) regions.  SKU2 supports FCC, Japan and China.

  4. How is the Indy RS2000 designed to be mounted for optimal thermal performance?

    Answer: The Indy RS2000 is designed to be surface mounted on a PCB but can have several different thermal solutions depending on usage.  Please review the Indy RS2000 HW User's Guide for more details. 

    Here are 4 common options, also shown in the image below:

    • Surface mount the Indy RS2000 on a host PCB without heatsinking or a conducted path away from the module except the PCB.  This is recommended only for room temperature usage or at low duty cycles.
    • Surface mount with a heat sink directly below the RS2000 host PCB and use a screw through the module and PCB into the bottom heat sink.  The screw does provide a conducted path from the heatsink to the top metal of the module.  It should be noted that the screw does not provide thermal contact to the internal substrate of the module.
    • Surface mount with a sheet metal chassis connected to the RS2000 via a thermal block on the backside of the host PCB. The thermal block conducts heat to the sheet metal chassis, which absorbs and dissipates.
    • Surface mount with a machined chassis that makes direct contact with the backside of the host PCB. The machined chassis conducts heat well throughout, and has a high thermal capacity as well.


  5. Can the same SW/FW from the Indy RS500 be used on the Indy RS2000?

    Answer: No.  The Indy RS500 and Indy RS2000 use separate firmware images.  The IRI host library and API are the same but please read the release documentation to better understand functional differences.

  6. Is the Indy RS2000 a module?

    Answer: Yes, the RS2000 is a surface mount module. It contains all of the components of an RFID radio subsystem, mounted on a printed circuit board, with a metal shield. It is designed to be added to a device via soldering for electrical and mechanical connection. It is not integrated into a monolithic package, nor does it contain unpackaged die.

  7. What other components are needed to make a complete reader with the Indy RS2000?

    Answer: The Indy RS2000 does not require additional external components to function as a UHF RFID reader engine.  A user would need to provide DC power, a communication interface (UART) to a host and an RF antenna to build a functional reader engine.  As part of an embedded system, the reader engine would be accompanied by a host controller, peripherals, connectivity to external systems, power supply, and in many cases an embedded RAIN RFID antenna.

  8. Does the Indy RS2000 use the Indy R2000 reader chip?

    Answer: Yes.  The Indy RS2000 uses the market-leading Indy R2000 reader chip.

  9. How far can you read a tag with the Indy RS2000?

    Answer: This depends on a number of factors: reader antenna gain, reader antenna reflection properties, environmental factors (metal in the area), and tag performance.  Please keep in mind that tag performance can vary depending on the properties of the item being tagged.  We have measured a read range above 10 meters when operating at 30dBm output power with a 3dBi reader antenna and using the latest Smartrac Dogbone tag in free space.  Longer read range can be achieved with higher gain reader antenna usage.

  10. How fast can the Indy RS2000 read tags?

    Answer: The Indy RS2000 can read theoretically reader over 1000 tags per second.  In practice, most applications use the RS2000 in DRM (Dense Reader Mode) to improve noise immunity.  This limits tag read rates to 150-200 tags per second depending on tag population and inventory settings.

  11. How does a host interface with the Indy RS2000?

    Answer: The physical host interface to the Indy RS2000 is a serial UART port.  The logical interface is Impinj’s IRI (Impinj Radio Interface).  Impinj provides the IRI API in the ITK (IRI Tool Kit) release package.  The IRI Tool Kit includes the documentation, IRI API, libraries, and example code in C.  Please log into the Impinj support portal to request access at Contact your local Impinj representative for more information.

  12. How can I evaluate the Indy RS2000?

    Answer: Ordering an Indy RS2000 Development Kit (IPJ-E4001-1 or IPJ-E4001-2) is the best way to start your evaluation of the module.  The kit includes everything needed to start reading tags within 20 minutes.  The kit has the following components:

    • An RS2000 development board with access to all pins via headers, RF ports, and health/status LEDs
    • 2 antennas: near field for development and far field for performance testing
    • All necessary cabling and power supply
    • Tag samples
    • USB drive with documentation

    Please contact your local Impinj representative for ordering information.

Was this article helpful?
1 out of 1 found this helpful



Article is closed for comments.