USE CASE · VEHICLE GATE DETECTION

Vehicle gate detection AI
LiDAR + camera at the gate.

A portal-mounted LiDAR + camera pair identifies and classifies approaching vehicles at plant gates, weighbridges and in-plant intersections — truck, wheel loader, forklift, AGV — in real time. Drives gate control, traffic-light interlocks and routing. Works at night, in fog and in dust. Custom-built for your fleet and your existing gate infrastructure.

3–30 m detection range per portal
> 300/h vehicles per hour throughput
Day / night / fog / dust all-condition operation
Truck · loader · forklift · AGV per-class output
USE CASE  ·  Vehicle gate detection · LiDAR + camera fusion

Identify the vehicle at the gate, before it queues or blocks the lane.

Vehicle gate detection AI is a perception pipeline mounted at industrial plant gates, intersections and weighbridges that uses LiDAR and a calibrated camera to identify and classify approaching vehicles (truck, wheel loader, forklift, AGV) in real time and drives gate-control, weighing and in-plant routing decisions.

The pain is well-known to every plant operator. Existing gate automation relies on RFID tags, ANPR cameras and induction loops — and each one fails in a different condition. RFID assumes every vehicle carries a working tag, which falls over the moment a subcontractor, a hire truck or a maintenance vehicle turns up. ANPR cameras lose the plate in dirt, road spray, low sun or driving snow. Induction loops miss small vehicles, forklifts on rubber tyres and pedestrians altogether. The plant ends up paying a manual gate operator or living with a delayed gate, and the queue at peak shifts turns into measurable lost throughput.

Our approach fuses two sensors at the gate. A 3D-LiDAR delivers geometry-based detection that does not care about paint, lighting, dirt or weather — a truck has the silhouette of a truck whether it is clean, muddy or covered in road salt. A calibrated camera adds visual confirmation and, where the camera angle allows, fuses with existing ANPR for plate identification. A custom classifier — trained on your fleet, your wheel loaders, your forklifts, your AGVs — returns a per-vehicle class plus track ID, written directly into the gate PLC or the weighbridge controller. Pedestrians are detected as a separate safety class.

This is not an off-the-shelf SaaS. Every plant has its own gate layout, its own fleet, its own weighbridge interlock logic. We treat every engagement as a discovery + fixed-scope build, descending from our hub service Industrial Perception AI. Typically a retrofit: we add the sensor portal next to your existing gate, RFID reader, ANPR camera and weighbridge — we do not replace what already works. The code and the model are handed over to you at the end. Related capability: truck terminal LiDAR volume measurement.

„A gate that opens for the right vehicle and only the right vehicle pays for itself in queue minutes alone."

Built on the same perception stack we use for our LiDAR wagon-detection and truck-terminal volume pipelines — sub-5 cm geometry, two-second response.

Three stages

From approach to gate signal — three stages of the pipeline.

1 · Sensor at the gate

One LiDAR plus one calibrated camera mounted on a portal, mast or existing gate structure at the plant entrance, weighbridge approach or dispatch shed. Detection range 3–30 m, throughput beyond 300 vehicles per hour. IP65+ housings, dust-tolerant optics, runs in fog, snow, night and direct sunshine — no maintenance call when the weather turns.

2 · Vehicle classification + class-aware logic

The fusion classifier separates the scene into your vehicle classes — truck, wheel loader, forklift, AGV, passenger car, pedestrian — plus an "unknown" fallback. Class-aware rules let the gate open for trucks at the goods entrance, route loaders to the dispatch shed, hold the gate when a pedestrian is in the lane. Models retrained on your labelled data, not on a public benchmark.

3 · Gate-controller integration

Classification results write into the gate PLC, the weighbridge controller and the yard-management system over OPC UA, REST, MQTT or digital I/O. The gate opens, the weighbridge triggers, the event is logged with class and image evidence, the ticket hands off to ERP. Fuses with existing RFID and ANPR — we strengthen what you have, we do not replace it.

Pipeline architecture · #how-it-works

How the pipeline works — concretely.

We keep the architecture boring on purpose. Three loosely coupled stages, each one independently testable, each one swappable when the sensor stack changes. Built on the same stack we use across all our perception work: PCL, Open3D, OpenCV, PyTorch.

01

Portal capture (LiDAR + camera)

The LiDAR delivers a 3D point cloud of the approach lane — hundreds of thousands of points per frame at portal speed. The camera adds a synchronised colour image, lens-calibrated and time-stamped. Per-vehicle UUID assigned on first contact and carried through the full track. Raw data writes to local storage for audit trail and re-labelling.

