How to Wire a Long-Range UHF Reader to an Access Controller or Barrier

To wire a long-range UHF RFID reader to an access controller, run three conductors from the reader’s Wiegand output to the controller’s reader port: D0 (green), D1 (white) and a shared ground (black). Power the reader from its own DC supply (commonly 12 V on integrated readers) sized for transmit current, set both ends to the same Wiegand format, and let the controller’s relay pulse the barrier’s open input.

System overview: vehicle tag, UHF reader, controller and barrier

A UHF vehicle lane has four parts, and each has one job:

• Vehicle tag. A passive EPC Gen2 (ISO/IEC 18000-63) label, usually stuck inside the windshield. It has no battery; it answers by backscattering the reader’s signal.
• UHF reader. An integrated long-range UHF reader combines radio and antenna in one weatherproof housing and turns the tag’s EPC (or TID) into a number.
• Access controller. It decides whether that number is allowed right now (whitelist, schedules, anti-passback) and logs the event.
• Barrier. The boom gate’s own control board raises the arm when its open input is triggered. Its loop detector or photo-eye keeps the arm from closing on a vehicle.

Keep those roles separate: a UHF reader is never a substitute for the barrier’s safety loop. For a site-level view of lanes, tags and software, see RFID vehicle access control and parking.

Order the reader for the band used where it will be installed: 902–928 MHz under FCC rules in the United States, 865–868 MHz under ETSI rules in Europe, and other national bands elsewhere. Our UHF frequency by country guide lists them.

Matching Wiegand 26/34 output to the controller

Wiegand is a one-way, three-wire interface. Both data lines idle high (typically about 5 V); a short low pulse on D0 sends a 0 and one on D1 sends a 1. The controller counts the bits, checks parity and discards any frame that fails.

The catch with UHF is length. An EPC is commonly 96 bits, but a Wiegand frame carries far fewer:

• Wiegand 26 (H10301): bit 1 is even parity over bits 2–13, bits 2–9 are an 8-bit facility code (0–255), bits 10–25 are a 16-bit card number (0–65,535), and bit 26 is odd parity over bits 14–25. That leaves 24 ID bits.
• Wiegand 34: bit 1 is even parity over bits 2–17, bits 2–33 carry 32 data bits, and bit 34 is odd parity over bits 18–33. Controllers differ on whether they show the 32 bits as one number or as two 16-bit fields.

So the reader must choose which bytes of the tag to send. Many readers output the last 3 bytes of the EPC in 26-bit mode and the last 4 bytes in 34-bit mode; some let you select TID bytes or a start address instead. Confirm this setting before you enroll a single vehicle. The Wiegand 26-bit format guide walks through the bit math.

Worked example. An EPC ending in …00 1A 2B 3C, sent in byte order, becomes facility code 26 (0x1A) and card number 11,068 (0x2B3C) in 26-bit mode, or the single 32-bit number 1,715,004 (0x001A2B3C) in 34-bit mode.

Two practical rules follow. First, blank tags do not always ship with unique EPCs, so either encode serialized EPCs or configure the reader to send TID bytes. Second, prefer 34-bit if the controller supports it. With 26-bit, only 24 bits tell tags apart, so two tags whose last three bytes happen to match look identical to the controller.

Wiring table: D0, D1, GND, 12V and cable length

Reader wire	Common color*	Connect to	Notes
+12V DC	Red	Power supply +V	Supply rated above the reader’s peak current
GND	Black	Power supply 0 V and controller reader-port GND	Common reference for D0/D1; mandatory with separate supplies
D0 (Data 0)	Green	Controller D0 / DATA0	Idles high, pulses low for each 0
D1 (Data 1)	White	Controller D1 / DATA1	Swapping D0 and D1 inverts every bit
Shield / drain	Bare	Controller-end ground only	Leave the reader end unconnected
LED / buzzer (if fitted)	Varies	Controller LED / BZ outputs	Optional read feedback
Relay NO / COM (if fitted)	Varies	Barrier OPEN / COM	Direct relay mode only

*Colors follow a widely used access-control convention. Always check the label on the reader’s cable.

Power is where UHF lanes differ from proximity-reader doors. A long-range reader typically draws several hundred milliamps while transmitting, far more than a 125 kHz or 13.56 MHz reader, so power it from a dedicated access-control power supply rated above its datasheet peak current, not from the controller’s reader port. With separate supplies, join the grounds as shown, but never connect the two +V outputs together.

