Virtual Loop Detector: Vehicle Detection Without Cutting the Road

Every barrier lane has to answer one question before the boom lifts: is there a vehicle? For decades the answer came from a loop of wire buried in the pavement. On a new-build asphalt approach that is still the cheapest and most durable way to do it. But a growing share of lanes cannot be cut at all: finished block paving, a suspended deck, a post-tensioned slab, or a loop that has already failed twice under the same surfacing.

A virtual loop answers the question without cutting anything. It is a detection zone defined in software by an above-ground sensor — most often FMCW radar, sometimes a camera or LiDAR — that hands the barrier controller the same kind of presence signal a buried loop hands it. This guide covers where that works, where it does not, what belongs in the specification, and how to commission a lane that uses one.

What a virtual loop actually does

An induction loop is a metal detector. A coil of wire under the surface changes inductance when steel passes over it, and a detector module in the cabinet turns that change into a relay output. The barrier controller never sees the coil; it only sees the relay close and open.

A virtual loop moves the sensing above the pavement. The sensor measures the distance and speed of objects in its field, and the installer draws one or more zones inside that field: usually an activation zone on the approach side of the boom and a presence zone under or just behind the boom. When a vehicle enters a zone, the sensor closes a potential-free relay exactly as a loop detector would.

Two practical differences follow from that:

• Line of sight replaces digging. A loop works under 100 mm of asphalt and does not care what is parked on top of it. A sensor needs an unobstructed view of the zone, which is why mounting height, angle, signage and vegetation suddenly matter.
• The zone is editable. Zone size, direction filter and target type (vehicle only, or vehicle plus pedestrian) are set in software and can be changed in minutes. A loop's shape and position are fixed the moment the sealant cures.

Four ways to detect a vehicle at a barrier

Method	How it senses	Pavement work	Strengths	Watch-outs
Inductive loop	Metal mass over a buried coil	Saw-cut, loop wire, sealant, detector module	Unaffected by rain, glare, fog and darkness; ignores people and bicycles when tuned	Requires cutting; wire breaks where pavement moves; repairs reopen the lane
Radar virtual loop	Range and speed of objects in a software-defined zone (FMCW, typically in the 24–79 GHz range)	None — mounted above ground	No road works; zones reconfigurable; works in rain, fog and at night	Needs a clear field of view; snow banks, signs and swaying vegetation cause false presence
Camera / vision virtual loop	Objects detected and tracked in the image	None	Can classify vehicles, and read plates when paired with an LPR camera	Low sun, headlights, dirt and heavy rain affect it; privacy and lighting rules apply
Magnetometer	Disturbance of the earth's magnetic field	Small borehole or shallow burial	Presence detection without a saw-cut; very low power	Less common for gate actuation; gives little information about the target

For loop sizing, wiring and fault-finding, the companion guide on vehicle loop detectors covers the in-ground side in detail. This article stays on the above-ground alternative.

When a virtual loop is the right choice

• The slab cannot be cut. Post-tensioned and pre-stressed concrete contains tensioned strands and ducts. A saw-cut through them is a structural problem, not a maintenance nuisance.
• The surface is not a road. Suspended decks, rooftop car parks, steel grating and bridge approaches take a mounted sensor far more easily than a cut.
• The paving is finished and expensive. Block paving, stamped concrete, resin-bound gravel and exposed aggregate all show a saw-cut line for years. On heritage or listed sites, cutting may not be permitted at all.
• Something is already buried. Underfloor heating, fibre, irrigation and shallow drainage turn a loop layout into a survey job before it becomes an installation job.
• The loop keeps failing. Where pavement moves or water reaches the saw-cut, the wire breaks — and every replacement reopens the same lane.
• The lane is temporary. Event car parks, construction access and seasonal sites can take their detection away with them at the end of the job.
• The schedule is tight. A loop has to be cut, sealed and cured before traffic runs over it; a mounted sensor can be aligned and tested the same day.

When the buried loop is still the better answer

• New build with the subbase open. If the pavement is not laid yet, the loop costs little more than the cable and has no field of view to protect for the next ten years.
• Heavy foot traffic beside the lane. A tuned loop responds to metal mass, so pedestrians and cyclists crossing the zone are simply not seen. A radar sensor in vehicle-plus-pedestrian mode will see them, and vehicle-only mode then depends on field shaping and testing.
• Counting and multi-loop logic. One detector module can serve several loops for presence, counting or tailgating logic. Surface sensors usually cover one zone group each, so the same logic needs more hardware.
• Deep snow and standing water. Radar copes with weather, but a zone buried under a ploughed snow bank is no longer the zone you commissioned.
• The operator's standard names a loop. Some parking operators and public authorities still specify an approved inductive-loop system for the safety presence function. Where that applies, the loop is not optional.

Plenty of lanes end up with both: a loop for the presence function the operator requires, plus an above-ground sensor for activation or for the area the loop cannot cover.

Mounting and geometry

Most gate sensors are mounted roughly 0.5–0.7 m above the pavement — on the barrier cabinet, a dedicated post or the boom skirt, depending on the model. What matters is what the sensor can see:

