In an LPR barrier system, the camera reads a plate and the access system applies permission or payment rules. Neither event proves that the vehicle has cleared the moving boom. An inductive loop provides a separate vehicle-presence input that can inhibit closing while the detection zone is occupied, when the detector and barrier controller are correctly configured.
This function is often called an anti-smashing, anti-fall or safety loop. Those names describe its intended role in vehicle protection; they do not establish pedestrian protection or certify the complete installation. Vehicle detection, access authorization and protection against mechanical injury must be considered separately.
What is inductive-loop anti-smashing?
A wire loop embedded in the road connects to a detector. A vehicle changes the loop’s inductance, and the detector reports occupancy through its configured output. The barrier controller uses that input according to its documented logic, for example to hold the boom open or inhibit closing. Whether an active input stops or reverses a moving boom depends on the controller and connection; do not assume every input behaves alike.
The protected area is determined by the loop geometry, detector settings, vehicle characteristics and barrier layout. A loop does not read a plate, decide whether a fee is paid, or reliably detect a person simply because that person is beneath the arm.
Why LPR systems still need presence detection
A permitted vehicle can pause, reverse or move more slowly than expected after recognition. Another vehicle can follow closely. A timer started by a plate read cannot prove that the boom’s path is clear. Presence detection gives the controller a separate physical input; it does not replace the operating rules needed for tailgating, direction control and exceptions.
How the two loop roles work
An approach or trigger loop detects an arriving vehicle. Depending on the design, it can trigger capture, enable a terminal, or request free exit. An opening request still has to pass the configured access rules. A presence loop near the boom monitors the area relevant to closing. Its location must keep the necessary vehicle area covered throughout passage, rather than merely detect arrival.
Two loops are a common arrangement, not a universal specification. Some projects need different zones or supported sensor technologies. Follow the barrier and detector manuals for channel assignments, relay logic, mounting distances and fault behavior; a diagram from another project is not an installation drawing.
Step-by-step operation
- The arrival detector or camera detects an approaching vehicle and the system captures its plate.
- The access or parking software checks the applicable permit, visitor or payment rule.
- The controller receives an authorized opening request and raises the boom according to its control logic.
- While the vehicle occupies the configured presence zone, the detector maintains the relevant input and the controller inhibits closing as specified.
- After the zone clears and the required passage sequence is satisfied, the controller can close using its configured logic. Faults and ambiguous sequences must follow the agreed exception procedure.
Trigger loop versus presence loop
| Item | Trigger loop | Vehicle-presence loop |
|---|---|---|
| Primary task | Detect arrival for capture, terminal activity or an opening request | Provide occupancy information relevant to boom closing |
| Typical area | Approach or reader/terminal position | The vehicle zone associated with the boom |
| Signal use | A pulse or presence output, according to the application | A maintained presence output where required by the controller |
| Important limit | Arrival does not automatically authorize entry | Vehicle occupancy detection alone does not protect pedestrians |
Why loops remain useful
Inductive loops are an established way to detect vehicles and are available with different channel and diagnostic options. They can support LPR lanes, ticket terminals and card-reader systems without changing the identity credential. The practical trade-off includes road cutting, cable installation, surface repair, detector compatibility and maintenance. Familiar technology still needs a suitable design and commissioning.
Applications and site conditions
Car parks, offices, residential entrances and industrial premises can use separate authorization and presence inputs. The same principle also applies where manual approval or a ticket terminal remains in service. These are potential applications, not evidence that a particular Shunjie model has been installed or approved at every type of site.
Vehicle mix matters. Motorcycles, high-clearance vehicles, trailers and long combinations can produce different detection behavior. A queue, slope or nearby metal structure can change the usable layout. Record these conditions before deciding the loop geometry and required supplementary protection.
Common problems and a sensible check order
| Symptom | Possible causes to investigate | Useful evidence |
|---|---|---|
| Boom starts closing too early | Incomplete zone coverage, an interrupted presence output, wrong input assignment or closing sequence | Observe detector and controller states through the full passage with the lane controlled |
| Boom remains open | Zone still occupied, detector fault, damaged loop, unsuitable settings or an uncompleted sequence | Compare the clear lane with detector indicators and controller diagnostics |
| False or unstable detection | Interaction between loops, cable damage, moisture or unsuitable installation/settings | Record fault indicators, nearby equipment and conditions when the symptom occurs |
| Some vehicles are missed | Geometry or sensitivity unsuitable for the actual vehicle mix | Test the relevant vehicle types using the manufacturer’s commissioning procedure |
These are investigation paths, not confirmed diagnoses. Isolate a malfunctioning lane from normal traffic and use the manufacturer’s service procedure. Do not bridge a detector input or disable protection to make the barrier close. Electrical measurements and adjustments belong to competent personnel with the relevant manuals.
Installation and acceptance checks
- Record lane width, boom travel, stopping positions, mounting space, drainage and the types of vehicles expected.
- Specify the detector output, controller input, presence/timeout behavior and reaction to loss of power or loop fault. A matching connector does not prove functional compatibility.
- Follow the selected detector’s instructions for loop construction, feeder routing, sealing, separation and settings. There is no single loop width or distance suitable for every barrier.
- Under controlled commissioning conditions, check stationary and slow vehicles, full clearance, closely spaced traffic, relevant vehicle types and fault indications. Never use a person beneath a moving boom as a test target.
- Document the accepted configuration, test results, operating instructions and maintenance responsibilities before normal use.
When additional protective devices are needed
Keep pedestrian routes separate from vehicle lanes where the layout allows. If people, cyclists or mobility aids can enter the movement area, the project needs an assessment of those risks and suitable protective measures. Adding an ordinary radar or photocell does not by itself demonstrate personnel protection.
Use devices explicitly suitable for the intended protective function, with the required controller monitoring, coverage, force limitation and validation for the installation. FEIG’s R-Loop application guidance, for example, distinguishes vehicle-only presence outputs from a specific person-protection configuration with additional conditions. That is a model-specific example, not a certification or compatibility claim for Shunjie equipment.
FAQ
Is LPR alone enough to prevent a boom hitting a vehicle?
No. Identification and authorization do not establish that the movement area is clear. The controller needs the detection and protective measures specified for the installation.
Can the trigger loop also be the presence loop?
Only if the equipment design and verified coverage support the required functions. Do not merge the two roles merely to save a detector.
Where should the presence loop go?
In the zone required by the selected barrier and detector design. “Before” or “behind” the cabinet is not enough information to set a universal position.
Can loops work with radar or infrared devices?
They can be combined where the controller and selected devices support it. Agree the wiring, signal logic, monitoring and acceptance tests; a list of sensor types is not proof of compatibility.
Why does the boom stay open after the vehicle leaves?
Check whether the detector or controller still reports occupancy, a fault, a timer or an incomplete passage sequence. Record the state before changing settings.
Are loops sufficient for every parking project?
No. Vehicle mix, road construction, lane geometry and the presence of people can require a different design or additional measures.
For equipment selection, review the barrier range and share your lane layout, controller details and detection requirements with Shunjie.
