Impinj has issued firmware version 10.4 for its R700 series RAIN RFID readers. On paper it is a modest point release, but it clears two of the more tedious obstacles integrators hit in the field: finding a USB Wi-Fi dongle the reader will actually accept, and persuading a browser to talk to a reader directly.
More Wi-Fi dongle choice for awkward installations
The R700 has no onboard wireless radio. Wi-Fi is added through a USB dongle, and the practical limit has always been the list of validated devices rather than the reader itself. Firmware 10.4 adds support for a further chipset, the MediaTek MT7601U, widening the pool of adapters that can be fitted to an R700. Every previously validated dongle still works, and the current list is published in the release notes.
This matters more than it sounds. Consumer USB adapters go end of life constantly, and a replacement bought under the same model name eighteen months later can easily carry a different chipset. Broadening chipset support reduces the odds of a spares cupboard full of dongles the reader will not enumerate. Impinj is explicit that nothing else changes: the same SSID, security and network settings apply whichever supported dongle is in use, so provisioning scripts and device management workflows stay as they are.
Worth remembering that Wi-Fi solves the data path, not the power one. Most fixed reader deployments run on PoE because one cable does both jobs. Where that cabling is impractical, in yards, temporary docks, chilled areas or listed buildings, a Wi-Fi dongle plus a local DC supply is the fallback, and the more dongle options the better.
CORS control arrives on the RAIN RFID REST API
The second change is aimed squarely at developers. The Impinj IoT Device Interface has exposed an OpenAPI compatible REST API on the reader since firmware 7.3, alongside MQTT and Kafka for data egress. What it did not expose was any control over Cross-Origin Resource Sharing, so a browser based dashboard served from one origin was blocked by the browser’s own security policy from calling a reader on another. The usual answer was a backend proxy that existed purely to relay the request.
Firmware 10.4 lets CORS be enabled or disabled through the REST interface itself. Each R700 then behaves as a standards compliant, individually addressable API endpoint that modern web frameworks can call directly. For a small installation with a handful of readers and a status dashboard, that removes an entire tier of middleware and the hosting, monitoring and patching that came with it.
One caution: CORS exists to restrict what browsers may do, so switching it on relaxes a protection rather than adding one. Scope it to the origins you actually serve, and keep readers on a segmented VLAN rather than anywhere near a public interface.
R700v2 adds four APAC regions
Version 10.4 also extends R700v2 regional support to South Korea, Taiwan, Vietnam and Indonesia. UHF band plans and permitted power differ by regulatory domain, so region coverage in firmware decides whether one hardware platform can serve a multi country rollout or whether a project needs separate variants and separate spares holdings. For partners with APAC operations, that is the difference between one reader platform and several.
Affected part numbers cover the 4 port ETSI, FCC and global, and Japan readers in both original and revision 2 form: IPJ-R700-241, -241-B, -341, -341-B, -441 and -441-B. Impinj recommends updating to the latest firmware, with technical queries going to [email protected]. As always, stage it on a test reader first and check any LLRP, RShell or on reader custom application dependencies before rolling it across a live estate.
