A conventional overhead RFID read point is three purchases pretending to be one. There is a reader in a cabinet. There are antennas on coaxial runs out to wherever the coverage actually has to be. And there is a machine somewhere — a PC in the comms room, a VM, occasionally a laptop under somebody’s desk — running the middleware that turns a torrent of raw reads into the handful of events your WMS or ERP will accept.
The Identium ID-EA500 Edge Array Reader collapses those three into one 500 × 500 × 45 mm ceiling panel on a single PoE cable. An Impinj E710 reader IC, a 12 dBi integrated antenna array and a quad-core Linux edge controller share one enclosure, and the filtering, zone logic and direction detection happen on the unit before anything leaves it.
This post is about that architecture: what the collapse removes, what it does not, and when it is the wrong call. The full datasheet is here.
First, the boundary — because it decides everything else
The ID-EA500 gives zone-level presence and dwell, and direction of travel derived from RF phase. It does not give x, y coordinates across a floor. The datasheet says so in a box headed “Stated plainly”, and this is the third paragraph of a launch post because getting it wrong is the most expensive misunderstanding in overhead RFID.
The panel can tell you a pallet is in bay 4 rather than bay 5, that it has sat in inbound staging for forty minutes, and that a carton crossed the dock door outbound rather than inbound. It cannot tell you the pallet is 2.3 m from the east wall. Zone presence deliberately applies hysteresis and hold-times so items near a boundary do not flicker between areas — useful behaviour, and the opposite of coordinate tracking.
If your requirement really is coordinates, stop here and read our comparison of active RFID, BLE and passive UHF for RTLS. Passive UHF is the wrong radio for sub-metre positioning whoever makes the panel.
What collapsing three boxes actually removes
The antenna cabling design. On a conventional read point that is where the engineering time goes: route, length, loss, connector quality, a VSWR check per run. With the array behind the panel face, the coaxial run and everything that can go wrong along it are out of the job. One drop carries power and data.
The middleware host. The substantial one. Zone presence, direction, rules, alerts, dwell and expected-versus-found reconciliation all execute on the panel’s own controller, and the console that configures them is served by the unit. Nothing to install on a PC, no Windows machine to patch, and no single server whose reboot takes every read point down with it.
Two things that usually get skipped. If the network drops, events queue on board — up to 200,000 — and are delivered in order when the link returns. The datasheet specifies that buffer for HTTP POST and WebSocket, a distinction worth holding on to and one we return to below. And every unit dials out to ReaderSense MDM over an encrypted WebSocket, so an installed base is visible, diagnosable and updatable from one browser rather than by driving to sites.
What it does not remove
RF physics. A 12 dBi array on a ceiling is still a radio looking at tags on goods. Tag type, mounting height, the material behind each tag and the metal and liquid in the room decide what is read. The datasheet gives no read range and no coverage area, and we will not supply one — not even a “typical” one. Coverage is measured on your site, at your height, on your goods; our guide to scoping a project by read range and environment sets out what to measure. Nor does the panel rescue a badly chosen tag.
Ceiling and power planning. This is a half-metre square panel, not a small box, and each position needs a fixing and a clearance. The datasheet lists 802.3af and 802.3at with 802.3at recommended, so af-only switches are a budget line. There is also a 9–24 V DC input and optional Wi-Fi 5 or 4G LTE, so a panel can run without a data drop — but it still needs power. Wireless changes what the cable carries; it does not remove the cable. Two things the datasheet does not state, and that we are therefore not going to state either: a panel weight and an IP rating. If you are fixing to a suspended grid, or mounting in a cold room, a wash-down area or a dusty yard, ask us for both in writing before you specify.
Per-unit licensing. The licence is per unit, bound to the device by a signed key, so each panel needs its own. That makes it a per-panel line rather than a per-site one. No figure is published, so ask.
Tag writing. The datasheet lists continuous inventory with RSSI, phase and antenna per read. It lists no tag write, lock or kill function. Somebody still has to encode EPCs before any ceiling panel has something to find, and that remains a job for a desktop reader at an encoding bench.
Commissioning. Zones, hold-times, rules and alerts are configuration, and configuration is a visit by someone who knows what the settings mean for your goods and your traffic.
ReaderSense Edge is not the ReaderSense you may already know
Three products share a name, and the distinction matters in a specification.
ReaderSense — covered in a separate post — is the free cross-platform desktop application that ships with every Identium UHF reader, for setting up, tuning and operating a unit from a Windows or macOS machine.
ReaderSense Edge is pre-installed on the ID-EA500 and serves its own web console from the panel: live inventory with RSSI, antenna and last-seen; zone presence; direction of travel; rules and alerts driving relays, stack lights and webhooks; store-and-forward; dwell, counts, trends and reconciliation with CSV export; a Modbus RTU master over RS485; and admin, operator and viewer roles with a full audit trail.
ReaderSense MDM is the fleet layer: token enrolment, health telemetry (CPU, memory, disk, temperature, reader link, inventory state, tag count, upload queue), remote console access through the tunnel, and remote updates with automatic rollback if a unit does not come back.
Two details to design around. Store-and-forward buffering is specified for HTTP POST and WebSocket; MQTT 3.1.1 over TLS is a data-out option, but the on-board buffer is not claimed for it, so confirm that behaviour with us rather than building against an assumption. And for security review: the datasheet states data goes straight to your systems with no Identium account required, and separately that ReaderSense MDM is hosted by Identium — two different planes. The tunnel is outbound-only, with no inbound ports, no VPN and no firewall changes at site. If your policy requires the management plane on your own infrastructure, raise it before you specify.
Specifications
Drawn strictly from the datasheet.
| Reader IC | Impinj E710 |
| Air protocol | EPCglobal Gen2 / ISO/IEC 18000-63 |
| Frequency | 865–868 MHz (India); other regional plans configurable |
| Antenna | Integrated panel array, 12 dBi |
| RF output | Up to 33 dBm, software-adjustable |
| Read events | Continuous inventory with RSSI, phase and antenna per read |
| Edge controller | Quad-core 64-bit ARM up to 2.0 GHz · 1 TOPS NPU · 2 GB LPDDR4X · 32 GB eMMC + microSD |
| OS | Linux, ReaderSense Edge pre-installed |
| Network | 1 × 10/100/1000 Mbps RJ45; optional Wi-Fi 5 (2.4 / 5 GHz) or 4G LTE |
| Serial, USB, I/O | RS232 and RS485 · 2 × USB 2.0 host, 1 × USB-C, UVC camera support · 4 opto-isolated inputs, 4 outputs (3 relays) |
| Data out | REST API · HTTP POST · WebSocket · MQTT 3.1.1 (TLS) · webhooks · Modbus RTU · CSV export |
| Buffering | Store and forward on board (HTTP POST / WebSocket) |
| Fleet | ReaderSense MDM, hosted by Identium |
| Power | IEEE 802.3af / 802.3at PoE (802.3at recommended); 9–24 V DC input |
| Dimensions | 500 × 500 × 45 mm |
| Mounting | Ceiling suspension, or 4 × M6 rear inserts on a 416 × 300 mm pattern |
| Indicators | Integrated LED light bars |
| Environment | −25 °C to +65 °C, 5–95 % RH non-condensing (edge controller) |
| Licence | Per unit, bound to the device by a signed key |
Three readings worth making explicit. The NPU is silicon on the board; the datasheet claims no vision function built on it, and neither do we — there is no shipping vision feature here, so do not specify this panel against a vision requirement. The USB camera support is likewise an interface, not an application. And the temperature and humidity figures are stated for the edge controller, which is the qualification the datasheet attaches to them.
Why “up to 33 dBm” is a ceiling, not a running figure
India’s licence-exempt UHF RFID allocation is 865–868 MHz, set by the short-range-device rules notified as G.S.R. 853(E) on 10 December 2021, which expressly superseded the 2005 rules that had specified 865–867 MHz. That older figure is still widely quoted and is no longer the current allocation. Table IV of the 2021 rules permits 2 W e.r.p. interrogator power only in four channels of 200 kHz or less, centred at 865.7, 866.3, 866.9 and 867.5 MHz, with no more than four seconds of continuous transmission per channel and at least 100 ms between bursts on the same channel; the table references ETSI EN 302 208.
33 dBm is 2 W, which is why “up to 33 dBm, software-adjustable” is best read as a compliance control rather than a performance number. Two cautions follow. The 2 W ceiling applies on those four channels, under those duty-cycle conditions — so the top of the range is not a level you may simply leave set everywhere. And the limit in the rules is on radiated power, e.r.p., which by definition accounts for antenna gain; the datasheet does not state whether its 33 dBm figure is measured at the radio or radiated by the panel, and we are not going to guess on its behalf. The practical consequence is the same either way: the output setting that keeps a particular installation inside the Indian limits is a commissioning decision, and the number for your site is a question for us and for WPC or your own compliance advisor, not something to read off a specification table.
Identium is BIS certified, and our UHF readers and antennas are WPC-approved for India’s licence-exempt UHF RFID band. The ID-EA500 datasheet itself states no approval status for the product, so if a tender needs the approval position for this specific model, ask us for it in writing rather than inferring it from the rest of the range. Our BIS and WPC compliance guide explains why the approval position decides whether you can switch anything on.
When the collapse is the right call — and when it is not
It fits where you want overhead zone coverage at several separate positions and are prepared to pay per position: shelf and floor zones in retail, bay and aisle zones in a warehouse, in-and-out counting by direction at dock doors, stacks and returns in a library, equipment and linen in a hospital, asset rooms in an office. It fits best where there is no comms room worth putting a PC in, where sites are spread out, and where nobody wants to own a middleware server.
It fits badly in four cases. When one read point genuinely needs several antennas aimed in different directions — a wide multi-lane dock portal — a multi-port fixed reader driving external antennas is still the right structure, and our reader selection guide covers that choice. When the requirement is coordinates rather than zones, which is the boundary at the top of this post. When the workflow you actually need is tag encoding, which belongs on a desktop unit. And when the mounting environment is wet, washed down or genuinely dirty, because the datasheet publishes no ingress rating and you should not assume one from the fact that it is a sealed-looking panel.
For context in the wider range, see our integrated readers — reader and antenna in one housing, without the edge controller — and the full UHF RFID reader line-up. Every reader we ship comes with an SDK, a demo application and its source code.
There is no published price, lead time or coverage figure for the ID-EA500, and you should be wary of anyone who offers a coverage figure before seeing your ceiling. What we can do is measure it: Identium can run a site trial with an ID-EA500 and ReaderSense on your own goods at your own mounting height, so the panel count and zone layout come from measurement rather than estimation.
Related reading
- Need x, y coordinates rather than zones? Active RFID vs BLE vs passive UHF: choosing an RTLS
- The desktop application, not the on-panel one: what Identium ReaderSense does
- Where this panel sits in the range: RFID integrated readers with inbuilt antenna