02

Vehicle classification + ANPR fusion

The point cloud goes through ground removal, voxel down-sampling and a PointNet-style classifier trained on your fleet. The camera image goes through a CNN trained on the same labels — and, where the geometry allows, into the existing ANPR pipeline for plate readout. The heads fuse into a per-track class plus optional plate ID. Pedestrians are detected as a dedicated safety class with a hard interlock.

03

Gate-PLC write-back + event log

Per-vehicle output: class, track ID, plate (if read), timestamp, audit image. Writes to the gate PLC or weighbridge controller over OPC UA — or to the MES, ERP, yard-management system, whatever the plant already runs. Every event is logged with image evidence; the dashboard shows live vehicle positions across the gate area.

All three stages run on an industrial PC in the gate cabinet. No cloud dependency, no external API, no licence dial-home. The code is yours at handover.

What you get

Three deliverables — from the same pipeline.

Per-vehicle event log

Every gate pass gets a structured record: class, track ID, plate (if read), timestamp, audit image, gate decision. Drops into ERP, into yard management, into the security audit trail. Searchable per shift, per supplier, per vehicle type — and useful for the incident report nobody wants to write from CCTV scrubbing.

Gate-control automation

The gate opens — or stays closed — based on classification plus your business rules: trucks at the goods entrance, loaders at the dispatch shed, only forklifts inside the warehouse aisle. Queue logic handles back-to-back arrivals without bouncing. The manual gate operator becomes an exception handler, not a full-time role.

In-plant traffic dashboard

Live view of which vehicles are where in the plant — gate counts, weighbridge throughput, dispatch-shed approach queue, forklift movement in the warehouse aisles. Same temporal model we use on stockpile monitoring — applied to vehicle tracks instead of material piles.

Why custom

Why a custom build — not an off-the-shelf product.

Every plant has its own fleet, its own gate layout, its own existing RFID, ANPR and weighbridge infrastructure. A generic classifier solves the generic case; your case is not the generic case.

Site-specific class library

Your fleet is not the public benchmark. Your wheel loaders, your forklifts, your AGVs, your subcontractor trucks — we calibrate the model on your vehicles under your gate lighting and dust conditions, and we re-calibrate when the fleet changes or a new subcontractor comes on site.

Retrofit-friendly — keep your existing gate

We add the sensor portal next to your existing gate motor, boom barrier, RFID reader, ANPR camera and induction loop. The mechanical gate stays, the existing automation stays, the cabling stays. We add a perception layer that takes the failure cases off your plate — dirty plates, missing tags, small vehicles.

Integrates with weighbridge, ANPR, RFID, gate PLC

Most plant gates already run a weighbridge controller, an RFID reader, an ANPR camera and a gate PLC. We fuse the classification output into what is already there — we do not replace your gate-management system. OPC UA, REST, MQTT, digital I/O and analog outputs all supported.

IP ownership + clean handover

You own the source code, the model weights and the labelled dataset at handover. We document the system, train your team, and walk away clean. No black box, no monthly per-vehicle licence, no service contract you cannot exit. See our FAQs on IP and engagement model for the standard terms.

FAQ

Questions about vehicle gate detection AI.

The engagement-model questions we hear from every plant operator considering a custom perception build for the gate. Need something more specific to your site? Ask us.

Industrial Perception AI

