Configuration

Management of your devices

To access the device configuration page, simply click on the respective device in the "Devices" list view.

Tipp

Use a logical naming scheme for your devices to keep the configuration organized.

Camera configuration

Clicking on one of the displayed cameras opens its settings. Once you've configured the camera connection, you'll see a live image.

Data transmission

Your devices send events to an MQTT broker whenever a trigger condition is met.

Custom MQTT lets you send events to an MQTT broker that you provide. The event format definition is available here.

Use the ssl:// prefix for the broker address to enable transport encryption.
Message compression can save up to 50% of the bandwidth used to send events. Ensure that both the broker and the consuming application support decompressing zlib/deflate payloads.

IO connection

The IO connection enables external IO devices that receive on/off signals to drive outputs. Define an ROI or a Crossing Line and combine it with one or more rules. Each rule allows you to select a desired IO output.

Output behavior is configured per camera stream. Enable IO device and select the required Family for the connected IO device.

Supported IO device families:

Family	Description
BMC	Uses potential-free contacts. Up to 12 contact outputs can be configured. The BMC connects up to 4 BMAs and is used as an interface between BMA TLC and a traffic light controller. An optional error output can be configured.
Quido	Uses potential-free contacts. Supported variants are Quido 4/4, Quido 8/8, and Quido 2/16 with 4, 8, or 16 outputs. Control Center warns if the same output is assigned more than once.
XKOPMV	Ethernet-based protocol for traffic light controllers. Each camera stream uses its own IP address and port. Up to 12 contacts can be configured for each stream.

Rules and outputs are configured in Models & Event Triggers. Rules can be based on a Region of Interest (ROI) or a Crossing Line (CL):

For an ROI, the output remains active while the configured condition is fulfilled.
For a Crossing Line, the output closes briefly when the configured rule is fulfilled.
With Presence and Counting, the output remains active while at least one matching object is present in the ROI and briefly toggles when a new matching object enters the ROI.

One contact can be used as an error output to signal device errors to the controller. For details, see Configuration of the error output.

Models & Event Triggers

In the configuration, you can select the model that suits your use case and configure event triggers. For guidance, consult the corresponding section in the solution areas.

Configuration of the model and event triggers

Models

Below you will find a brief description of each model. Different models are recommended depending on the solution.

Traffic & Parking (Standard)

Detection of 12+1 object classes in the context of traffic and parking.


Typical use cases	Traffic counting Turning movement counting Traffic flow Adaptive traffic control Barrier-free parking
Classes	car van car with trailer single unit truck articulated truck truck with trailer bus tram motorbike person bicycle scooter other See the class definition for a detailed description of the classes.

Traffic & Parking (Accuracy+)

Detection of 12+1 object classes in the context of traffic and parking. Optimized for higher accuracy while processing with roughly half the speed (measured in FPS) compared to Traffic & Parking (standard).


Typical use cases	Parking – Single Space Detection
Classes	car van car with trailer single unit truck articulated truck truck with trailer bus tram motorbike person bicycle scooter other See the class definition for a detailed description of the classes.

ANPR

ANPR detects single-line and two-line number plates and recognizes plate text, area code, and country code.


Typical use cases	Parking – ANPR
Format	EU licence plate standard format Examples of single-line Examples of two-line
Classes	numberplate
Countries	EU countries + (Switzerland, Norway, Liechtenstein)
Recognition of region of the licence plate	Austria, Germany, Swiss, Bulgaria, Czech Republic, Greece, Croatia, Ireland, Norway, Poland, Romania, Slovakia, Slovenia

What is the difference to Traffic & Parking (with Parking Mode ANPR)?

Traffic & Parking (with Parking Mode ANPR) first detects a vehicle and then detects a number plate within that region. ANPR mode skips vehicle detection and instead detects number plates within the full camera image. Both modes use the same underlying ANPR models for plate detection, classification, and recognition.

In comparison to Traffic & Parking (with Parking Mode ANPR enabled):

Only the number plate must be clearly visible; the full vehicle is not required, and only the plate is pixelated in Control Center.
All number plates in the camera frame are detected; vehicles with multiple plates (for example, trailers) are fully captured.
No other objects like cars, buses, or people are detected or classified.
Only available via custom MQTT connection; Data Center is not supported.

People: Full Body

The full body of a person is detected.


Typical use cases	People counting
Classes	Person

People: Head

The head of a person is detected, beneficial if the full body is not visible and if distance to objects is less than 5m.


Typical use cases	People counting
Classes	Person

Event triggers

Event triggers create an event when a defined condition is met.

Crossing Line (CL)

A Crossing Line (CL) triggers an event as soon as the center point of an object crosses the line.

The CL also logs the direction of travel in which the object crossed the line, distinguishing between In and Out directions. You can swap the In and Out directions at any time. Furthermore, a custom name can be assigned to both directions.

By default, a CL counts each object only once. If every crossing is to be counted, there is an option to activate events for repeated CL crossings, with the caveat that counts are only considered if there's a five-second interval between them.

Enable Attach movement path to event to include up to 10 track points in the payload; if a path has more than 10 points, intermediate points are skipped.

Speed estimation can be activated as a trigger option for a CL. Configure the physical distance in meters between the lines. For optimal results, use a straight section without curves or inclines.

Region of Interest (ROI)

A Region of Interest (ROI) consists of four points that form an area. An ROI triggers an event after a defined time interval or when the occupancy changes from occupied to unoccupied (or vice versa).

