Configuration
Here you will find information on how to successfully connect and configure the camera.
Last updated
Here you will find information on how to successfully connect and configure the camera.
Last updated
To call up the configuration page of the devices, simply click on the respective device in the “Devices” list view. You can use this to manage all cameras that are processed on this device.
We recommend a logical naming scheme for the devices at this point.
Click on one of the cameras displayed to open the settings for the respective camera. As soon as you have configured the camera connection, you will see a preview of the camera image.
In the configuration, you can select the model suitable for your use case and configure event triggers. Please consult the corresponding section in the solution areas.
Solution areasBelow you will find a brief description of each model. Different models are recommended depending on the solution area.
Traffic & Parking (standard): Recognition of 12+1 object classes in the context of traffic and parking.
Traffic & Parking (Accuracy+): Recognition of 12+1 object classes in the context of traffic and parking. Optimized for higher accuracy at a processing speed of about half (measured in FPS) compared to “Traffic & Parking (Standard)”
See class definition for a detailed description of the classes.
Event triggers trigger an event when a defined condition is met.
Counting lines (CL) trigger a count as soon as the center of an object crosses the line. When configuring a CL, it is important that the camera perspective is taken into account.
The CL also logs the direction in which the object has crossed the line in the In and Out direction. You can swap the In and Out direction at any time. In addition, a separate name can be assigned for the two directions.
By default, a CL only counts each object once. If every crossing is to be counted, there is an option to activate events for repeated CL crossings. With the restriction that counts are only taken into account if there are five seconds in between.
In addition to the repeated CL crossings, ANPR and Speed Estimation are also available as triggers or settings.
Speed Estimation_ can be activated as a special trigger setting for a CL in the left sidebar. This adds another line that you can use to specify the distance in your scenario. For the best results, we recommend a straight line without curves/slopes.
Your devices send events to an MQTT broker when a trigger is triggered. The standard configuration sends data to the data center. Custom-MQTT allows you to send events to an MQTT broker provided by you, the definition of the event format can be found here.
Message compression can save up to 50% bandwidth used to send events to the MQTT broker. Please note that the broker and application must support decompression of zlib / inflate.