Wiegand data is generally rated to about 150 m (500 ft) over 22 AWG shielded cable, but on UHF lanes the power pair usually runs out first. Voltage drop equals current × loop resistance (both conductors). The table assumes an example 0.5 A peak; use your reader’s datasheet figure.

Conductor size	Resistance per conductor at 20 °C	Drop at 0.5 A, 30 m (98 ft) run	Drop at 0.5 A, 50 m (164 ft) run
22 AWG (0.33 mm²)	≈ 53 Ω/km	≈ 1.6 V	≈ 2.6 V
20 AWG (0.52 mm²)	≈ 33 Ω/km	≈ 1.0 V	≈ 1.7 V
18 AWG (0.82 mm²)	≈ 21 Ω/km	≈ 0.6 V	≈ 1.0 V
16 AWG (1.31 mm²)	≈ 13 Ω/km	≈ 0.4 V	≈ 0.7 V

At that 0.5 A example, a 12 V reader fed through 50 m of 22 AWG sees under 9.5 V at its terminals while transmitting, which can cause resets or short range. Use a heavier power pair, or place the supply at the lane and run only D0, D1 and GND back to the controller. Keep reader cable in its own conduit, away from the barrier motor’s mains wiring.

Direct relay mode vs controller mode

Some integrated UHF readers include a relay and an internal tag whitelist, so they can open a barrier without a controller. Larger sites send Wiegand to a controller instead.

	Direct relay mode	Controller mode
Where the decision is made	Whitelist stored in the reader	Access controller or parking software
Wiring to barrier	Reader relay NO/COM → barrier OPEN/COM	Controller relay NO/COM → barrier OPEN/COM
Event log and audit trail	Limited or none	Central log of every read
Schedules and anti-passback	Usually not available	Standard controller features
Adding or removing a vehicle	At each reader	Once, in the controller database
Best fit	One or two lanes, small private sites	Multi-lane sites, entry/exit pairs, audit needs

In both modes the relay is a dry contact. Wire COM and NO across the barrier’s open input so the contact closes briefly on a valid read; wiring NC would hold the input closed whenever the relay is idle. Never apply voltage to a dry-contact input. A barrier’s open input is a low-current logic input and needs no suppression, but if a relay switches a lock or solenoid, follow the exact load / output manufacturer’s suppression instructions. Do not automatically add a diode; some locks prohibit it or require another protection arrangement.

For controller mode, a networked door controller with a free Wiegand reader port and a relay output is all you need. Giving each lane its own door channel keeps entry and exit logic separate.

RS485 and TCP/IP for parking software

Wiegand is fine for “open or don’t open,” but parking software usually wants the full EPC, the read time and sometimes signal strength, and it may configure readers remotely. That needs a two-way link.

Interface	ID data delivered	Direction	Typical max cable run	Typical use
Wiegand 26	24 bits (e.g., last 3 EPC bytes)	Reader → controller	≈ 150 m (500 ft)	Standard access controllers
Wiegand 34	32 bits (e.g., last 4 EPC bytes)	Reader → controller	≈ 150 m (500 ft)	Controllers with 34-bit support
RS485	Full EPC/TID, per reader protocol	Two-way, multi-drop	Up to 1,200 m (4,000 ft) at low baud rates	Lane controllers, PLCs, parking PCs
TCP/IP (Ethernet)	Full EPC/TID plus reader settings	Two-way	100 m (328 ft) per copper segment	Parking software, remote management

For RS485, use a twisted pair for A/B, terminate each end of the bus with 120 Ω, and run a reference conductor. Vendors disagree on A/B labeling, so swap the pair if nothing answers. The command set is defined by the reader’s firmware, so get the protocol document or SDK before designing software around it. For Ethernet, give each reader a static IP or DHCP reservation. If you need Wiegand and RS485 or TCP/IP output at the same time, confirm that per model.

Mounting height, angle and lane separation

• Aim at the stop point. Tilt the reader so the windshield tag sits well inside the read zone, not at its edge, while the vehicle slows for the arm. A reader beside the lane is usually turned inward toward the lane center.
• Match the tag height. Mount the reader head around the height of the tags it reads. Car and truck windshield tags sit at very different heights, so for mixed traffic test both or add a second reader for high vehicles.
• Check the glass. Windshields with metallic heat-reflective coatings can block UHF almost completely. Many have an uncoated area near the mirror; otherwise use tags designed for headlamp or license-plate mounting.
• Place the tag correctly. Follow the tag’s instructions, usually top center behind the mirror, clear of the metal roof edge and any tinted band.
• Limit the range. Set RF power to the lowest level that reads reliably at the stop point, so the reader ignores the adjacent lane and the second car in the queue.
• Separate entry and exit. Don’t point entry and exit readers at each other. Where several readers share a site, use their dense-reader or channel settings.
• Stay within regulatory limits. FCC rules allow up to 1 W conducted power with antennas up to 6 dBi (4 W EIRP) in 902–928 MHz; ETSI EN 302 208 allows up to 2 W ERP on its four high-power channels in 865–868 MHz. Don’t fit higher-gain antennas to chase range.

Enrolling vehicle tags with a desktop issuer

A desktop UHF writer on a USB port turns enrollment into an office task instead of a lane task. A workable process:

1. Pick a numbering scheme that fits the Wiegand format, for example one facility code per site and sequential card numbers.
2. Encode the EPC so the bytes the lane reader sends carry that number, and record each tag’s TID alongside it.
3. Lock the EPC bank behind an access password so tags can’t be rewritten in the field.
4. Label and register. Print the number on the tag backing or an issue sheet, then add it to the controller or parking software.
5. Test one tag at the lane and confirm the controller shows exactly the number you registered.

Locking stops rewriting, not copying: a standard EPC can be read and written onto another tag. The TID is programmed when the chip is made and cannot be changed on standard tags, so outputting TID bytes makes simple copying harder. Where spoofing is a real risk, use tags with cryptographic authentication and a reader and software that verify it. Tamper-evident windshield labels that break when peeled also stop tags moving between vehicles.

Troubleshooting: wrong numbers, double reads and no reads

Wrong or unexpected numbers

• Format mismatch: the reader sends 34-bit and the controller expects 26-bit, or the reverse. Many controllers drop frames of the wrong length; some mis-parse them.
• Byte selection or order: the reader sends TID instead of EPC, different bytes, or bytes reversed. Compare the controller’s number with the hex EPC from the desktop writer.
• D0 and D1 swapped: every bit is inverted, so parity fails and reads are rejected or show unrelated numbers.
• Display format: the controller shows facility code plus card number while your register holds one combined decimal, or vice versa.

Double reads

• The reader re-reports a waiting car’s tag. Set the reader’s same-tag filter (repeat interval) and the controller’s anti-passback or re-entry timer.
• Entry and exit readers both see the tag, or reflections from cabinets, fences and large vehicles stretch the read zone. Reduce RF power first, then re-aim or add distance.

No reads

• Missing common ground: the reader powers up but the controller receives nothing.
• Voltage sag during transmit: measure at the reader terminals while it is reading, not at the supply.
• Coated windshield, tag too close to metal, or tag behind a tinted band.
• Wrong regional band variant, or RF power left too low after an earlier range reduction.
• Tag enrolled under a different number than the one the controller actually receives.

Installation checklist

• Reader band variant matches the country (902–928 MHz FCC, 865–868 MHz ETSI, or the local band)
• Supply rated for the reader’s peak current plus margin; voltage checked at the reader terminals while transmitting
• Reader GND tied to controller GND; +V outputs of separate supplies not joined
• Same Wiegand format (26 or 34) and byte selection set on reader and controller
• Shield drain grounded at the controller end only; reader cable separated from mains wiring
• Relay NO/COM wired to barrier OPEN/COM; pulse time set
• Barrier loop detector or photo-eye working independently of the reader
• RF power reduced; no reads from adjacent lanes or queued vehicles
• Same-tag filter and anti-passback configured
• Tags encoded, locked, labeled and registered; one test tag verified per lane

Next steps

Tell us the installation country, your lane layout, the Wiegand formats your controller accepts, and whether parking software needs RS485 or TCP/IP. We’ll confirm the reader band, output format and tag type, and can send samples for a lane test before you order in volume. Request a quote and we’ll reply within 24 hours.

Suppression source

Only the suppression guidance was reviewed for this update. Securitron SAM installation manual, section 6.3 illustrates manufacturer-specific requirements; use the exact equipment manuals.