Vehicle access guide
Parking access: LPR, RFID cards, UHF tags or QR?
Choose how regular users, visitors and service vehicles identify themselves at each entrance. Compare the equipment, issuing process and fallback before specifying a Lexoh parking lane.
Short answer
Match the credential to the arrival.
License plate recognition (LPR) reads a vehicle’s plate with a camera and recognition software. Radio-frequency identification (RFID) reads a card, fob or tag using radio waves. Ultra-high-frequency (UHF) vehicle tags are a type of RFID; this guide distinguishes them from cards deliberately presented near a reader. A QR code is an optical credential shown to a scanner on a phone or on paper.
Lexoh combines access software with readers, kiosks and lane equipment. The software evaluates the presented identifier against the configured permission; reading an identifier alone does not authorize entry. Plan the primary credential and an assistance or alternate-credential path for each user group.
A site can combine several credential types where the selected readers, controller and software support them. A resident using the same vehicle has different needs from a delivery driver or a guest arriving in a rental car. Start with those journeys, then confirm the equipment and configuration in the proposal.
Side by side
Compare the equipment and operating constraints.
Scroll horizontally to compare every option.
| Criterion | License plate (LPR) | RFID card | Long-range UHF tag | QR code |
|---|---|---|---|---|
| What is read | Plate characters captured by a camera | Compatible card or fob | Compatible vehicle-mounted RFID tag | Code on a screen or paper |
| Driver action | Follow the marked approach and stopping instructions | Stop and present the credential | Follow the marked approach; no hand presentation of a mounted tag | Stop and present the code within the scanner’s read zone |
| Read zone | Set by camera, lighting, angle and recognition configuration | Defined by the reader/card combination | UHF9DBI: 0–15 m stated range, dependent on tag chip and environment | Defined by scanner, code size, display quality and presentation |
| Issuing work | Register the plate and keep vehicle changes current | Issue, activate, replace and revoke cards | Assign the tag, install it appropriately and manage vehicle changes | Issue with configured rights, expiry and permitted reuse |
| Typical fit | Registered vehicles and plate-linked parking sessions | People already using a compatible door badge | Regular fleets or other vehicles assigned a tag | Visitors, reservations and temporary access |
| Constraints | Obscured plates, capture conditions and rental/temporary plates | Lost or shared cards; reach from different vehicles | Windshield/material compatibility, mounting and adjacent-lane reads | Glare, battery, copied codes and scanner access |
| Winter checks | Visible plate, capture quality, lighting and fallback | Reader temperature rating, icing and reach | Reader/tag ratings and mounting; UHF9DBI operating range is −25 to +70 °C | Scanner rating, snow/ice, reach and a paper or assistance fallback |
| Offline behavior | Verify local recognition and available permissions | Verify local authorization and revocation handling | Verify local authorization and revocation handling | Verify code validation, expiry and reuse rules during outage |
| Cost drivers | Camera, illumination, licensing, setup and exception handling | Reader, cards, issuing and replacement | Reader/antenna arrangement, tags, mounting and issuing | Scanner, issuing workflow and any required integration |
Decision rules
Five decisions to make for each entrance.
Use these questions together. Several may apply to the same lane.
-
1. Do regular users keep the same vehicle?
Consider plate recognition when registering and updating plates is practical. Consider a UHF tag when the operator can assign and maintain a compatible vehicle credential. Check actual vehicles, read zones and exception handling before choosing either.
-
2. How is temporary access issued?
A QR code can suit guests, contractors and reservations. Define who issues it, when it becomes valid, when it expires and how reuse is controlled. Automated issuing requires the reservation or visitor workflow to be included and verified.
-
3. Does permission belong to a person, vehicle or trailer?
Choose the record that must hold the right. A tag on a towing vehicle does not establish the identity of its trailer. If a trailer needs its own identifier, verify the tag’s mounting, material compatibility and read zone.
-
4. Can the existing door card be reused?
Check the exact card technology, encoding and reader/controller support. A brand name alone does not prove compatibility. Confirm that the reader position can be reached from the vehicles using the lane.
-
5. What happens when identification or payment fails?
Define the kiosk, intercom or authorized staff response for an unread credential, an unpaid stay or a driver without a working phone. Include the answering hours and permissions in the operating scope.
Worked scenarios
Illustrative combinations by site type.
Scroll horizontally to compare every option.
| Site | Regular users | Temporary users | Why |
|---|---|---|---|
| Campground or RV park | Plate or compatible UHF tag for registered vehicles | Time-limited QR tied to the booking, if integrated | Handle towing vehicles, changed plates and late arrivals. |
| Marina | Plate for parking; separate trailer identifier if required | QR or staff-assisted access | Define whether the permission concerns parking, the launch, the boat or the trailer. |
| Condominium | Plate or vehicle tag; compatible card for doors | Resident-issued guest access where configured | Plan tenant changes, rentals and emergency assistance. |
| Office building | Compatible existing card or registered plate | Visitor QR or reception assistance | Check card reuse and visitor issuing responsibilities. |
| Municipal paid lot | Plate linked to a permit where configured | Ticket, QR or plate linked to a paid stay | Trace payment and permission to the correct session. |
| Industrial site | Compatible UHF tags assigned to fleet vehicles | Scheduled visitor credential or staffed assistance | Test actual truck heights, trailers and adjacent-lane reads. |
Barrier integration
How the credential connects to the barrier.
The reader reports an identifier. The configured access system evaluates the relevant zone, validity period, status and any payment condition. An authorized command then goes to the barrier control system. Vehicle detection and the operator’s protective functions govern the physical passage according to the approved sequence; a loop or radar does not independently prove that closing is permitted.
Keeping an existing barrier requires a review of its model, control inputs, electrical interface and protective sequence. The reader also needs a supported interface and credential format. Do not infer compatibility from the words Wiegand or OSDP alone. Ask the integrator to document the complete reader-to-controller-to-operator connection.
-
Anti-passback
If repeated entry must be restricted, define entry/exit tracking, exceptions, reset permissions and behavior during a lost connection. Demonstrate those rules for the chosen credentials.
-
Offline operation
Specify which credentials and permissions remain available locally, how expiry is handled and when revoked rights reach the lane. Demonstrate outage and recovery using the approved procedure; credential type alone does not determine offline capability.
-
Event and video review
Define the events to retain, the camera views available for investigation and who may access them. Confirm time synchronization, retention and the handling of personal data in the project scope.
Canadian winter
Plan for winter conditions at the actual site.
Snow, dirt or salt can obscure plate characters. Lighting and camera alignment cannot recover characters hidden from view, so agree on an alternate credential or assistance path. Review the real approach, expected vehicles and day/night conditions with the installer; a season alone does not determine which credential will work best.
UHF avoids relying on visible plate characters, but it still has equipment limits. The Lexoh UHF9DBI French datasheet, page 3, lists a 0–15 m read range dependent on tag chip and environment, an IP65 rating and an operating temperature of −25 to +70 °C. Its −40 to +85 °C storage range is not an operating rating. A site that may be colder than −25 °C needs a documented suitable equipment arrangement; do not assume this reader is rated for those conditions.
-
Plate recognition
Check clear sight of the relevant front or rear plate, lighting and obscuration. Include unread and changed plates in the acceptance scenarios.
-
UHF tag
Verify the exact tag and reader combination, windshield or mounting material, orientation and lane association. A longer maximum range is not always desirable beside another entrance.
-
Cards and QR codes
Confirm reader/scanner temperature limits, protection from snow and ice and driver reach. Include a flat phone battery, glare or an unreadable code in the fallback plan.
Project checklist
Questions to answer per lane before choosing
Answer these for each entrance and include the agreed behavior in acceptance.
-
Who arrives here, and how often with the same vehicle?
Regular users with a stable vehicle point to the plate or a tag. Changing vehicles point to a card or a code.
-
Do these users already carry a credential for doors?
Confirm the exact card technology, encoding and compatible reader/controller combination before planning reuse.
-
How are temporary users invited today?
Reservation system, front desk, resident portal: the issuing flow determines whether QR codes can be automated.
-
What happens to a vehicle the reader cannot identify?
Intercom, kiosk, remote operator or a second credential. Decide this before the equipment.
-
Is the lane paid?
Paid lanes need the payment and exception path designed with the credential.
-
What must still work during an outage?
Specify locally available rights, expiry, revocation, permitted reuse and assistance; verify interruption and recovery.
Practical questions
Questions asked when choosing a credential
Is plate recognition suitable for Quebec winters?
It can be considered when the camera and installation suit the site, but a hidden plate cannot supply readable characters. Evaluate capture conditions and define a fallback for snow-covered or dirty plates. Check the environmental limits of every proposed reader; UHF is not automatically suitable for every winter temperature.
Can one entrance use plates and QR codes?
A project can combine these credentials with compatible readers and the required controller/software configuration. Define how each identifier maps to the access record, which lanes it may open and what happens when more than one is presented. Include those cases in acceptance.
What range does the Lexoh UHF9DBI specify?
Page 3 of the supplied French datasheet states 0–15 m, depending on the tag chip and environment. Verify the chosen tag, mounting and actual read zone on site. This is a reader specification, not a guaranteed distance or a promise that drivers can pass without slowing or stopping.
Which credential costs least?
Compare the complete installed and operating scope. Plates avoid issuing a physical card or tag but still require capture equipment, software and administration. QR codes require scanning and an issuing process. Cards and tags add stock, distribution and replacement work. Request prices for the actual lane and user volumes.
Can a QR code be copied or shared?
An image of a code can be copied. Validity, expiry and single-use rules can limit use when supported and configured, but the code image alone does not prove who is presenting it. Define the required controls and demonstrate reuse, expiry and offline behavior before acceptance.
Do I still need a card with plate recognition?
A compatible card can remain useful for pedestrian doors or as a fallback at the lane. Decide which user journeys need it, then verify the card technology and reader support. Plate recognition does not establish that every door or exception can use the same credential.
How should rental vehicles and temporary plates be handled?
Define an authorized process to update the plate for the permitted period or issue another supported credential. Verify that the recognition system handles the actual plate format. Record who can make the change and when the temporary right expires.
Can we keep the existing barrier?
Possibly, after checking the operator model, control interface, condition and protective sequence against the proposed access system. Changing the credential changes the reading equipment, but can also change stopping positions and timing. Have the integrator review the complete lane.
References and further reading
- Lexoh parking access control
How rights and lanes are configured.
- Lexoh UHF reader
Read range and mounting.
- Lexoh vehicle detection guide
Detection options for the barrier.
- Lexoh UHF9DBI — French technical datasheet, page 3
Read range depends on tag chip and environment. Operating and storage temperature limits are distinct.
Lane review
Plan the credential and the fallback together.
Share your user groups, existing credentials, lane plan and seasonal conditions with Lexoh. We can review the readers, software rules and operating responsibilities before preparing a proposal.
Discuss your lanes