Options

Description

ROI type

Generic: Default mode. Detects objects whose center is inside the ROI.
Directed: Detects objects entering the ROI from a specified direction (tolerance ±60°).
Occlusion: Detects objects whose center is inside the ROI or that fully occlude the ROI with their bounding box.
Parking: Deprecated and not supported by the Data Center. Use Generic instead.

Trigger action

Time: By default, an event is generated every 10 seconds. The time can be adjusted.
Occupancy: An event is generated when the ROI's occupancy changes. If the number of detected objects in the ROI reaches the defined maximum capacity, the ROI is considered occupied.
Rule: If a rule has been defined for the ROI, this field becomes active. By default, an event is generated at most every 10 seconds; this cooldown period can be adjusted.

ROI type "Directed"

The valid range for entry angles of a directed ROI is represented in the Control Center by the three arrowheads in the ROI. The following image shows examples of valid (green) and invalid (red) entry angles of object trajectories. Tracks that start within a directed ROI are always considered valid, regardless of direction.

Origin-Destination Zone (OD)

An event is triggered when an object's trajectory has moved across at least two OD zones, with the first and last zones of the event being used.

The first zone an object passes through is called the Origin zone, and the last zone the object passes through is called the Destination zone. The event is triggered when the object's sighting ends, for example, when the object moves beyond the edge of the image.

Raw Track Event

A Raw Track Event records the full trajectory of an object. The trigger fires once the track is finished—for example, when the object leaves the camera view.

Focus Zone

A Focus Zone defines an image area where object detection for tracks is considered. Object detection is active even outside the Focus Zone, but objects detected outside it aren't used for creating tracks. This means objects are pixelated throughout the entire image, regardless of the Focus Zone.

Classification and license plate recognition (if activated) only occur for objects detected within the defined Focus Zone.

Using Focus Zones allows for targeted system optimization:

Improved Tracks: The Focus Zone can limit where tracks are formed. For instance, Focus Zones can be defined to exclude the image's border areas, preventing unwanted merging of tracks.
Improved Classification: The Focus Zone can restrict the area where classification takes place. For example, areas where vehicles are too small for successful classification can be excluded by Focus Zones.
Increased Performance: Concentrating on essential image sections reduces the computational effort for classification and license plate recognition (if activated) for objects. This positively impacts the accuracy of object tracking, classification, and potentially license plate recognition.

Calibration

Live Calibration

For optimal system calibration during commissioning, Live Calibration provides a real-time visualization of detected and classified objects. In addition, it also displays the triggering of events and rules – including the associated BMC contacts.

Features

Object Detection & Classification
Objects detected by the selected model are highlighted with bounding boxes.
The center point of each object is tracked and visualized as a trajectory.
To ensure privacy, objects are pixelated.
Overlays are color-coded according to the object class (e.g., Green = Car, Violet = Truck, Pink = Bicycle). A legend on the right-hand side explains the applied colors and classifications.
Rules & BMC Contacts
Configured rules are displayed in an overview in the upper left corner of the screen.
The following information is shown:
- Rule name
- Time of the last trigger
- Optionally, the associated BMC contact
Status display:
Gray = Rule inactive
Red = Rule active

Track Calibration

The Track Calibration is an important tool for optimal positioning of the Event Triggers: It displays a live camera image and overlays it with the last 100 tracks, where each track visualizes the trajectory of a detected object.

Track Calibration helps to determine:

How objects and their tracks were classified.
If tracks are continuous or interrupted, for example by obstructions.
From what point objects are large enough for classification.

ANPR Calibration

The ANPR calibration is used for visual verification and fine-tuning of automatic license plate recognition. ANPR calibration enables:

Optimization of device mounting and alignment for optimal automatic license plate recognition.
Optimal positioning of Crossing Lines for optimal results.
Diagnosis of the data quality of license plate acquisition.

Tip

Set the crossing line at the end of the green tracks in the direction of travel.

ANPR overlay description

The most recently recognized license plates (top-left in the image):

The Crossing Line name, direction of travel, and time of the last five recognized license plates are displayed.
The recognized license plate text and image cutout are shown, allowing for manual verification of the results.

Color-coded trajectories in the focus area (center of the image):

Real-time camera image with color-coded trajectories for vehicle movements and ANPR recognition quality.
🟢 Best ANPR: Optimal recognition – license plates were read correctly.
🟠 Inconsistent ANPR: Ambiguous or unstable recognition.
🔴 License plate not detected: Vehicle detected, but no license plate found.
🔵 Object too small for ANPR: Vehicle too far away or too small, ANPR not possible.
⚫ Class not relevant for ANPR: Object detected, but the vehicle class is not relevant for ANPR (e.g., pedestrians, bicycles, scooters, trams).

Focus Zone: A rectangular detection area with an orange border, within which ANPR recognition occurs.

Camera settings

Digital zoom

Object detection can be improved by increasing the digital zoom to exclude irrelevant areas of the full camera image. This can also increase the effective detection distance because distant objects appear larger in the processed camera view.

In the following example, the houses beside the road and the sky above are not relevant for object detection.

By clicking the Camera settings button, the digital zoom level can be adjusted. Move the red zoom area by dragging the corner points or by using the zoom in/out buttons below. Existing event triggers are automatically adjusted to the new zoom level.

After applying the settings, the camera image will display the zoomed-in view.