Planning Access Control at Car Parks and Residential Entrances

Entrance planning starts with who uses each lane and how vehicle detection combines with access permission. The output is an entrance-plan record bringing together dealer-supplied passage data, control sequence and outage expectations.

Decision sequence for access control

1. Record entry/exit lanes, vehicle types and a separate pedestrian route. Distinguish physical closure from traffic regulation.
2. Choose a barrier, sliding gate or both. Add clear passage after cabinet, support and manoeuvring allowances to the dealer-supplied drawing.
3. Assess the full permission–opening–vehicle passage–waiting–closing cycle at peak time.
4. Identify which device detects presence, which grants permission and which command reaches the controller.
5. Define lost transmitter/card, visitor and outage scenarios. Mark deletion methods affecting all records separately.
6. The dealer’s technical team records detection, safety, closing sequence and manual-operation results on the installation.

Barrier or sliding gate?

The two products do different jobs, and on most projects the choice follows the security requirement.

A barrier regulates vehicle passage but does not fully close the opening to pedestrians or cyclists. Its opening time and duty limits are checked for the exact model and arm; the traffic profile, visitor control and any weighbridge sequence determine suitability.

A sliding gate closes the opening and can provide a physical boundary outside working hours. Its passage time depends on opening width, model speed, acceleration and control settings; no single time applies to all sliding gates.

At many sites both are used: the barrier manages flow by day, the gate closes the site at night.

Boom length and installation position

Boom length is not clear passage. Draw cabinet, support, resting position and vehicle movement together. Use the selected current FRIG or TROYA model’s document for dimensions and times; old DINAMIX or WM values do not transfer to a new sales name.

Agree foundation, structure and cable routes before concrete work. A need for wall mounting does not establish that the current range offers it; assess that condition with the partner.

Passage time includes permission checks, opening, vehicle travel, dwell and closing. Assess peak queues using the full sequence.

Detection and authorisation

Access control has two distinct layers that should not be confused: detection says a vehicle is there, authorisation says it has the right to pass.

• A loop detector senses vehicle presence. The UltraII sheet’s 3 cm × 5 cm channel, five turns and box 25 cm from the controller are that document’s installation example. Dimensions, turns and position do not apply to all detectors; use the installed model’s manual and the dealer team’s application data.

• Card reader is selected by the required authorisation method and verified interface. The local site does not provide an exact reader datasheet establishing frequency, memory capacity or enclosure rating; these values are confirmed for the ordered model.

• Remote control must match the receiver’s protocol and programming rules. The G24 manual describes RF433 options and company-code restrictions; it does not establish one memory capacity or compatibility promise for all receivers.

• Plate recognition removes the need to carry a card or remote; resident and visitor separation is managed on the software side.

Verify revocation against the installed system when a card or transmitter is lost. RF433 FIX and ROLLING manuals describe erasing all transmitters, not one lost record. Delete-all or ROLLING mode changes affect other users too; prepare re-pairing. Individual card revocation needs the selected reader/software’s documented procedure.

Adjacent entry and exit lanes

Assess interference between neighbouring loops through layout and detector settings. The chosen detector’s manual defines frequency options. Channel size, turns and box position are not a universal recipe. A competent team verifies detection and the control sequence with actual vehicles at commissioning.

What happens during an outage?

If the entrance must keep working during a power cut, plan a backup supply and manual release from the start. A battery option is not identical across motors and controllers; confirm compatibility and wiring in the selected model’s manual. Runtime or cycle count during an outage depends on the battery and installed system and should be tested on site before a figure is promised.

Electric vehicle charging on the same project

If EV charging is included, assess total load and panel protection separately. WCU-22 documents 400 V three phase/32 A and up to 22 kW, no built-in RCD and external 30 mA protection at the panel. Load management must be verified for the ordered configuration.

Entrance plan and handover record

Scenario	Planned behaviour	Result to record
Authorised vehicle	Permission → detection → allowed movement	Reader/receiver, input and control sequence
Vehicle detected, no permission	Detection alone grants no access	Control logic preserves the distinction
Lost transmitter	Revocation method supported by the model	Individual/all deletion, affected users, re-pairing
Outage	Verified manual/battery method	Installed equipment and tested behaviour
Adjacent lane	Loop inputs should not interfere	Detector/settings and vehicle-test result

The output contains the lane drawing, device/interfaces, permission/detection sequence, deletion scope and outage behaviour. The dealer submits unresolved model pairings for manufacturer assessment. Alkur does not survey sites or install the entrance.

For movement, photocell, limit or transmitter symptoms, use the model-specific checks in r-tec Error Codes and Fault Symptoms.