• Cover the approach, not the far side of the road. The activation zone belongs where a driver stops to take a ticket or present a card.
• Keep the boom out of the presence zone, or choose a model that learns the boom movement during teach-in.
• Watch the corners of the field. Signs, mirrors, flagpoles, bollards and swaying shrubs inside the zone produce the false presence calls that later get blamed on the gate.
• Plan the cable route with the lane, not after it. The sensor needs power (12–24 V DC is typical) and a signal pair back to the cabinet. Heated versions draw substantially more current than unheated ones, so check the cabinet's budget and the fuse.
• Long arms need more than one zone. On a 6 m arm, a single field often leaves a gap at the tip; check coverage against arm length and lane width before ordering.

Lane layout, island position and duct routes are settled before the first cable is pulled — the site preparation guide covers that stage in detail.

Commissioning a lane that has one

1. Wire to the right input. The sensor's relay goes to a dry-contact activation or presence input, not into the loop detector socket, which expects a coil.
2. Teach in with the lane empty and let the boom complete a full cycle if the model learns boom movement.
3. Set the zones slightly larger than the equivalent loop. Radar fields have soft edges, and most manufacturers recommend it.
4. Test three vehicle sizes: a compact car, a van, and a vehicle with a trailer. A trailer stopped under the boom is the classic early-close failure.
5. Walk the zone. Confirm what the sensor does with a pedestrian, then decide whether that behaviour is acceptable in this lane.
6. Drive the parallel lane and the verge. Cross traffic and passing vehicles must not open your gate.
7. Record the settings and hand the report over with the lane, so the same zones can be restored in minutes if the unit is ever replaced.

That is the detection part of the handover. Force limits, protective devices, signage and the acceptance record belong to the full sequence in the lane commissioning guide.

Failure modes worth knowing

• Dirty radome or lens. Dust, insects, salt film, condensation and frost cut detection range, and the sensor rarely reports it.
• Changed surroundings. A new sign, a parked van, a delivery cage or summer growth inside the field will trigger the gate.
• Mechanical drift. A knocked bracket or a jet-wash at close range can move the zone by centimetres — enough to miss a low sports car.
• Sensor-to-sensor interference. Two units facing each other across a lane can cross-trigger; direction filters and channel settings exist for exactly this case.
• Power problems. Undervoltage at the end of a long cable run shows up as intermittent missed activations, which are usually blamed on the sensor.

When a lane already behaves badly, the troubleshooting guide separates detection faults from motor, spring and controller faults. One point is worth stating plainly: a detection sensor is not a protective device. Where the operator's documentation requires monitored photo eyes or safety edges, a virtual loop does not replace them — the safety sensors guide sets out which device covers which risk.

What belongs in the specification

• Functions and zone count: activation, presence, protection — and how many of each.
• Output type: potential-free relay, normally open or normally closed, pulse or presence mode.
• Supply available in the cabinet, and whether a heated version is needed for the site's winter.
• IP rating and operating temperature range matched to the climate, not to the catalogue's best case.
• Target classification: vehicle only, or vehicle plus pedestrian, and the direction filter.
• Mounting kit and height provision on the cabinet, post or boom skirt.
• The standards and classification the sensor is declared under, plus a settings report at handover.
• A written statement of whether the sensor may serve the safety presence function or only activation.

Bottom line

A virtual loop is not a gadget for avoiding road works. It is the cheaper answer on the projects where cutting the road is expensive, risky or simply forbidden. Decide with three questions: can this surface be cut, who will keep the detection zone clear once the site is handed over, and does the operator's standard require an inductive loop for presence? Lane geometry and the barrier gate itself come after that. If a lane is being planned around detection rather than the other way round, send the zone sketch with the enquiry — it is the fastest way to get a gate specification that fits.

FAQ

Can a virtual loop replace an induction loop completely?

For activation, yes: the sensor closes a dry contact that the controller reads exactly like a loop relay. For the safety presence function, only where the gate operator's documentation accepts that type of device; otherwise the lane keeps its loop or the protective devices the operator requires.

Does a virtual loop work in rain, fog and snow?

Radar versions handle rain, fog and darkness, and heated models exist for frost. What they cannot handle is a detection zone that physically fills with a ploughed snow bank or standing water, which is why the zone has to stay clear after handover.

How much pavement work does it need?

None beyond a mounting point and a cable route. The sensor is fixed to the barrier cabinet, a post or the boom skirt, and its zones are configured by app or keypad instead of being cut into the surface.

Why does the gate close too early with a trailer?

Usually the presence zone is too short or sits too close to the boom, so the trailer leaves the field before the arm finishes descending. Set the zone slightly larger than the equivalent loop and test with a trailer during commissioning.

Can one sensor serve two lanes?

Sometimes, when both lanes sit inside its field of view and the model supports separate zones and outputs. Where each lane needs independent presence logic, separate sensors or a loop on at least one lane are usually simpler.

What should I send with an enquiry?

A zone sketch: lane width, arm length, where the driver stops, what the surface is made of, and whether the operator's standard requires an inductive loop. That is enough to specify a gate that fits the layout.