Indy RS500 is a completely integrated UHF reader SiP
(system-in-package). 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 RS500 is the easiest way to embed
UHF RFID reader capability.
For technical support, visit the Impinj support portal at support.impinj.com
Revision 1.1
For more information, contact readerchips@impinj.com
The Indy® RS500 reader SiP (system-in-package) is a completely integrated reader
solution for EPC Gen 2 / ISO18000-63 (formerly 18000-6C) applications. The Indy
RS500 was developed to make embedding UHF RFID reader capability easy. The Indy
RS500 builds on market-leading Indy reader chip technology and integrates all of the
necessary components into a small package. The Indy RS500 requires no external
components, is fully tested and meets regulatory requirements. The Indy RS500 comes
in a surface mount package designed to work as a SMT (surface mount technology)
compatible component in a standard PCB manufacturing process, which eliminates
costly mechanical hardware, RF cables and human assembly that are typically required
with embedded readers on the market today. The Indy RS500 is a turnkey solution that
will enable quick and easy embedding of RFID with low development risk and fast timeto-market.
Ideal for moderate read range of small tag populations, the Indy RS500’s small form
factor enables a diverse range of applications that need a low-cost embedded UHF
Gen 2 RFID reader capability, such as consumables authentication, access control,
process control, appliances, POS devices for retail, medical equipment, printers, and
low-duty handheld readers. The RS500 is capable of reading dozens of tags per second
at distances greater than 3 meters when using a 6 dBi reader antenna and far field
passive tags.
This document includes interface, functional, performance, mechanical and
environmental specifications. Host communication specifications (e.g. firmware upgrade
and host interface protocol) and Impinj Radio Interface (IRI) documentation is provided
in the latest RS500 Software release package. The Indy RS500 uses the IRI™ (Impinj
Radio Interface) to communicate with host systems. The IRI Tool Kit enables
developers to build on a variety of embedded host platforms by providing the following:
documentation, image loader, IRI library, sample C code and project files. The IRI Tool
Kit can be found in the latest Indy RS500 Software release package and can be
downloaded from the restricted documents and downloads section at
support.impinj.com. Please create an account and subscribe to receive automatic
updates to the latest documentation and releases. Contact your local Impinj
representative if you have trouble creating an account or accessing this site.
Maximum output power is 23 dBm
-65 dBm Rx sensitivity, assuming 15 dB antenna return loss
Inventory (FastID, Tag Population Estimate, Select, Session, Target)
Access (Read, Write, Lock, Kill, BlockPermalock, and QT)
Shielded to prevent unwanted radiation and provide noise immunity in embedded
environments
29 mm by 32 mm by 3.8 mm surface mount package with SMT compatibility
Single mono-static RF port
Field upgradability via firmware updates. Gen 2 v2 will be firmware upgradable.
Part of Impinj’s GrandPrix® platform, ensuring better performance when using
Impinj’s Monza® UHF RFID tag chips (enabling FastID, Tag Focus and QT)
UART serial interface using IRI (Impinj Radio Interface)
Test features (CW, PRBS, custom regions, channel lists, and fixed frequency)
3 System Block Diagram
An example Indy RS500 system-level block diagram for an embedded application is
shown in Figure 3-1. This figure shows the electrical connections that may and must be
made to control the RS500. In the figure, the required connections are illustrated with
solid lines. Recommended and optional connections are illustrated with different dotted
3.6 - 5.25 V
VDC_IN
UART1 RX & TX
RF
GND
Indy
RS500
SiP
NRST
WKUP
Host
GPIOs
Key
Required
Recommended
Test
Points
User
Def.
Optional
STATUS
&
HEALTH
UART2
RX
&
TX
GPIOs UC_ADC
&
UC_DAC
and dashed line patterns. They are also listed below.
For more detail on pin characteristics and behaviors, see the RS500 Hardware User’s
Guide.
Figure 3-1: Example RS500 Block Diagram
Required connections:
VDC_IN and GND are required to power the RS500.
RF is required to connect to the UHF RFID antenna.
UART1 Tx and Rx are required to communicate with the system host.
Recommended connections:
nRST is used to reset the RS500 if UART communication is not available. This
connection is highly recommended. This pin internally driven strong low during
software resets, so it should only be driven externally by an open drain signal. It
must not be driven strong high.
UART2 Tx and Rx may be used to examine debug information.
HEALTH indicates successful operation of the RS500. Connection to an LED
provides a visual indication of whether or not an error condition exists.
STATUS provides an indication when the RS500 is in active mode (for example,
inventorying tags). Connection to an LED provides a visual indicator of the device’s
activity.
The absolute maximum ratings (see Table 5-1) define limitations for electrical and
thermal stresses. These limits prevent permanent damage to the Indy RS500.
Operation outside maximum ratings may result in permanent damage to the device.
The Indy RS500 uses IRI to enable communications; this is enabled with the IRI Tool Kit.
The IRI Tool Kit includes documentation, IRI API, and sample C code. The IRI Tool Kit
is intended to enable a broad set of host platforms due to its ease of use and portability.
Communication with the RS500 via IRI occurs in two states:
1.
Configuration (synchronous)
a.
All communications are commands and responses
b.
Start and Stop commands cause transition to the Listen state
2.
Listen (asynchronous)
a.
Host is in a listening mode and polls to obtain tag reports
Customer applications can be enabled on a variety of embedded systems with hosts
ranging in size from small microcontrollers to large microprocessors. The IRI Tool Kit is
structured to ease portability by separating platform specific code from functional reader
operation; this is illustrated in Figure 6-1 below.
Please refer to the documentation included in the RS500 release package for complete
details on communicating with the Indy RS500 using IRI. The latest Indy RS500 release
package, which includes the IRI Tool Kit, can be downloaded at support.impinj.com.
6 Regulatory Information
The Indy RS500 (IPJ-RS500) has been certified for modular operation by FCC and
Industry Canada in certain specific configurations. Use of these IDs requires specific
text be added to product labeling and product Hardware User’s Guides. See the Indy
RS500 Hardware User’s Guide for more details on labeling specifics.
7 Package and Assembly Information
This section provides mechanical drawings and critical dimensions needed for PCB
layout and housing design, as well as SMT assembly information.
7.1 Package Mass
The mass of the RS500 SiP is 4.6 grams.
7.2 Package Dimensions
Package dimensions are shown in Figure 8-1 and Figure 8-2.
All dimensions are in millimeters.
Dimension tolerances (unless otherwise specified):
X = 1.0
X.X = 0.5
X.XX = 0.25
X.XXX = 0.125
Hole = 0.075
Angular: MACH 0.5
Bend: 1.0 Degree
Recommended footprint copper and pastemask dimensions are shown in Figure 8-3
and Figure 8-5. Dimensions for the individual pads are shown in Figure 8-4 and Figure
8-6.
Figure 8-3: RS500 Recommended Etched Copper Footprint – All Pads
Figure 8-6: RS500 Recommended Pastemask Footprint – Single Pad
It is important to note that the optimal pad and stencil design results in a stencil aperture
that is of a different shape than and that overhangs the etched pad. This design delivers
the optimum amount of solder to the castellation of the SiP pad. Figure 8-7 depicts the
pad/solder relationship.
Figure 8-7: Recommended Solder Stencil Opening with Etched Pad for RS500
of information in this document. Impinj reserves the right to change its products and
services and this information at any time without notice.
EXCEPT AS PROVIDED IN IMPINJ’S TERMS AND CONDITIONS OF SALE (OR AS
OTHERWISE AGREED IN A VALID WRITTEN INDIVIDUAL AGREEMENT WITH
IMPINJ), IMPINJ ASSUMES NO LIABILITY WHATSOEVER AND IMPINJ DISCLAIMS
ANY EXPRESS OR IMPLIED WARRANTY, RELATED TO SALE AND/OR USE OF
IMPINJ PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO
FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR
INFRINGEMENT.
NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY
PATENT, COPYRIGHT, MASK WORK RIGHT, OR OTHER INTELLECTUAL
PROPERTY RIGHT IS GRANTED BY THIS DOCUMENT.
Impinj assumes no liability for applications assistance or customer product design.
Customers should provide adequate design and operating safeguards to minimize risks.
Impinj products are not designed, warranted or authorized for use in any product or
application where a malfunction may reasonably be expected to cause personal injury
or death or property or environmental damage (“hazardous uses”) or for use in
automotive environments. Customers must indemnify Impinj against any damages
arising out of the use of Impinj products in any hazardous or automotive uses.
Indy is a trademark of Impinj, Inc. All other product or service names are trademarks of
their respective companies.
www.impinj.com
Federal Communication Commission Interference Statement
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two
conditions: (1) This device may not cause harmful interference, and (2) this device must
accept any interference received, including interference that may cause undesired operation.
This equipment has been tested and found to comply with the limits for a Class B digital
device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference in a residential installation. This equipment generates,
uses and can radiate radio frequency energy and, if not installed and used in accordance with
the instructions, may cause harmful interference to radio communications. However, there is
no guarantee that interference will not occur in a particular installation. If this equipment does
cause harmful interference to radio or television reception, which can be determined by
turning the equipment off and on, the user is encouraged to try to correct the interference by
one of the following measures:
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that
to which the receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
FCC Caution:
Any changes or modifications not expressly approved by the party responsible for
compliance could void the user's authority to operate this equipment.
This transmitter must not be co-located or operating in conjunction with any other
antenna or transmitter.
Radiation Exposure Statement:
This equipment complies with FCC radiation exposure limits set forth for an uncontrolled
environment. This module can be used with T800 or similar platform with similar dimension,
antenna location and RF characteristic.
This device is intended only for OEM integrators under the following conditions:
1) The antenna must be installed at the same location as tested in the certification filing, and
the maximum antenna gain allowed for use with this device is 4.41 dBi.
2) The transmitter module may not be co-located with any other transmitter or antenna.
3) For portable usage condition, this module has been SAR evaluated in T800 host with
compliance result and can be used with this specific host as described in the certification
filing. Other host or platform needs separate approval.
As long as 3 conditions above are met, further transmitter test will not be required.
However, the OEM integrator is still responsible for testing their end-product for any
additional compliance requirements required with this module installed
IMPORTANT NOTE: In the event that these conditions can not be met (for example certain
laptop configurations or co-location with another transmitter), then the FCC authorization is
no longer considered valid and the FCC ID can not be used on the final product. In these
circumstances, the OEM integrator will be responsible for re-evaluating the end product
(including the transmitter) and obtaining a separate FCC authorization.
End Product Labeling
The final end product must be labeled in a visible area with the following: “Contains FCC
ID: QYLRS500”. The grantee's FCC ID can be used only when all FCC compliance
requirements are met.
Manual Information To the End User
The OEM integrator has to be aware not to provide information to the end user regarding how
to install or remove this RF module in the user’s manual of the end product which integrates
this module. The end user manual shall include all required regulatory information/warning as
show in this manual.
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.