Fixed UHF RFID Reader

At-a-glance — antenna ports, EIRP envelope and throughput

• 4-8 portsMonostatic antenna ports per reader
• +30 to +36 dBmEIRP per port (region-firmware dependent)
• 300-600 /secTag inventory throughput in dense-reader mode
• 25.5 WPoE+ (802.3at) at port under full load

Handheld-only workflow vs fixed-reader portal + dock-door array

Throughput benchmark — Auburn U RFID Lab + Impinj dense-reader published data

When a fixed UHF reader is the right choice

• Fixed-location throughput workflow (dock door, portal, overhead conveyor, retail ceiling array, yard gate, production-line checkpoint) where tagged goods pass a defined zone under the reader's RF field.
• High-tag-population inventory. A single FX9600 or R700 at +33 dBm can inventory 300-600 tags per second with a Q-algorithm optimised for crowd scenes; no handheld achieves that throughput.
• Continuous operation, network-integrated. Fixed readers run 24/7 on PoE+ or 12-24 V DC, stream tag events over LLRP / MQTT / Kafka to a middleware or cloud endpoint, and are managed from a central fleet controller (Impinj ItemSense, Zebra Savanna, or a custom IoT gateway).
• Regulatory-audited deployments: EU Tire Regulation (2024/1257) finished-tire-exit portals, FDA DSCSA pharmaceutical packaging, ATA Spec 2000 aerospace MRO and GS1 EPCIS track-and-trace all require fixed reader arrays for their enforcement zones.

Technical specification and configuration options

• Antenna ports — 4 port (R420, R700 base, FX9600 4-port, ALR-F800 4-port) or 8 port (R700-8, FX9600 8-port, ATR7000 overhead array). Monostatic (single antenna TX + RX) is standard; bistatic configurations available on CAEN A949EU for long-range outdoor yards.
• RF output power — +30 dBm (1 W) to +33 dBm (2 W) per port on EU firmware, up to +36 dBm (4 W EIRP with 6 dBi antenna) on FCC firmware per 47 CFR 15.247 limits. Software-adjustable per port.
• Antennas (sold separately) — 6 dBi circularly polarised near-field (Times-7 A5010, Laird S9028), 9 dBi CP far-field (MT-262013, Times-7 A6034), 12 dBi linear polarised long-range (MTI MT-263013, Laird S9028PCLJ), and overhead arrays (Zebra AN620, Impinj xArray-integrated).
• Host interface: GigE + PoE+ (802.3at, 25.5 W at port) on all modern readers, with Wi-Fi 5/6 on R700 firmware 1.11+ and FX9600 optional; serial console via USB-C for setup; GPIO for trigger / shift / light-tower integration.
• Power: PoE+ (25.5 W) or 24 V DC barrel jack. A fully-loaded 8-port R700 at maximum EIRP draws ~22 W; an 8-port FX9600 draws ~28 W; an ATR7000 overhead array draws up to 40 W and requires PoE++ (802.3bt) or external DC.
• Environmental: indoor IP51 standard (R700, FX9600, ALR-F800). IP65/IP67 outdoor variants (CAEN R1260I, Feig ISC.LRU3500-IP) for yard, gate and outdoor-portal deployments. Operating range -10 to +55 °C (standard), -20 to +60 °C (outdoor SKUs).
• On-reader processing: Impinj R700 ships with a 1.6 GHz dual-core Cortex-A9, 1 GB RAM and 4 GB flash for running edge-filter, tag-dwell and duplicate-suppression logic on the reader itself; Zebra FX9600 ships with an 800 MHz PowerPC and supports Java application development (Zebra RFID Application) for similar edge-processing.

Software, SDK and integration options