What does custom perception AI software cost? +
We don't publish list prices because every project is scoped against your data and your decision logic — but we work to three predictable tiers. Discovery & Assessment — a 1–3 day workshop, on-site or remote, fixed price in the low-four-figure range. You receive a written feasibility note, a recommended next step and (if applicable) a fixed-price quote for the follow-on project. Useful even if you don't then go ahead — many customers use the note to evaluate two or three vendors. Custom Pipeline / Tool — a 4–12 week project delivering a working perception pipeline (parser + algorithm + dashboard or OPC UA integration). Fixed scope, fixed price, you own the code at handover. Typical project size is in the mid-five to low-six-figure range depending on data volume, sensor count and integration depth. Long-term Partnership — a monthly retainer for ongoing development and on-call support. Sized to the team capacity you need (typically 0.5–2 FTE equivalent). Quarterly road-mapping included. All three tiers include source code, written documentation and a clean handover — no licence dependence on us. See our Industrial Perception AI service for the full engagement model.
How long does it take to build a custom perception pipeline? +
From signed contract to a working tool in production, expect 4–12 weeks for a standard custom-pipeline engagement. The spread is driven by three factors. Data readiness. If you already have labelled data or representative recordings, we start training in week 1. If we need to set up data collection, add a sensor, or label from scratch, the front end adds 1–3 weeks. Integration depth. A standalone dashboard with REST output is the fastest path — typically 4–6 weeks. OPC UA integration into a running control system, with interlocks, factory-acceptance tests and a customer change-management process, is closer to 8–12 weeks. Sensor count and site complexity. One LiDAR + one camera in a clean indoor environment is faster than a six-sensor outdoor portal with dust, snow and dynamic lighting. We scope the difference up-front in the Discovery workshop. For a faster first signal we recommend the Discovery & Assessment tier — 1–3 days, fixed price, written feasibility note within a week. See Industrial Perception AI for the full model.
Who owns the code and IP we pay you to build? +
You do. Our standard contract transfers full ownership of the project-specific code, model weights, training data (where the data is yours) and documentation to you on final acceptance. We don't keep a back-door licence and we don't lock you into a maintenance contract. What we retain is our pre-existing toolbox — reusable libraries, calibration utilities, generic data parsers, the OWL EYE® core — which we license to you, royalty-free, for use on the delivered tool. This is the same boundary that any reputable engineering firm draws: we bring the toolbox, you keep the deliverable. If you want a different IP arrangement — for example a joint patent on a novel algorithm, or a co-developed model that we both reuse with consent — we structure that explicitly in the project contract. Tell us up-front in the Discovery workshop. Full engagement details on our Industrial Perception AI page.
Can you use our existing cameras and LiDAR sensors? +
Yes — in most cases. Our toolchain is sensor-agnostic on the data layer. If your sensors deliver a standard format (PCD, LAS, E57 for point clouds; RTSP, GigE Vision, USB3 Vision for cameras) we can ingest them in a day. We've worked with Riegl, Livox, Faro, Hesai, Velodyne, Ouster, Basler, FLIR, Allied Vision and IDS cameras. We'll tell you honestly when the existing hardware isn't the right tool. Common cases where we recommend a replacement: - The existing LiDAR is too narrow (FoV or range) to cover the area you want classified — usually solved by repositioning before buying anything new. - The camera is auto-exposing on a high-contrast scene (sun + shadow at a gate), which breaks classification reliability — solved by switching to a manual-exposure industrial camera with HDR sensor. - The existing sensor's vendor lock-in (proprietary stream format, no documented SDK) makes integration cost more than a Livox replacement. We don't earn a margin on reselling hardware to you. If you do want us to source new sensors, we do that through our normal Hardware & products channel at list price. See Industrial Perception AI for how we scope it.

Send us a scan from your gate.

A few sample point clouds from your gate or weighbridge approach, a list of vehicle classes you need to distinguish, your existing RFID / ANPR / PLC setup — we come back within two business days with a written feasibility note and a fixed-price scope for the discovery workshop. Part of our Industrial Perception AI service.

info@sachtleben-technology.com +49 7831 969 22-190
Send us a message

Tell us about your plant gate.

Gate layout, fleet description, existing RFID / ANPR / weighbridge setup, sample point clouds — anything you have. We come back within two business days with an honest first assessment and a fixed-price scope for the Discovery workshop.

Company address (optional)Firmenadresse (optional)Adres firmy (opcjonalnie)Indirizzo azienda (opzionale)Adresse de la société (facultatif)Dirección de la empresa (opcional)Endereço da empresa (opcional)
Direct line Direktwahl Telefon bezpośredni Linea diretta Ligne directe Línea directa Linha direta
Mon — Fri · 08:00 – 17:00 CET Mo — Fr · 08:00 – 17:00 Uhr Pn — Pt · 08:00 – 17:00 CET Lun — Ven · 08:00 – 17:00 CET Lun — Ven · 08:00 – 17:00 CET Lun — Vie · 08:00 – 17:00 CET Seg — Sex · 08:00 – 17:00 CET
Email E-Mail E-mail Email E-mail Correo electrónico E-mail
Response within one business day. Antwort innerhalb eines Werktages. Odpowiedź w ciągu jednego dnia roboczego. Risposta entro un giorno lavorativo. Réponse sous un jour ouvré. Respuesta en un día laborable. Resposta em um dia útil.
Headquarters Unternehmenssitz Siedziba główna Sede principale Siège social Sede central Sede
Sachtleben Technology GmbH
Tresdorf 6
24238 Mucheln
Germany Deutschland Niemcy Germania Allemagne Alemania Alemanha
Last updated: