Vehicle Detection and Safety Inputs for Barrier Gate Projects

This guide helps integrators separate access decisions, vehicle detection and movement protection before choosing hardware. Our Automatic Boom Barrier Gates category shows the gate family; the selected controller manual and local safety design determine compatible devices and wiring.

Write the lane sequence first

Begin with a normal vehicle visit: detect arrival, identify the user, make an access decision, command the arm, observe passage and close only under the agreed control and protection conditions. Then add the cases that cause operators trouble: an unreadable credential, a driver who reverses, a closely following vehicle or a detector fault. Each case needs an expected system response, not just a drawing of where the sensors sit.

The sequence also clarifies ownership. The access system may decide who is authorized; the barrier controller manages arm movement according to its inputs. Document the signal between them and the state returned to the operator. “Access granted” is not the same event as “boom fully open,” and neither proves that the area is clear for closing.

In an office parking entrance, employee arrival peaks and visitor exceptions may make this sequence especially visible to users. The site workflow should be defined before the installation team chooses detector locations.

Give each input one clear purpose

An inductive loop is commonly used for vehicle presence, but it should not be assumed to detect pedestrians or every two-wheeler. A photoelectric beam detects an interruption at its installed line of sight; that does not mean it covers the entire lane. A device’s intended safety role depends on its specifications, position, controller compatibility and applicable local requirements. The table defines functions to evaluate, not a universal bill of materials.

Survey the physical area each device can see

Mark the stopping point, boom sweep, vehicle path and nearby pedestrian routes on a lane drawing. Check how small cars, motorcycles where permitted, vans and vehicles with trailers move through the proposed detection area. For optical devices, assess line of sight, likely blockage and exposure to sunlight, dirt and vehicle lights. Device placement and the actual vehicle mix need testing; a product datasheet cannot prove that this lane will detect every object.

Document what happens when a vehicle arrives from the wrong direction, stops between detection points or backs away before entering. If lanes are close, verify which input belongs to which lane. Ask how loss of power, a broken cable or a failed sensor is represented to the controller; a generic “normally closed” or “normally open” label does not explain the behavior of every fault. Use the actual device-controller combination in the test.

An installation drawing should show more than a generic sensor icon. Record the device location, mounting method, cable path, input terminal, expected active state and the event it should produce. This makes field testing reproducible and later replacement safer.

Agree on the controller’s response to each state

For each input, define normal, active and fault states. Record the expected response while the arm is opening, fully open and closing. “Open request,” “hold open” and “interrupt closing” are different controller functions. Some devices may be monitored for faults, others may not be; the controller documentation must identify which functions and supervision methods are available.

The supplier should provide the current controller manual and a project-specific wiring schedule, including selected accessory models, power supply and input assignments. A CAME barrier installation manual illustrates why input behavior must be read from the actual controller documentation; it does not establish Zibor Park wiring. The Accessories & Spare Parts page is a starting point, not proof that a part fits every gate. Verify compatibility with the exact model and controller version before procurement.

Define what operators see when the lane is held open or a safety input is active. If a fault only appears as “gate not closing,” staff may be tempted to bypass the device. A clear fault message and escalation path are more useful than an unexplained timeout. Any override procedure must be controlled and reviewed against the site’s safety requirements.

Commission with observed tests, not only controller settings

A control-panel setting can be correct while the detector is in the wrong place. Commissioning needs both input-state checks and observed vehicle movements. The qualified installer should use a site-approved test plan and keep people clear of the boom’s movement area.

Test normal entry and exit, a vehicle that stops before the arm, a vehicle that remains in the controlled area and an interrupted identification attempt. The installer should also check the documented response to a sensor or cable fault using the manufacturer’s approved procedure. Record the test condition, expected response, observed response and corrective action. Fault testing and local safety acceptance belong to qualified personnel; this article is a specification guide, not a field wiring instruction.

After any adjustment to timing, sensor position or lane markings, repeat the affected tests. A successful demonstration with one passenger car does not establish performance for all vehicles using the site. The owner should sign off on the tested vehicle mix and exception workflow.

Put the decision in the project handover

The handover pack should include the lane drawing, controller version, wiring schedule, accessory models, test records and instructions for investigating a held-open gate. Identify which devices are standard in the quoted gate package and which are project-specific additions. This prevents a later service technician from guessing why an input was installed.

For a new lane, send the drawing, vehicle mix and intended access sequence when discussing Zibor Park barrier gates. We can help identify which controller and accessory documents the project team needs to review before finalizing the site-specific design.