• LLRP (Low-Level Reader Protocol, ISO/IEC 19762). The open, vendor-neutral standard. Port 5084 TCP, binary message framing, RoSpec / AccessSpec / ROReport lifecycle. All readers in this catalogue ship with LLRP natively. Reference libraries: LTK (Java, C, C#, C++, Python), sllurp (Python), octane.llrp (Impinj), go-llrp (Go).
• Impinj Octane IoT Device Interface (IoT-DI). Higher-level REST + MQTT endpoints on R700 firmware 1.11+. The reader publishes tag-event JSON to an MQTT broker (Mosquitto, HiveMQ, AWS IoT Core) or Kafka topic without middleware. Recommended integration pattern for cloud-native deployments.
• Zebra RFID SDK for Android / C / Java / .NET. Cross-family SDK covering FX9600, FX7500 fixed plus RFD40, RFD90 handheld sleds. One API, two form factors. The main reason Zebra-shop deployments tend to stay Zebra end-to-end.
• CAEN RFID SDK / A927Z Library. Covers CAEN's R1260, A949EU and quattro series with LLRP extensions for bistatic antenna control and long-range dwell tuning.
• Feig FEDM (Feig Electronic Device Manager). Cross-platform C / C++ / Java / .NET SDK with full coverage of ISC.LRU3500 and the broader Feig fixed-reader portfolio including HF ISO 15693 vicinity readers used in libraries.
• Middleware integration: Impinj ItemSense, Zebra Savanna, CAEN easy2read, Barco ClickShare-for-RFID, Turck BL ident, and dozens of GS1 EPCIS-compliant platforms accept LLRP streams and upconvert to higher-level business events (aggregation, commissioning, shipping-confirmation).

Sampling, site survey and deployment steps

1. Step 1
   Pilot one reader + two antennas on the actual deployment geometry (real dock door, real portal width, real tagged goods) for at least one operating shift. Lab benchmarks overstate real-world range by 30-50%.
2. Step 2
   Capture baseline read-rate data with RSSI histograms. The raw tag-event stream tells you whether the antenna pattern matches the RF target, whether EIRP is adequate, and where blind spots live. Every Proud Tek pilot ships with the LLRP capture tooling needed.
3. Step 3
   Verify regional firmware during factory acceptance. The reader's model number does not tell you the firmware image; confirm the ETSI / FCC / SRRC image version before deployment.
4. Step 4
   Size PoE and network. A PoE+ switch must deliver 25.5 W per port under load; 15 W PoE (802.3af) throttles the radio and silently degrades range. A 4-reader cluster needs 4 × PoE+ ports plus VLAN segregation from general IT traffic.
5. Step 5
   Plan the firmware maintenance window. Readers need 1-2 firmware updates per year for bug fixes and regulatory compliance. Budget a monthly 5-minute outage per reader in the operational SLA.

Site survey → pilot → fleet rollout timeline

1. Week 1-3 — site survey + reader/antenna selection

   Walk-the-floor RF site survey: dock-door geometry, forklift interference, metal-reflective surfaces, PoE switch audit. Reader shortlist narrowed to 2-3 SKUs across Impinj / Zebra / CAEN / Feig per deployment country firmware requirement.

2. Week 4-8 — single-portal pilot with LLRP capture

   One reader + antenna set wired at real operating geometry. sllurp / LTK capture running for full shift; RSSI histograms + read-rate curves reviewed against business-rule threshold (typical dock-door target: ≥99.5 % per-case read confirmation).

3. Week 9-16 — multi-portal fleet buildout

   4-20 portals installed across the site, managed via Impinj ItemSense / Zebra Savanna or custom MQTT-to-Kafka ingest; LLRP ROReport stream upconverted to GS1 EPCIS 2.0 events for downstream WMS / ERP / regulatory audit.

4. Month 4-12 — full rollout + fleet governance

   Reference operating practice across retail-ceiling-inventory, logistics-dock-door, automotive-tire-exit-portal, aerospace-MRO-toolroom and pharmaceutical-DSCSA fixed-UHF-reader programmes.

FAQ