RFID Reader Power and Region Settings: Compliance Is a Configuration Problem

Compliance is not decided by the purchase order. It is decided by the configuration file that runs on the reader, and by whoever last changed it.

A reader certified for Europe will happily transmit at a power and on a channel plan that is legal in North America and illegal in Germany, if a technician selects the wrong profile during a site visit. The fix is governance of radio settings, not more stickers.

Three different power numbers

Most arguments about power are really arguments about which quantity is being quoted.

• Conducted power is what the radio delivers to the antenna port, measured at the connector.
• ERP adds antenna gain and subtracts cable loss, referenced to a half-wave dipole.
• EIRP does the same calculation referenced to an isotropic radiator, so it reads 2.15 dB higher than ERP.
• A regulatory limit is almost always stated in one of the last two, and the type matters.
• Antenna gain is the most common cause of accidental non-compliance, because it is chosen late.

Regions differ in band, power and access method

The same hardware generation is certified against four or five very different rule sets.

• North America uses 902 to 928 MHz with frequency hopping and comparatively generous power.
• Europe uses 865 to 868 MHz with lower power, narrow channels and listen-before-talk obligations.
• China uses dedicated sub-bands near 840 and 920 MHz, with its own power and channel rules.
• Japan uses a narrow band around 916 to 921 MHz and requires listen-before-talk.
• Other markets each have their own band edges and duty-cycle rules, and they change.

The practical consequence is that a global roll-out needs a region-specific configuration catalogue, not a single "best" setting copied between sites.

Frequency hopping, LBT and duty cycle

How a reader is allowed to occupy the spectrum matters as much as how loudly it speaks.

• Frequency hopping spreads transmissions across channels, so no single channel is occupied continuously.
• Listen-before-talk requires the reader to check the channel and back off if it is busy.
• Some regimes allow higher power in exchange for stricter channel access, and vice versa.
• Duty cycle limits mean a reader can transmit only a percentage of the time, which caps throughput.
• A configuration that ignores the access method can be legal in power and still be non-compliant.

Dense reader mode and the neighbours

In a real facility, the limit is usually interference rather than regulation.

• Dense-reader mode narrows the receiver and reduces adjacent-channel interference between readers.
• Session and inventory-flag choices decide whether tags answer one reader or many.
• Channel plans should be coordinated between adjacent portals, not chosen in isolation.
• Wi-Fi and other systems share the band in some regions, and harmonics can land elsewhere.
• Two legally configured readers can still make each other useless, which is an engineering problem.

Build a configuration catalogue, then lock it

The control that prevents most incidents is a small, versioned set of approved profiles.

• Define one profile per regulatory region: band, channels, power, access method, dense mode, sessions.
• Set the maximum power in the profile, and give field staff no reason to exceed it.
• Use region-locked hardware or firmware where the vendor offers it, so a wrong profile is harder to apply.
• Version profiles, and record which reader serial runs which version and since when.
• Review the catalogue whenever a national regulator changes the rules, and re-certify if required.

Antennas and cable loss change the result

The radio setting is only half of the transmission path.

• A higher-gain antenna raises EIRP without touching the reader's power setting.
• Long cable runs lose both power and reliability, and cheap connectors lose more than expected.
• Circular-polarised antennas trade a few decibels for orientation tolerance, which is often worth it.
• Mounting height and tilt change the field in the aisle more than a one-decibel power change.
• Document the antenna model, gain and cable loss beside the power setting, or audits become guesswork.

Prove compliance with documents, not confidence

Regulators and customers ask for evidence, and evidence has a shelf life.

• Keep the declaration of conformity, the test report and the certificate for each model and region.
• Keep the radio licence or registration where the country requires one.
• Match the certificate to the actual configuration; a certified reader run out of profile is still non-compliant.
• Retain installation records showing antenna gain and configured power per site.
• Re-check evidence when firmware changes, because a new firmware can change the radio behaviour.

Roaming assets and cross-border equipment

Readers that travel, and tags that travel, create compliance questions that fixed sites avoid.

• A reader moved between countries must be reconfigured before it transmits, not after.
• Handhelds carried across borders should switch profile automatically by location or by operator choice.
• Tag chips are usually passive and less regulated, but their band still matters for performance.
• Equipment sent for repair may return with a factory default profile; verify on receipt.
• Document the reconfiguration step in the shipping and commissioning checklists.

Field change control and audit

The failure mode is rarely malice; it is a technician solving a read problem at 5 p.m.

• Log every change to power, channel plan or region, with who, when and why.
• Require a second approval for any change that increases EIRP above the approved profile.
• Alert when a reader reports a configuration that differs from its assigned profile.
• Audit a sample of sites each quarter, comparing reported and actual settings.
• Feed read-performance complaints back into antenna and layout design, not into power.

A deployment checklist that survives an inspection

If an inspector arrives, the answers should already exist in a folder.

• Region and band per site, with the applicable national rule cited.
• Configured power, antenna gain, cable loss and resulting EIRP or ERP.
• Channel plan and access method, plus evidence that the setting is actually active.
• Certificate and declaration for the exact model and firmware in service.
• A named owner for the radio configuration, which is the control that keeps all of the above true.