Short answer: yes, two UHF RFID readers within range of each other can interfere, because one reader’s carrier can drown the far weaker tag replies the other is listening for. In India, full reader power is allowed on only four channels of up to 200 kHz; dense reader mode, which the ETSI standard that India’s Table IV references defines for this channel plan, is how close readers share them, where supported.
Table IV of G.S.R. 853(E) of 10 December 2021 centres those channels at 865.7, 866.3, 866.9 and 867.5 MHz, so neighbouring readers share them. Table IV also describes tags as responding at a very low power level around the reader channels, which is why a neighbour’s carrier can drown their replies. In dense reader mode, tags reply in the gaps between reader channels: ETSI EN 302 208 V3.4.1 defines it for this plan, and GS1 EPC Gen2 Release 3.0.1 Annex G illustrates it (Example 1).
How does India’s four-channel plan differ from the US hopping plan?
| Parameter | India (G.S.R. 853(E), Table IV) | US (47 CFR 15.247) |
|---|---|---|
| Band | 865–868 MHz | 902–928 MHz |
| Where full reader power is allowed | Four channels of ≤200 kHz only | Across the band: hopping or digital modulation |
| Channels | Centred at 865.7, 866.3, 866.9, 867.5 MHz | ≥50 hop channels (<250 kHz wide) for 1 W |
| Reader power | 2 W e.r.p., antenna gain included | 1 W peak conducted; 0.25 W with 25–49 channels |
| Time on one channel | ≤4 s continuous, ≥100 ms before reuse | ≤0.4 s average in any 20 s |
| How close readers keep apart | Tags reply between reader channels | Hopping; RAIN’s US9A also lists dense reader mode |
Sources: 47 CFR 15.247(a)(1)(i), (a)(2), (b)(2) and (b)(4); EN 302 208; Gen2 Annex G; RAIN RFID System Design Guidelines V2.0, Table 1. India’s figure is e.r.p.; the US figure is conducted, reduced for antenna gain above 6 dBi, so they are not directly comparable.
An Indian site cannot spread readers across many hop channels, so the design problem is sharing four channels well. For readers built to the US plan, see can a US 902–928 MHz reader be used in India?
Why do two UHF readers close together interfere?
There are two separate problems, with different fixes.
The radio problem. A passive tag has no transmitter; it answers by reflecting part of the reader’s carrier, so its reply is far weaker than any reader’s carrier. A second reader’s carrier on or beside the frequency where your tags answer can bury that faint reply. Gen2 clause G.1 puts it this way: with two or more readers, range and read rate improve when reader transmissions do not collide spectrally with tag responses. EN 302 208 clause 4.4.1 tests this as adjacent-channel selectivity, with the other device ±0.6 MHz away.
The protocol problem. Gen2 tags support four sessions, S0 to S3, each with its own A/B inventoried flag, so readers on different sessions can inventory shared tags independently (clause 6.3.2.2). Two readers on the same session and target flip the flags the other is looking for, so tags drop out of each other’s rounds: missed or slow reads with no RF fault at all.
Neither is containment, a reader logging tags at the next dock door (handled with power, aim, triggers and filters), nor one reader’s anti-collision (how many tags a reader can read at once).
India’s UHF RFID channel plan at a glance
- Channels: within the 865–868 MHz band, four high-power channels of ≤200 kHz (Table IV), centred 600 kHz apart.
- Pairing: for readers close together, the RAIN RFID System Design Guidelines V2.0 (clause 2.7.2) give the widest separation by pairing 865.7 with 866.9 MHz and 866.3 with 867.5 MHz, each pair 1.2 MHz apart.
- Antenna gain counts: e.r.p. is antenna input power times gain relative to a half-wave dipole (Rule 2(1)(c)).
- Time: ≤4 s continuous, ≥100 ms before reuse; at the limit a reader may switch straight to another channel (EN 302 208 clause 4.2.1).
- No protection: the exemption applies on a “non-interference, non-protection and shared and nonexclusive basis” (Rule 3).
More on RFID frequencies in India.
What is dense reader mode, and does it work in India?
EN 302 208 V3.4.1 defines dense interrogator mode as one in which several readers may transmit on the same channel at once while tags answer in the adjacent channels. For the lower band it requires tags to respond within the low-power channels (clause 4.2.2.1). The earlier V3.3.1 (2020) called this the preferred method, as it separates reader and tag frequencies and minimises inter-modulation products.
Gen2 calls it dense-interrogator mode and, for this plan, uses alternative-channel backscatter, one of three dense-interrogator methods in Annex G.1. Its illustrative Example 1 is this plan, shown with 75 kbps tag data on a 300 kHz subcarrier (BLF 300 kHz, Miller M=4); RAIN’s India profile, below, sets 320 kHz.
The cost is speed. Gen2 Table 6-10 sets the tag data rate at BLF/4 for Miller M=4, against BLF for FM0. How much that slows a real inventory depends on the tags and reader, so measure it.
India’s position. Table IV does not name dense reader mode. It references EN 302 208, and Rule 5(2) requires compliance with the respective EN. The RAIN RFID System Design Guidelines V2.0 (Table 1, clause 2.5.9) list India’s IN8A profile with dense reader mode at Miller M=4, a 320 kHz BLF and adaptive frequency agile channel use, identical to Europe’s EU8A; Identium One decodes those profile codes. Confirm the current position with WPC.
Check the reader. Gen2 says readers built for dense-interrogator operation (its own conformance term is ‘certified’) shall support the mode but need not always use it, and must hold ±10 ppm frequency accuracy over the nominal −25 °C to +40 °C range (±20 ppm extended) and meet the dense-interrogator transmit mask (Gen2 clauses 6.3.1.1, 6.3.1.2.1 and 6.3.1.2.11). Gen2 Annex G says a reader that instructs tags to use subcarrier (Miller) backscatter alongside other readers shall adopt its region’s channel plan, so set the India region profile. Vendors name the setting differently and not every reader offers it, so ask your supplier, or us, in writing. Identium is a BIS and WPC approved RFID manufacturer in New Delhi. Background: EPC Gen2, ISO/IEC 18000-63 and RAIN RFID and Gen2X and Gen2v3.
How do you stop two readers interfering, and in what order?
Work from the top: early rows are settings, later rows change the installation.
| Measure | What it does | When it is enough |
|---|---|---|
| 1. Channel plan and link profile | Widest pairs, Miller profile, India region | The slowdown follows channel overlap |
| 2. Sessions | S2 and S3 alternate on adjacent readers | Flag contention; it does nothing for RF |
| 3. Trigger gating | Reads only when a sensor fires | Traffic is intermittent |
| 4. Antenna aim, separation, polarisation | Antennas apart; facing pairs angled | Fields overlap only at the edges |
| 5. Power | Lowest setting that still reads the lane | Only surplus power reaches the neighbour |
Sessions. RAIN’s guidelines (clause 3.1.4) suggest alternating S2 and S3 so same-session readers are as far apart as possible. S0 suits small, fast-moving populations such as conveyors (clause 3.1.2). S2 and S3 flags persist for more than 2 s after power is lost over Gen2’s nominal temperature range (Table 6-21), and RAIN notes this can exceed a minute at room temperature, depending on temperature and tag silicon (clause 3.1.4). So reset tags with a B→A inventory or a Select rather than waiting.
Triggers. A reader that transmits only when something is in its lane spends less time on air beside its neighbour. EN 302 208 clause 4.3.7.3 requires a lower-band reader to transmit no longer than needed to read the tags present and confirm there are no more, suggesting motion triggers, a light beam or duty-cycled polling. Rule 5(2) requires compliance with the referenced EN; confirm with WPC how it applies to your installation. On supported Identium readers, ReaderSense starts reading when an input fires.
Aim and power. Two antennas facing each other can interfere, as the antenna gain and polarisation guide explains. Whether polarisation helps between readers depends on the antennas, so test it. Directional antennas have more gain, which counts towards e.r.p.; see antenna cable loss and read range.
How do you tell RF interference from session contention?
Separate the two problems above with a switch-one-off test at production settings:
- Run reader A alone, then reader B alone, then both, logging the reads each time.
- Compare the logs by antenna and by frequency. ReaderSense, on supported Identium readers, breaks reads down this way.
- Change one thing at a time: move B to the other session and repeat; then, if both readers allow channel selection, move them 1.2 MHz apart and repeat.
If the drop follows the channel overlap, fix the channel pairing and link profile first; if it clears when sessions are separated, it was flag contention. RSSI alone does not diagnose interference (what RSSI tells you).
One multi-port reader or several readers: which interferes less?
Often one multi-port reader. A single-radio multi-port reader serves its antennas in sequence, so its ports do not transmit at the same time or compete for a channel as two readers do; the IHZ4 serves its four ports this way.
The trade is time: read time is shared across the enabled ports. If every lane must be read continuously at full rate, test whether that shared time keeps up; if it does not, use two readers with paired channels and alternating sessions.
When does a ceiling array beat several lane readers?
The ID-EA500 is one ceiling panel with an integrated antenna array and edge controller. It reports zone presence and dwell, plus direction of travel from RF phase, not x, y coordinates, and suits overhead coverage of an area. A wide multi-lane portal suits a multi-port fixed reader better, and a single narrow lane a gate reader.
It does not remove the channel question: several panels are several readers on the same four channels, needing the same channel and session plan. No coverage figure is published, so plan a site trial.
What should you ask a reader supplier before installing several readers?
Get the answers in writing, for the exact model:
- Can it be set to the India region profile?
- Are dense-interrogator mode and Miller link profiles supported and selectable?
- Can channels be chosen or paired, or does the reader pick them?
- Is power set per port or for the whole reader?
- Are session and target selectable?
- Does it have GPI inputs that can start and stop reading?
- How does it behave beside a reader on the same channels, and which setting changes that?
Planning several readers in one building? Send us the reader count, spacing between read points, antenna models and a raw read log, and we will work through the channel and session plan with you.
Further reading on Identium One
- RAIN RFID regional reader settings table — dense reader mode and the regional settings behind it.