Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
1 x BMA
2 x Pole mounting clamps
1 x Power cable
Mounting process on a light pole
The camera is attached to the pole by using clamps. These adapt to the diameter of the pole.
A hole is drilled underneath the camera, where the cable gland with seal is then screwed in place. The cable is fed through the pole to the ground at this point. At the other end of the cable is the appropriate plug (2 or 3-pin) for the BMA
There is a cover in the lower section of the light pole. This can be opened with a special key to get the battery inside the pole. The power supply with plug or terminal strip should also be located here.
There is a two-pin plug on the battery that is used to charge the battery and a two-pin cable that is used to power the camera. If a terminal strip is available instead of a connector strip, the connector can be disconnected and the cables can be clamped directly into the terminal strip.
Diameter min. 10 cm
Input voltage | 230 V AC with integrated charge controller |
---|---|
Output voltage
12 V DC
Energy reserve
18 h
Maximum power
21 W
Capacity
380 Wh
L x W x H
790 mm x 80 mm x 62 mm
Connections
for the camera: 3-pin connection for the power supply type F plug
Release date: 25.09.2024
The B101 and B401 with passively cooled housings are ideal for installation in control cabinets. Typical solution areas are parking space monitoring and traffic surveys.
The B101 and B401 differ in their performance and therefore in the number of streams that can be processed in parallel.
-> See details
Products (BMA, Mobile BMA, BCA, B101/B401)
Update size: ~130MB
Long tracks are displayed as a continuous line in Live/Track calibration
MQTT connection establishment does not lead to a delay in image/event processing
Watchdog for LTE connections
Corrupt caches are automatically rebuilt
Simple configuration of parking spaces, divisible into several groups. These settings are supported:
Balanced parking, i.e. one or more crossing lines record entries and exits.Manual calibration by the operator is possible.
Single and multi-space parking, i.e. ROI configured for single or multiple parking spaces.
Internationalization
Data Center is now available in English. The language is automatically selected based on the language configured in the browser.
Robustness
Behind the scenes, we have revised the event processing and infrastructure required for the data center in terms of resilience and scalability. This means that the data center is ideally equipped for increased event and user volumes in the future.
Bugfixes
Config App - Saving crossings for existing turn-offs possible
Config App - All ROIs can be added
Improvments
Bugfixes
ANPR-option available for B401
Correct device connectivity state after moving between tenants
Devices available after reprovisioning
Fallback for connection status in case of an Azure infrastructure issue
The Data Center can be selected as a configuration and is set as the default option for event processing.
The internal BMA camera can be selected directly as a configuration.
An intelligent optical system for monitoring road users and the flow of traffic. of the traffic flow
To ensure successful charging of the battery box, the following steps must be followed in the order indicated:
Charger is disconnected from the mains (must not be connected to 230 VAC!)
Connect charger and rechargeable battery
Connect charger to mains (230 VAC)
<Charging in progress...>
Bulk LED = charging in progress
Absorption LED = charging in progress
Storage LED = charging process completed
Disconnect charger from mains (must not be connected to 230 VAC)
Wait <30 seconds>
Disconnect charger and battery
Test: After successful charging, the voltage of the battery should be at least 13.5 VDC
BMA specifications
Data transfer | |
---|---|
General | Variant AC | Variant DC |
---|---|---|
Certification | |
---|---|
The BMA processes personal data only vaguely, without storing it and only for the purpose of anonymization. This is done on the basis of Art. 6 para. 1 f) GDPR, namely in the legitimate interest of the operator. Only the anonymous data is then used to carry out traffic management. The BMA complies with the Low Voltage Directive 2014/35/EU and the Electromagnetic Compatibility Directive 2014/30/EU. This resulting CE certification is attached to the bottom of the device.
The supplier assumes no liability for compliance with local requirements or additional certifications that may be required in certain regions or markets. It is the responsibility of the purchaser or user to ensure that the product complies with local regulations and specific requirements that may go beyond the specified certifications. The supplier disclaims all liability for any damage or loss that may result from non-compliance with such additional requirements.
Release date: 19.06.2024
The BERNARD Mobility Controller (BMC) serves as an interface between BMA and the control unit of the traffic signal systems, up to 12 potential-free contacts can be switched. The BMC supports up to 4 BMAs. The 2-wire connection cable serves both as a communication channel for switching commands between the BMA and BMC and as a power supply for the BMA. (Data sheet and Operating instructions))
The configuration is carried out centrally in the browser via the Control Center
The event trigger "Region of Interest" (ROI) in combination with Rules is supported.
Multiple ROIs can be defined. Several rules can be assigned to each ROI.
Rules enable contacts to be switched when a person or an object is present (presence). They can be combined with filters for vehicle classes, number of objects or length of stay of the objects.
Note: Support for the event trigger "Crossing Lines" is planned for future releases, but ROI can also be used for counting.
To be able to use this feature, the latest device update must be installed.
The Classification has been improved, especially the classes Single Unit Trucks and Vans. This affects the Traffic& Parking - Standard and Accuracy+ models.
Event format extension: In addition to trackId, the trackUuid is also issued. See Event Schema for details.
The improvements mentioned are available for the following products:
BMA, mobile BMA, BCA, B101, B401
P101, OP101, P401, VPX
To use this feature, the latest device update must be installed.
GDPR-compliant recording of parking times or country and region of the license plate number
Parking times up to 72 hours long
No saving of image data on the device or in the cloud
No saving of license plates. The license plates are pseudo-anonymized with a hashing process on the devices and anonymized in the cloud after exit matching.\
The improvements mentioned are also available for the following products:
BCA, B101, B401
P101, OP101, P401, VPX
To be able to use this feature, the latest device update must be installed.
Display of available or planned device updates\
All event triggers, focus area and camera stream-related parameters can be easily reset. This makes it easy to reconfigure temporary traffic surveys with the mobile BMA.
Bug fixes:
Configurations are reliably saved.
Camera images are reliably displayed in the Firefox browser.
Bug fix for the grouping of the turning movement counts
Good positioning and alignment of the optical sensor is crucial in order to guarantee optimum detection accuracy. Detailed instructions can be found in the Alignment of the BCA section.
The sensor is attached to the poles using clamps. These adapt to the diameter of the pole.
The compute module is attached to the poles using clamps. These adapt to the diameter of the pole.
The sensor is connected to the computer unit using the network cable supplied.
Finally, the computer unit is connected to the respective power supply (12V, 24V or 230V) using the power cable. The BCA then starts up and can be configured in the Control Center.
Technical documentation
Use this documentation to learn more about the technologies and products of Bernard Technologies and how to use them.
This is documentation is machine translated
This documentation is a technical guideline for you as a partner and client and generally anyone interested in integrating our software in a new or existing data analytic IoT environment.
Data streaming protocol
MQTT
Data encoding
JSON
Data transmission
LTE
Operating conditions
-20° C - +50° C
Power supply
220 - 240 V AC
12 / 24 V DC
Frequency range
47 - 63 Hz
N/A
Power consumption
230 V AC 50 Hz
14 W
Material
Housing: Polycarbonate Rain cover: Polycarbonate 3D printing
Protection class
IP65
Dimensions
210 x 155 x 140 mm (L x W x H)
Weight
2000 g
Mounting method
Pole mounting, clamping range 60 - 150 mm
GDPR-compliant
yes
1 x Compute module
1 x optical sensor
1 x Network cable
1 x Power supply cabel
4 x Clamps
The BMA processes personal data only vaguely, without storing it and only for the purpose of anonymization. This is done on the basis of Art. 6 para. 1 f) GDPR, namely in the legitimate interest of the operator. Only the anonymous data is then used to carry out traffic management. The BMA complies with the Low Voltage Directive 2014/35/EU and the Electromagnetic Compatibility Directive 2014/30/EU. This resulting CE certification is attached to the bottom of the device.
The supplier assumes no liability for compliance with local requirements or additional certifications that may be required in certain regions or markets. It is the responsibility of the purchaser or user to ensure that the product complies with local regulations and specific requirements that may go beyond the specified certifications. The supplier disclaims all liability for any damage or loss that may result from non-compliance with such additional requirements.
This guide focuses on specific details that need to be considered when capturing license plates. The focus is on the placement of the optical sensor, the camera settings themselves and the configuration of the event triggers.
Please note at this point that the camera settings must be adjusted according to the installation location, as lighting conditions may vary.
Perfect sensor placement is critical in order to get a clear image and readable number plates. While some parameters such as distance from the sensor to the number plate can be fine-tuned by zooming after installation, mounting height and angle between the sensor and travel direction of vehicles can only be adjusted by physical and cost-intensive re-arrangement. The sensor position has to be chosen in a way that passing vehicles are fully visible and can be captured throughout several frames of the video stream while making sure the number plates are large enough for the ANPR system to identify every single character.
We recommend mounting heights between 3 and 8 meters, therefore the suitable minimum capture distance ranges from 5 to 20 meters. Besides the vertical angle constraint, number plates should be visible with at least 250 pixels-per-meter (PPM), this constraint determines the minimum focal length (zoom) the sensor has to be set to.
Mounting height [m] | Minimum capture distance [m] | Maximum capture distance [m] | Range of focal length [mm] |
---|
Why between 3 and 8 meters of mounting height?
The lower bound of 3 meters is determined by rather practical reasons and not technical limitations. Sensors mounted lower than 3 meters are often prone to vandalism. Also, headlights from passing vehicles can lead to reflections on the sensor. The upper bound of 8 meters is determined by the resulting minimum capture distance of at least 14 meters for the needed camera resolution of 1920x1080p. License plates need to be visible with 250 pixel-per-meter (PPM).
As the compute module and sensor are mainly mounted on existing infrastructure such as traffic light poles, there are two general options to mount the sensors: side mounting or overhead mounting.
Overhead mounting
When positioning the sensorabove the vehicles, two lanes can be covered with one sensor.
Consider mounting height (1) and capture distance (2) which determine the vertical angle (3) between the sensor and the travel direction of the vehicle. The distance between the center of the lane (4) and the senosr determines the horizontal angle (5) between the sensor and the travel direction of the vehicle.
Side mounting
When mounting the sensor to the side of the road, two lanes can be covered, assuming the horizontal angle between the sensor and the travel direction of the vehicles is not exceeding 20°.
Position the sensor as close as possible to the side of the road to avoid a horizontal angle larger than 20°. Larger angles can lead to lower accuracy because parts of the number plate can become unreadable. While traveling directions (1) and (2) are the same for both vehicles, horizontal angle (3) is much larger than (4).
Instructions for setting up a mobile traffic survey.
Pay attention to the local legal regulations and find out whether a permit is required to set up the mobile system at the location you have defined.
Obey local regulations regarding the minimum distance from the roadway.
The mobile system should not block any driveways or footpaths.
The mobile system must not obscure any traffic signs.
Select a suitable location for the installation. Please note that the height of the system when the pole elements are fully extended is approx. 6 m.
the mobile system must be attached to a fixed infrastructure
take the telescopic mast incl. mounting bracket and position it on an existing infrastructure (e.g. light pole, pipe post, etc.)
Guide the supplied tensioning straps through the lugs (2x) of the mounting bracket and attach the tensioning straps to the pole you have selected (e.g. lighting pole, tubular post, etc.)
to prevent easy removal of the mobile BMA, install two padlocks through the ratchet element of the tensioning straps
place the BMA on the top element of the telescopic mast and fix it in place with a twist-and-push movement
attach the BMA to the back of the lower pole strap
use the supplied reusable cable tie and pull it hand-tight
connect the 2-pin black/blue plug to the BMA. Make sure that the plug is inserted straight
Next, connect the 2-pin gray plug to the back of the battery box and close the plug fuse
lift the battery box and place the battery box in the middle guide of the C-profile
if the battery box is in the correct position, you can insert a padlock through the hole at the lower end and close it
loosen the twist lock on the mast element and raise the mast to the desired height
close the twist lock firmly in a clockwise direction to prevent loosening due to vibrations
Do this for all 4 mast elements if the maximum height is reached
check the current alignment of the BMA using the Control Center
you can adjust the alignment around the vertical axis by rotating the mast element
to change the alignment around the horizontal axis, the mast must be fully retracted and the cover of the sensor opened
turn the optical part of the sensor up or down to obtain the desired alignment and close the cover of the sensor
carry out steps 12 - 14 again
finally, place the mast lock around the twist lock of the lowest mast element and secure it with a padlock
Now you can set your sensor via the Control Center and configure the current traffic survey in the Data Center
Technische Daten |
---|
*) for optimum alignment and calibration according to installation instructions
Data transfer |
---|
Allgemein | Variante AC | Variante DC |
---|
For parking space management, it is necessary to record license plates as well as images of vehicles entering and exiting in plain text so that evidence can be provided and penalties enforced. The data is only stored for this purpose and is limited in time, by default to 48 hours.
This mode may not be used in public spaces without permission and in accordance with applicable laws and regulations.
Statistical recording of the parking duration and countries/regions of the license plates is possible without storing the license plates. The license plates are pseudo-anonymized using a hashing process and thus form the data basis for determining the parking duration. A maximum parking duration of 72 hours can be recorded.
The BCA processes personal data only vaguely, without storing it and only for the purpose of anonymization. This is done on the basis of Art. 6 para. 1 f) GDPR, namely in the legitimate interest of the operator. Only the anonymous data is then used to carry out traffic management. The BCAcomplies with the Low Voltage Directive 2014/35/EU and the Electromagnetic Compatibility Directive 2014/30/EU. This resulting CE certification is attached to the bottom of the device.
The supplier assumes no liability for compliance with local requirements or additional certifications that may be required in certain regions or markets. It is the responsibility of the purchaser or user to ensure that the product complies with local regulations and specific requirements that may go beyond the specified certifications. The supplier disclaims all liability for any damage or loss that may result from non-compliance with such additional requirements.
Set up parameters | Recommended |
---|
General
Function
Mobile traffic surveys
Mounting
On poles using mounting brackets and tensioning straps
Protection
Tensioning straps and battery secured with lock
Battery/charger
Capacity
100 Ah
Output voltage
12 V
Max. runtime (during survey)
110 h (~4.5 d)
Max. runtime (standby)
245 h (~10 d)
Max. charging time
7.5 h
Connectivity
Technology
LTE
Protocol/Format
MQTT / JSON (event schema)
Environmental conditions
Temperature range
-20 °C to +50 °C
Protection class
IP65
Dimensions
Transport length of pole (retracted)
1.78 m
Maximum height
6.05 m
Weight BMA
1.4 kg
Weight telescope pole with mounting bracket
2.1 kg
Weight battery box
14.9 kg
Rev. 09/2024
1 x B101 / B401
1 x Cable with 2,5 / 5,5 mm DC-Jack
Pixels Per Meter is a measurement used to define the amount of potential image detail that a sensor offers at a given distance. | 250 PPM (vehicle) Using the camera parameters defined below ensures achieving the minimum required PPM value) |
Sensor mounting - distance to object center | 5-20 meters Please consider that the zoom needs to be adjusted according to the capture distance. |
Sensor mounting height | 3-8 meters |
Sensor mounting - vertical angle to the object | <40° Note: setting the correct distance to vehicle and sensor mounting height should result in the correct vertical angle to the vehicle. |
0° - 20° |
Function | Automatic license plate recognition |
Licence plate format | Examples: |
Countries | EU Countries + (Swiss, Norway, Lichtenstein) |
Recognition of region of the licence plate | Austria, Germany, Swiss, Bulgaria, Czech Republic, Greece, Croatia, Ireland, Norway, Poland, Romania, Slovakia, Slovenia. |
Lanes | max. 2 |
Day / Night | yes / yes (with IR) |
Accuracy (< 15km/h)* | 97% (Daylight or good lighting conditions) 95% (Night or poor lighting conditions) |
Accuracy (< 60km/h)* | 95% (Daylight or good lighting conditions) 85% (Night or poor lighting conditions) |
Mounting parameters |
Data Streaming Protocol | MQTT |
Data Encoding | JSON |
Data transmission | LTE |
Operating conditions | -20° C - +50° C |
Power supply | 220 - 240 V AC | 12 / 24 V DC |
Frequency range | 47 - 63 Hz | N/A |
Power consumption | <30W | <30W |
Protection class | IP65 |
Dimensions | 205 x 150 x 90 mm (L x B x H) |
Weight | 1200 g Compute module + 2000 g Optical sensor |
Mounting method | Mast mounting, Clamping range 60 - 150 mm |
1 x BMA 12V
1 x Battery box 100Ah/12V
1 x Battery charger 12V/15A
1 x Telescopic pole
1 x Mounting bracket
2 x Tensioning straps
1 x Mast lock
1 x Reusable cable tie
4x Padlocks
3 | 5 | 20 | 4-12 |
4 | 7 | 19 | 5.4-12 |
5 | 9 | 18 | 6.6-12 |
6 | 10 | 18 | 10-12 |
7 | 12 | 18 | 11-12 |
8 | 14 | 17 | 12 |
Rev. 06/2024
For reasons of readability, the masculine form has been chosen in the text, the information refers to all genders.
BMA | BERNARD Mobility Analyser |
---|---|
The BMC links the BERNARD Mobility Analyser (BMA) and a traffic light system (TLS). The BMA, an intelligent optical system for the identification of objects, can initiate vehicle-actuated switching recommendations, such as request, dimensioning and registration. This information is transmitted to the BMC and countermeasures are taken. This information is transmitted to the BMC and countermeasures (relieving the traffic light system) can be initiated.
Please be sure to observe the safety instructions for protection against electric shock and the risk of injury. Read the operating instructions carefully before starting work
These operating instructions must be kept in the vicinity of the BMC to ensure that it is used in accordance with the applicable safety regulations at all times;
The operating instructions must be kept in a safe place! If the BMC is passed on to a third parties, they must be passed on with it.
Use the BMC only for its intended purpose.
Before commissioning, ensure that the mains voltage corresponds to the specified mains voltage.
No voltage must be applied to the device during installation.
Installation must be carried out by qualified personnel and must comply with all local regulations.
The BMC can be damaged by even a slight shock. Ensure careful handling, storage and transportation.
All information and instructions in these operating instructions have been compiled taking into account the applicable standards and regulations, the state of the art and many years of knowledge and experience.
The manufacturer accepts no liability for damage in the following cases:
Non-compliance with these instructions
Use other than the intended use
Use by insufficiently qualified personnel
Unauthorized modifications
Technical modifications
Use of unauthorized spare parts
The actual scope of delivery may deviate from the explanations and illustrations described here in the case of special versions, the use of additional ordering options or due to the latest technical changes. The obligations agreed in the contract documents, the general terms and conditions as well as the manufacturer's terms of delivery and the statutory regulations valid at the time of conclusion of the contract shall apply.
In addition to the safety instructions in these operating instructions, the safety, accident prevention and environmental protection regulations applicable to the area of use must be observed. The following applies in particular:
The operator must inform himself about the applicable health and safety regulations
The operator must clearly regulate and define the responsibilities for installation, operation, troubleshooting, maintenance and cleaning;
The operator must ensure that all persons handling the BMC have read and understood these instructions. In addition, he must train the personnel at regular intervals and inform them about the dangers
The operator is responsible for ensuring that the BMC is always in perfect technical condition.
The following therefore applies:
The operator must ensure that the maintenance intervals described in this manual are adhered to
The operator must instruct the personnel regularly. An instruction log must be created for better follow-up.
Safety instructions are identified by symbols in these operating instructions. The individual instructions are introduced by signal words that express the level of hazard.
The instructions must be followed to avoid accidents, personal injury and damage to property.
**Danger! Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.
**Warning! Indicates an imminently hazardous situation that must be avoided.
**Caution! Indicates a potentially hazardous situation which, if not avoided, may result in damage to property and the environment.
**Hint! Highlights useful tips and recommendations.
Work on the BMC may only be carried out by a qualified electrician or by instructed persons under the direction and supervision of a qualified electrician in accordance with the electrotechnical regulations.
**Caution! Unforeseeable risks of hazards may arise if the device is not used as intended, i.e. that is not described under intended use or that goes beyond the intended use.
The BMC is intended exclusively for controlling traffic light systems (individually depending on object classes, environmentally sensitive control, public transport priority) and for pedestrian flow detection (movement flows, counting, warning if limit values are exceeded). The BMC is designed for public use outdoors or in enclosed spaces.
The BMC may only be used in accordance with the specifications in the operating instructions. All instructions, safety regulations and compliance with the prescribed operating, maintenance and servicing conditions must be observed. No modifications, attachments or conversions may be made to the BMC without the manufacturer's approval.
For damage resulting from improper use
the operator bears sole responsibility.
The manufacturer accepts no liability whatsoever.
The following shows the schematic structure of an intelligent traffic light system (TLS) in conjunction with the BERNARD system. This system, consisting of power supply, BMC and BMA, is regarded as a single unit and as such fulfills the legal requirements. Up to four BMAs can be connected to one BMC. The BMAs communicate with the BMC via power line communication. The connection between the control unit of the TLS and the BMC is made via up to twelve potential-free optocoupler switching contacts, so that the BERNARD system is electrically isolated from the TLS and no electrical interference is to be expected.
The following power supply is used to supply the BMC with power: Meanwell MDR-100-24 (https://www.meanwell.com/Upload/PDF/MDR-100/MDR-100-SPEC.PDF). The power supply is supplied with the BMC. Only the use of this power supply is recommended. With a cable length > 5 m, the DC voltage must be set to 30 V using "+V Adj" to compensate for a possible voltage drop on the connecting cable between the BMC and BMA. A cable cross-section greater than 0.75 mm² is recommended for the connecting cable between the BMC and BMA.
**Caution! Damage due to incorrect transportation! Incorrect transportation can cause considerable material damage
Only open and completely remove the packaging at the actual installation site.
The BMC is packed by the manufacturer for transportation. The delivery should be checked for completeness and transport damage immediately upon receipt so that remedial action can be taken quickly if necessary.
Disposal of the packaging: Separate the packaging materials accordingly and take them to the appropriate collection points for recycling and environmental protection.
If possible, the device must be stored in a dry and dust-free place. Avoid direct UV radiation.
The installation of the BMC in combination with one or more BMAs is described below.
**Caution! Incorrect handling or inattention can lead to injuries or crushing. Installation only by a suitably trained specialist or demonstrably instructed personnel. Local safety, accident prevention and environmental protection regulations must be observed during installation.
Note! Ensure that connected cables have been connected correctly. Cables must be firmly clamped in the connection blocks. It is therefore recommended to check each cable clamp before commissioning.
De-energize the system
Snap the Power Supply onto the DIN rail. For a cable length > 5 m: Set the DC voltage to 30 V using "+V Adj".
disconnect all connection blocks from the BMC
open the BMC baselatch (orange) as shown in the illustration. Place the BMC on the DIN rail and close the baselatch again. The BMC should now be firmly seated on the DIN rail.
Establish the 24V DC connection between the power supply and the BMC connection block (see wiring diagram). Check the connections and plug the connection block into the BMC. 6.
Connect the cables to the BMA with the BMA connection block (see wiring diagram). The polarity is not relevant. Check the connections and plug the connection block into the BMC.
Connect the cables to the control unit with the connection block of the potential-free contacts (see wiring diagram). Connect as shown in the wiring diagram the common ground of the control unit to one of the two outputs of the potential-free contacts as shown in the connection diagram. Check the connections and plug the connection block into the BMC. 8. 8 [Establish a 230V AC mains connection to the power supply: Connect the protective earth conductor (PE), the neutral conductor (N) and the phase conductor (L) to the power supply as shown in the wiring diagram].(#user-content-fn-1)
**Danger! Danger due to electric current! Failure to observe the safety instructions may result in injury or death!
**Warning! Commissioning may only be carried out by appropriately trained specialist personnel. (see also chapter Personnel qualification).
Switch on the system.
The power LED on the power supply should light up
The power LED on the BMC should light up yellow for 5 seconds and then change to green. The connected BMAs are now supplied with power via the BMC.
As soon as the BMA has started up (this can take a few minutes), the BMA can be configured via the Bernard Control Center and a corresponding potential-free contact can be assigned to the region of interest zones. See #konfiguration-des-bmcs-im-bernard-control-center
If a zone is configured, the corresponding BMC switch LED should light up when the zone is assigned.
For further steps on operating the BERNARD Control Center, please refer to the "BERNARD Control Center" operating instructions.
The RGB LEDs of the BMC show the following functions:
Power LED:
Off: BMC switched off. Yellow: BMC starts (5 seconds). Green: BMC in operation.
Sensor LEDs:
Flashing green: Heartbeat received from corresponding BMA (4 second interval).
White: BMA watchdog active.
Switch LEDs:
Off: Contact open. ** Green: Contact closed.
The system is configured via the BERNARD Control Center
Select the corresponding BMA in the Control Center. As shown in the illustration, check the box for "IO-device" under "Event Connection - Configuration mode".
Below the MQTT configuration, an "IO device" field appears in which the BMC can be selected under "Family".
Then save the changes using the "Save" button at the bottom of the page. As soon as the changes have been saved, the zones can be assigned to the contacts under "Configure Model & Event Triggers" (bottom left in the camera image).
First add the desired "Region of Interest" zones under "Traffic Events"
Once the zones have been configured, save your changes using "Save changes". The configuration could then look like this, for example:
To configure the corresponding potential-free contacts, click on "New Rule" under "Custom Rules" and configure the corresponding rules for when the contact should be switched, as shown in the following graphic, for example:
In this configuration, the potential-free contact 5 of the BMC would be closed as long as an object (vehicle/person) is located in the "roizone05" zone. More complex conditions can also be configured, e.g. that the contact should only be switched for certain vehicle classes in order to prioritize a bus, for example. Save the rule using the "Save" button. Add the rules for other zones. In the overview of event triggers, a "Rule" marker should then be added in red under "Type" (see illustration below).
As shown in the following image, the value must also be set to zero under "Global Settings" - "RoI time interval (seconds)".
Note! If the "RoI time interval" is set to 0, no ROI zones should be configured without a corresponding rule, as otherwise the corresponding ROI is evaluated every millisecond and consequently generates a large number of MQTT events.
Finally save the changes with "Save Changes" -> "Save & Deploy". In this way, the configuration changes are synchronized to the device. It may then take some time (up to 1 minute) until the changes are active on the device. Now, the contacts are switched according to the configured rules.
In the interest of constant operational readiness, a visual inspection of the BMC and the BMA and cleaning of the acrylic dome of the BMA should be carried out at least once a year by a suitably trained specialist or demonstrably instructed personnel. (see #personalqualifikation) be carried out. Software updates are carried out by the manufacturer with the customer's consent.
**Caution! The use of rough cleaning cloths can damage the acrylic element and thus impair its function.
Only clean dust and grease on the acrylic with a soft cloth and a little cleaning alcohol. If the device has been stored for a long time, you can use a dry cloth to remove the dust residue on the housing.
If the system malfunctions, the following points should be checked one after the other.
**Danger! Electrical current: Ensure that the power supply is switched off or disconnected. Failure to do so may result in serious injury or death.
**Warning! Decommissioning only by authorized and competent persons.
**Warning! Incorrect handling or inattention can lead to injuries or crushing.
To decommission the BMC, disconnect the system from the power supply. Remove all terminal plugs from the BMC. Open the base latch and dismount the BMC. The cables can then be removed from the terminal plugs.
At the end of its service life, the BMC must be disposed of properly. The local disposal regulations apply to the disposal of all device parts and packaging materials.
Do not dispose of the BMC in the residual waste. In accordance with European Directive 2002/96/EC on waste electrical and electronic equipment and its transposition into national law, used electrical and electronic equipment must be collected separately and recycled in an environmentally friendly manner.
No personal data is read or processed in the BMC. This means that the use of the BMC is harmless under data protection law.
The BMC complies with the Electromagnetic Compatibility Directive 2014/30/EU. This results in the CE certification affixed to the underside of the device.
The BERNARD Gruppe is committed to producing its products in a sustainable and environmentally friendly manner. The BMC complies with the RoHS Directive 2011/65/EU.
It is not permitted to modify the BMC in any way. Any modifications will invalidate the manufacturer's service and liability with immediate effect.
Rev. 06/2024
The supplier assumes no liability for compliance with local requirements or additional certifications that may be required in certain regions or markets. It is the responsibility of the purchaser or user to ensure that the product complies with local regulations and specific requirements that may go beyond the specified certifications. The supplier disclaims all liability for any damage or loss that may result from non-compliance with such additional requirements.
Rev. 09/2024
B101 | B401 |
---|
The B101/B401 processe personal data only vaguely, without storing it and only for the purpose of anonymization. This is done on the basis of Art. 6 para. 1 f) GDPR, namely in the legitimate interest of the operator. Only the anonymous data is then used to carry out traffic management. The BMA complies with the Low Voltage Directive 2014/35/EU and the Electromagnetic Compatibility Directive 2014/30/EU. This resulting CE certification is attached to the bottom of the device.
The supplier assumes no liability for compliance with local requirements or additional certifications that may be required in certain regions or markets. It is the responsibility of the purchaser or user to ensure that the product complies with local regulations and specific requirements that may go beyond the specified certifications. The supplier disclaims all liability for any damage or loss that may result from non-compliance with such additional requirements.
Rev. 09/2024
DC power supply unit with 12 to 48 V output voltage and at least 20 W (B101) or 60 W (B401) output power.
If other devices are connected to the power supply unit, the output power of the power supply unit must correspond to the required total peak power of all connected devices.
Ethernet network connection (at least 100 Mbit/s) with DHCP server and Internet access (at least 1 Mbit/s down/up). IPv4 - a private IPv4 address is sufficient.
Network camera(s) with RTSP (H.264) stream (at least 720p @ 25FPS). Camera(s) accessible via the network.
Cable with 2.5 / 5.5 mm DC plug (included).
RJ45 network cable (CAT 6)
Unplug the power supply.
Attach the device to the mounting surface or DIN-rail.
Plug the network cable into the Gigabit Ethernet port of the device and connect the cable to the network switch / router.
Connect the DC power-cable to the power supply and insert the DC-jack into the DC power (12-48V) connection on the device.
Switch on the power supply to start the device.
Firewall setting: In order for the device to communicate with the Control Center, the following ports must be open for outgoing connections:
Static IP: Should the device be assigned a static IP address in the network (optional):
Configure the static IP address in the IP/MAC binding of the router/DHCP server. The MAC address of the device can be found on the sticker on the underside of the device or in the data sheet supplied.
It may be necessary to restart the device after changing the network settings by briefly disconnecting it from the power supply.
As soon as the device is supplied with power and the network settings are configured correctly, the device should be displayed as online in the Control Center.
Select the corresponding device and add a new camera stream via “Add camera”:
The next step is to configure the camera stream. To do this, select “RTSP” from the drop-down menu under “Camera Connection - Connection type” and fill in the parameters for the camera stream.
Depending on which data interface is required, the corresponding data interface can then be selected on the right-hand side under “MQTT Connection - Configuration mode”. If the events are to be sent directly to a self-hosted MQTT broker, “Custom MQTT connection” must be selected. The parameters of the MQTT broker can then be configured in the “Custom MQTT” field.
Use cases for traffic scenarios
How to successfully perform traffic counts on specific urban roads and highways, including the classification of objects according to our (sub)classes. You want to know the traffic situation of an urban road or highway? Our software is the solution to record the number of all objects, broken down by object type (class) and direction.
For this use case, our software provides you with all the information you need for traffic counting. The counts of the vehicles including their classification can be recorded. The counts are divided into two directions (in/out). Furthermore, several counts can be carried out in one camera, e.g. the separate counting of each lane. In addition, it is possible to add a second counting line, calibrate the distance between them and estimate the speed of vehicles passing both lines. are recognized by our software.
In the table below you will find detailed information on the requirements, settings and positioning of the camera.
Setting | Recommended |
---|
Do you want to know the traffic flow at intersections and traffic circles? The Swarm Perception Platform provides the solution to capture the number of vehicles traveling from an origin zone (origin) to a destination zone (destination), broken down by vehicle type (class).
For this use case, our software provides you with all the necessary data for source-destination traffic analyses - the number of vehicles from one zone to another, including classification according to the standards TLS (technical delivery conditions for route stations) issued by the German Highway Research Institute (BASt).
In the table below you will find detailed information on the requirements, settings and positioning of the camera.
Setting | Recommended |
---|
Tip: Use the or .
Sensor mounting - horizontal angle to the object
EU licence plate standard format ()
Note: Two-line/square licence plates are not supported.
Distance: 5 - 20 m Height: 3 - 8 m Horizontal angle 0° - 20°
Life phase | Qualification |
---|---|
Fault | Possible cause | Remedy |
---|---|---|
Port | Protocol | Richtung |
---|
For the configuration of the event triggers and other settings, see .
Problem | Possible cause | Solution |
---|
BMC
BERNARD Mobility Controller
TLS
Traffic light system
OUT
Output-side switched contacts
PLC
Power line communication
Mounting
Basic technical training of instructed personnel
Commissioning
Specialized electrical engineering training
Maintenance
Basic technical training of instructed personnel
Commissioning
Specialized electrical engineering training
Disassembly
Basic technical training
Instructed personnel
**Power supply LED does not light up **
Defective or interrupted supply line.
Check the electrical supply line.
Power supply is defective.
Replace the power supply. Contact the support team.
BMC power LED does not light up
Defective or interrupted supply line.
Check the electrical supply line.
BMC is defective.
Please contact support for this.
**Sensor LED of the connected BMA does not flash green every 4 seconds (no heartbeat is received from the BMA) **
Defective or interrupted supply line to the BMA.
Check the electrical supply line. If the BMA itself is in operation ("Online" connection in the Control Center), the supply line is not the problem.
The supply cable to the BMA is too long.
The voltage drop on the supply cable is too great, so that the BMA is not reliably supplied with power. Use a shorter supply cable or a cable with a larger cross-section.
BMA is still in the start-up process or is performing an update.
Check again after 10 minutes.
BMA not correctly configured.
Communication between BMA and BMC is disrupted, e.g. by electromagnetic interference from parallel lines.
Contact the support team. Use of shielded twisted pair cables.
Status LED of the potential-free contact does not light up although the vehicle is in the zone.
BMA not correctly configured.
Status LED of the potential-free contact lights up, but control unit does not register switching operation
Defective or interrupted cable. Incorrect assignment in the control unit.
Check the electrical cable. Check the assignment in the control unit.
Technical data |
Function | Interface between BMA and control unit of the traffic light system. Power supply of the connected BMA. |
Number of BMAs | 1 - 4 |
Outputs | 12 potential-free (galvanically isolated) switches with screw connection. Imax = 700 mA, Umax = 60 VDC |
Diagnostic outputs | Freely configurable, up to 4 potential-free (galvanically isolated) switches with screw connection. Imax = 700 mA, Umax = 60 VDC |
Mounting | DIN rail |
Connection cable BMA | 2 cores, cable cross-section ≥ 0.75 mm² (AWG18), connection length up to 120 m at 30 V input voltage |
Connection parameters |
Input voltage | 24 - 30 VDC |
Power consumption | ≤ 2 W for BMC plus ≤ 25 W per connected BMA |
Environmental requirements |
Temperature range | -20 °C to +60 °C |
Humidity | ≤ 95 % (at 25 °C) |
Safety requirements |
CE tested according to | EMC 2014/30/EU Road traffic signal systems - Electromagnetic compatibility EN 50293 |
Conducted interference emission and interference radiation | Compliant with EN55032 (CISPR32) Class B |
Dimensions |
height x width x depth | 60 x 107(214) x 90 mm |
Weight | < 1 kg |
80 | IPv4 - TCP/UDP | Outgoing |
123 | IPv4 - UDP | Outgoing |
443 | IPv4 - TCP/UDP | Outgoing |
1194 | IPv4 - UDP | Outgoing |
8883 | IPv4 - TCP | Outgoing |
5671 | IPv4 - TCP | Outgoing |
Device is offline in the Control Center | Power supply outside the specification. Voltage: 12 - 48V Power: 20W (B101), 60W (B401) More power is required if other devices are connected to the same power supply! | Use of a suitable power supply. |
Incorrect network configuration. | Clarification with network administrator. |
Incorrect Firewall settings. see above. | Clarification with network administrator. |
No internet connection over the network | Device has to be connected to a network with internet connectivity. |
Device crashes frequently / is displayed as offline in the Control Center. | Power supply outside the specification. Voltage: 12 - 48V Power: 20W (B101), 60W (B401) More power is required if other devices are connected to the same power supply! | Use of a suitable power supply. |
No data in Data Center | Network port of the MQTT service not enabled. | Activation of port 8883 by the network administrator. |
No data received via custom MQTT broker | Network port of the MQTT service not enabled. | Activation of the used port by the network administrator. |
Object speed | < 130 km/h |
Day/Night/Lighting | During the day/well lit/night vision |
Indoor/outdoor use | Exterior |
Expected accuracy (counting + classification if all environmental, hardware and camera requirements are met) | Counting >95 % (vehicles, bicycles) Classification of main classes: >95 % Classification of sub classes: >85 % |
Supported products | BMA, mobil BMA,B101, B401 |
Frames Per Second (fps) | 25 |
Supported products | BMA, mobile BMA, B101, B401 |
Frames Per Second (fps) | 25 |
Camera streams |
Number of streams | 1 | 4 |
Stream | 720p @ 25 FPS | 720p @ 25 FPS |
Stream protocol & codec | RTSP (H.264) | RTSP (H.264) |
Data output |
Message protocol | MQTT | MQTT |
Data format | JSON | JSON |
Data interface |
Power supply |
Connector | 2,5 / 5,5 mm DC-Jack | 2,5 / 5,5 mm DC-Jack |
Input voltage | 12 - 48 V | 12 - 48 V |
Power consumption | 20 W | 60W |
Recommended power supply | Mean Well MDR-60-12 | Mean Well MDR-60-12 |
Network |
Connectivity | Gigabit Ethernet | Gigabit Ethernet |
Network configuration | DHCP | DHCP |
Mechanical |
Dimensions | 125 x 125 x 42 mm | 183 x 125 x 42 mm |
Weight | 0,6 kg | 0,8 kg |
Mounting | Surface mounting, DIN rail (optional) | Surface mounting, DIN rail (optional) |
Environmental conditions |
Operating temperature | 0°C to 50°C | 0°C to 50°C |
Operating humidity | ≤ 95 % (at 25 °C) | ≤ 95 % (at 25 °C) |
Pixels Per Meter is a unit of measurement used to define the amount of potential image detail a camera provides at a given distance. | >30 PPM (object classes car, truck) <60 PPM (object classes person, bicycle, motorbike) |
Video resolution | 1280 × 720 Pixel |
Video protocol/codec | RTSP/H264 |
Focal length | 2.8 mm - 12 mm |
Camera mounting - distance to object center | Object classes car, truck: 5-30 m (2.8 mm Focal length) 35-100 m (12 mm Focal length) Object classes person, bicycle, scooter: 3-12 m (2.8 mm Focal length) 25-50 m (12 mm Focal length) |
Camera mounting - mounting height | Up to 10 m Note: Mounting higher can help to minimize obstruction by large objects. |
Camera mounting - vertical angle to the object | <50 ° Note: The correct vertical angle to the object should be achieved by setting the correct distance to the vehicle and the optimum mounting height. |
0 ° - 90 ° Note: An angle of approx. 15 ° provides better results for classification, as more object details are visible (e.g. wheels, axles, etc.) |
Pixels Per Meter is a unit of measurement used to define the amount of potential image detail a camera provides at a given distance. | >30 PPM for object classes car, truck >60 PPM for object classes person, bicycle, motorbike |
Video resolution | 1280 × 720 Pixel |
Video log/Codec | RTSP/H264 |
Focal length | 2.8 mm - 12 mm |
Camera mounting - distance to object center | Object classes car, truck 5-30 m (2.8 mm focal length) 35-100 m (12 mm focal length) Object classes person, bicycle, scooter 3-12 m (2.8 mm focal length) 25-50 m (12 mm focal length) |
Camera mounting - mounting height | Up to 10 m Note: Mounting higher can help to minimize obstruction by large objects. |
Camera mounting - vertical angle to the object | <50 ° Note: The correct vertical angle to the object should be achieved by setting the correct distance to the vehicle and the optimum mounting height. |
0 ° - 360 ° |
Object speed | <50 km/h |
Day/Night/Lighting | During the day/well lit/night vision |
Indoor/outdoor use | Outdoor |
Expected accuracy (from origin to destination when all environmental, hardware and camera requirements are met) | origin-destination counts and classification main classes: >85 % (for vehicles) Classification main classes: >95 % classification sub classes: >85 % |
Use cases for traffic scenarios
There are the following main use cases of our technology to better understand the traffic situation in the city, on urban roads and on highways
Record the occupancy status of different parking lots in real time
For this use case, our software provides you with all the relevant information for single-user and multi-user detection. Our solution provides you with the occupancy status for each of your configured parking spaces.
The single space detection provides you with information about the occupancy of your parking space as well as information about the vehicle class in your parking space. Please note, however, that the configuration below is optimized for the detection of vehicles and is not designed for the detection of people or bicycles. In addition, the accuracy of the classification depends on the camera setup, so the classification will be less accurate when viewed from above.
**Good camera positioning and understanding the following section is crucial for accurate detection.
The biggest challenge in planning the camera setup is to avoid possible occlusion by other vehicles. We recommend using the Axis Lens Calculator or a Generic Lens Calculator and thoroughly testing your parking lot configuration under the following conditions:
Park a car in one of the parking lots
Park a larger vehicle (tall van, small truck, etc.) next to it
If you can still detect at least 70% of the first parked vehicle, the system will recognize it.
The parking spaces must be fully visible (within the camera's field of view). We do not guarantee full accuracy for cut off parking spaces.
Fully visible parking spaces
Avoid pitches being obscured by objects (trees, posts, flags, walls, other vehicles, etc.). Also avoid camera positions where vehicles (especially tall vehicles such as vans) occlude other vehicles.
Avoid occlusions by other objects
Occlusions** caused by other parked cars mainly occur when the parking spaces and the camera orientation are in the same direction.
Avoid occlusions by other vehicles
In the table below you will find detailed information on the requirements, settings and positioning of the camera.
How to successfully set up a parking lot scenario to get reliable utilization data.
Do you have a parking lot where you simply want to know the occupancy rate by counting entries and exits? Our technology offers the perfect solution to achieve this in a simple way. See for yourself:
For this use case, our software provides you with all the relevant information for your count based on entries and exits. It records the number of vehicles in your parking lot as well as the number of vehicles entering and leaving your parking lot. The whole thing can be configured for user-defined time periods.
The vehicles are recognized based on our defined classes. Please note that the following configuration is optimized for the detection of vehicles and not for people and bicycles.
In the table below you will find detailed information on the requirements, settings and positioning of the camera.
Setting | Recommended |
---|---|
The Control Center is where you configure your purchased BERNARD hardware products
Under the Devices menu item in the Control Center, you can centrally manage all your BERNARD devices and configure the cameras so that they generate data according to your requirements for your use cases.
Below you will find a description of the different parts of the device configuration:
Number | Description |
---|---|
BMA/BMC to control traffic light signaling.
Our BMA with the associated features enables you to communicate with traffic signal systems via relays (potential-free contacts) in combination with the BMC . The following applications can be covered in this way:
"Smart Prio System": Prioritization of certain traffic classes and ensuring smooth traffic behavior in real time (e.g. environmentally sensitive control, public transport registration, such as pedestrians, cyclists, e-scooters through to heavy traffic)
Simplify infrastructure maintenance: Replace multiple induction loops with a single BMA BMC. The installation does not require any excavation work and significantly reduces maintenance costs.
In the table below you will find detailed information on the requirements, settings and positioning of the camera
Setting | Recommended |
---|---|
Here you will find information on how to successfully connect and configure the camera.
To call up the configuration page of the Perception Box, simply click on the respective box in the list view. This allows you to manage all cameras running on this device.
You are of course completely free to name your BERNARD devices as you wish; we recommend a logical naming scheme at this point.
Click on one of the displayed cameras to open the Settings of the respective camera. You can name the camera there. At the top, you have the option of deactivating the camera stream. If a camera stream is deactivated, it is no longer taken into account by the software. The configuration is retained.
As soon as you have configured the camera connection (Camera Connection), you will see a preview of the camera image. You can now continue with the scenario configuration.
Now that you see your camera images, it's time for the Configuration. This is where the magic happens!
Since our software is mainly intended and used for specific use cases, you will find all the information you need for the perfect setup in the respective sections for your use case:
In the configuration, you can select the model suitable for your use case and configure any combination of event triggers and additional functions.
The model reflects the engine with which the BERNARD devices work.
Below you will find a brief description of each model. To decide which one you want or should use for your application, please read the section on the respective use case:
This model detects vehicles, people on two-wheelers and people in highly dynamic scenes (e.g. road traffic or highways, i.e. scenes in which objects move quickly).
This model detects vehicles, people on two-wheelers and people in low dynamic scenes in parking lots when a fisheye camera is used. This does not work for fast, dynamic traffic scenes.
This model detects a person, or the entire body of a person. This makes it ideal for detecting, tracking and counting people when they are further away (>5 m) from the camera.
This model detects a person's head and is therefore ideal for detecting, tracking and counting people when they are closer (<6 m) to the camera.
Each event trigger generates a unique ID in the background. You can assign user-defined names so that you can keep track of all configured triggers. This name is then used to display the corresponding data in the corresponding data evaluation tool.
Below you will find explanations of the individual event types and triggers:
We provide various templates for the three different use cases to make configuration and general use as easy as possible for you.
Parking events: Templates for all use cases in the area of parking space monitoring
Traffic events: Templates for use in the area of traffic monitoring and traffic safety
People events: These templates are perfect for use with our People Full Body or People Head models
The description of the available event triggers and the individually customizable event settings can be found in the following table:
**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 In and Out. You can switch In and Out at any time to adjust the direction accordingly. 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 the option to activate events for repeated CL crossings. The only restriction here is 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.
Regions of Interest** count objects in a specific area.** In addition, the class (Class) and dwell time (Dwell Time) are determined and specified.
Depending on the scenario, we can distinguish between three types of RoI. We offer the templates described below for these three types:
These zones are used for origin-destination analyses. Counts are generated when an object moves through OD1 and then OD2. At least two areas must be configured for an OD.
The first zone that the object passes through is called the origin zone (Origin). The last zone that the object passes is therefore referred to as the destination zone (Destination).
This section describes which status devices and camera streams can have and and what to expect in each case.
In the Control Center, you will find a basic monitoring status at both camera and device level. This status indicates whether your cameras are operational or whether action is required to get them running.
In the camera overview of your devices and dashboards, you will find the camera monitoring, which shows you whether your camera is working as expected. In the device configuration, you will find the device monitoring, which shows the worst status of all cameras running on the device. This allows you to see directly if something is wrong.
You can find out how to configure automatic e-mail notifications for status changes in
Status | Description |
---|
If, contrary to your expectations, your device is displayed as offline, please contact our
Device monitoring depends on the overall worst status to give you a good overview directly in your device list if a camera is not working as expected.
Status | Description |
---|
This status takes into account the system, the camera input and the MQTT connection.
The condition of your devices at a glance
The device health metrics allow you to provide evidence of reliable and continuous data collection and diagnose potential problems yourself (e.g. regarding a stable network connection, power supply, etc.). The following metrics are supported:
Device uptime, status, reboots, available memory space
Device temperature (supported for BMA/P101/OP101/Jetson Nano)
LTE modem traffic, signal strength and reconnects (supported for BMA/OP100/OP101)
Camera status and processing speed of the camera (FPS)
Created and pending events
MQTT, ,
MQTT, ,
Using the camera parameters defined below ensures that the minimum required PPM value is achieved. Tip: Use the or a .
Camera mounting - horizontal angle to the object
Using the camera parameters defined below ensures that the minimum required PPM value is achieved. Tip: Use the or a .
Camera mounting - horizontal angle to the object
Setting | Recommended |
---|---|
This model detects vehicles, people on two-wheelers and people in scenes with low dynamics, for example parking lots where objects are not moving or are moving slowly. Since this model analyzes the video at a higher resolution, it can detect objects that are further away from the camera. This requires more computing power and is therefore currently only recommended for
When recognizing and tackling people, we never perform facial recognition. No sensitive personal information of any kind is processed. at any time if you have any questions about personal data or data protection.
Single Space Parking | Multi Space Parking | Generic |
---|
Your devices send the results of the real-time analysis to an MQTT broker. The default configuration sends data to the Azure Cloud and to Data Analytics so that it can be retrieved there. If you would like to set up a custom MQTT, please contact our
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 .
Status | Description |
---|
Object speed
0 km/h
Day/Night/Lighting
During the day
At night (provided the surroundings are well lit or night vision mode is activated)
Indoor/outdoor use
both
Expected accuracy
(if all environmental, hardware and camera requirements are met)
> 95 % Excluding classification
Supported products
BMA, B101, B401
Frames Per Second (fps)
>5
Object speed
<30 km/h
Day/Night/Lighting
During the day/well lit
Indoor/outdoor use
both
Expected accuracy (counts when all environmental, hardware and camera requirements are met)
>95 % Only vehicles are considered for this accuracy. For parking lots, people and two-wheelers are not included in our test scenarios as they do not occupy parking spaces (for vehicles).
Supported Products
BMA, mobile BMA, BCA, B101, B401
Frames Per Second (fps)
>12
Supported products
BMA BMC
Frames Per Second (fps)
12
Event- Trigger | Duration (Time) | Duration (Time) | Duration (Time) or Status (Occupancy) |
Event- Type | Parking | Parking | People and Traffic |
Number of preset Objects | 1 | 5 | 1 |
Color | dark green | purple | light green |
Overview of your licenses.
The license management area gives you an overview of your software licenses. This means in detail:
The number of licenses currently in use: Number of activated camera streams. Deactivated streams are not counted.
The total number of licenses purchased:** In general, all basic licenses can be used with any hardware belonging to you. The respective status of the individual licenses
Active: The license is currently valid and the expiration date is in the future.
Expired: The license is no longer valid and has therefore expired. Either the license has already been renewed or you have decided to let it expire.
Inactive: The license period begins on a future date. The start and end date of the respective license validity The order and invoice number and the number of streams included
Adding or activating further streams is only possible if sufficient PLC licenses are available. Unused streams can be deactivated at any time
Pixels Per Meter is a unit of measurement used to define the amount of potential image detail a camera provides at a given distance.
>60 PPM
Using the camera parameters defined below ensures that the minimum required PPM value is achieved. Tip: Use the lens calculator from Axis or a generic lens calculator.
Video resolution
1280 × 720 Pixel
Video protocol/Codec
RTSP/H264
Focal length
2.8 mm - 4 mm
Camera mounting - Distance to object center
5-30 m, Vehicles should be as central/centered as possible in the image.
At a distance of 5 m from the camera, we can guarantee high accuracy for three parking spaces that are aligned orthogonally to the camera. In general, the further the distance to the camera, the greater the overview of the parking spaces.
Camera mounting - mounting height
Inside: 2.5 - 5 m Outside: 2.5 - 10 m Higher is better: Vehicles can obscure parked cars, so we recommend the highest possible mounting points.
Pixels Per Meter is a unit of measurement used to define the amount of potential image detail a camera provides at a given distance.
>60 PPM
Using the camera parameters defined below ensures that the minimum required PPM value is achieved. Tip: Use the lens calculator from Axis or a generic lens calculator.
Video resolution
1280 × 720 Pixel
Video protocol/Codec
RTSP/H264
Focal length
2.8 mm
Camera mounting - Distance to object center
5-20 m
Camera mounting - Mounting height
3-6 m
Camera mounting - Vertical angle to the object
<50 °
Note: The correct vertical angle to the object should be achieved by setting the correct distance to the vehicle and the optimum mounting height.
0 ° - 90 °
Pixels Per Meter is a unit of measurement used to define the amount of potential image detail a camera provides at a given distance.
>30 PPM (Object classes car, truck)
>60 PPM (object classes person, bicycle, motorbike)
Using the camera parameters defined below ensures that the minimum required PPM value is achieved. Tip: Use the lens calculator from Axis or a generic lens calculator.
Video resolution
1280 × 720 Pixel
Video protocol/Codec
RTSP/H264
Focal length
2.8 mm - 12 mm
Camera mounting - distance to object center
Object classes car, truck:
5-30 m (2.8 mm Focal length)
35-100 m (12 mm Focal length)
Object classes person, bicycle, scooter:
3-12 m (2.8 mm Focal length) 25-50 m (12 mm Focal length)
Camera mounting - mounting height
Up to 10 m
Note: Mounting higher can help to minimize obstruction by large objects.
Camera mounting - vertical angle to the object
<50°
Note: The correct vertical angle to the object should be achieved by setting the correct distance to the vehicle and the optimum mounting height.
0° - 90° Note: An angle of approx. 15° provides better results for classification, as more object details are visible (e.g. wheels, axles, etc.)
Object speed
< 40 km/h
Day/Night/Lighting
During the day/well lit/night vision
Indoor/outdoor use
Outdoor application
Expected accuracy(detection + classification, if all environmental, hardware and camera requirements are met)
detection > 95 % Classification of main classes: > 95 % Classification of sub classes: > 85 %
The device is ready for operation and connected to power and the Internet. |
The device is offline (no power, no internet, etc.). There are several simple steps you can check before contacting our support team. |
Everything is fine - all cameras configured on your device are working as they should. |
At least one camera on the device is not configured. Check the status in the camera monitoring for more details. |
At least one camera is not sending data as expected. |
At least one camera on the device has the status Warning. |
The device is offline. Check that the hardware is connected to the power supply and that there is a network connection. |
If you have just changed the configuration of one of the cameras, this status is displayed for a maximum of five minutes before the status is determined again. |
At least one camera is deactivated. |
Everything is fine and your camera is running as expected. The software is also running smoothly, the camera connection is available and the MQTT broker is connected. |
The camera is not configured. You must configure the camera and data connection as well as your respective configuration according to your use case. |
Data is still being generated and delivered, but there are problems that could affect the accuracy of the data. Problem types: a) Video images cannot be retrieved correctly; at least 10% of the images are incorrect b) Performance issues: The number of fps is below the minimum limit of the configured event types |
The Swarm Perception Box or your hardware is offline. Check the power supply and network connection. |
If you have recently adjusted the configuration, the status is set to Pending for about five minutes until the correct status is determined. |
The stream is deactivated and can only be reactivated if sufficient licenses are available. This status can also be used to save a configuration for a later point in time without the device currently being required. |
Information on the API for retrieving specific data from the Control Center
You can easily retrieve all settings and information available in the Control Center via an API. Below you will find the Swagger documentation. Here is an example: BMA Control Center
In general, we stick to the OAuth 2.0 Client Credentials Flow (Microsoft) documented here.
Make sure to include your Tenant ID as a header in the authentication flow.
To get the first part of the URL for your specific API documentation or Swagger UI, you can either contact our Support or retrieve it from the source code of your Control Center.
In our example, the URL is:
call the Swagger UI
the API call gives you information about the device status as follows
the different statuses of the devices are defined as follows in the API documentation
you can also retrieve the status of the individual streams. The API provides the following results
Switch between devices, Data Analytics and administration
Device Name/ID of your hardware. You can customize the device name as you wish. The ID is used for communication between the edge device and Azure Cloud.
Metadata Organize your devices and create events with predefined metadata. You can define up to five key and value pairs for a device. The keys and values can be freely defined, we support the automatic completion of keys to avoid annoying typing errors. After defining metadata, you can filter the list of devices by metadata values, and the generated events contain the predefined metadata for further processing by your application. Details can be found in the event schema.
This connection status (Connection) indicates whether a connection has been established between your hardware and the Management Hub (Azure). Available statuses are Online, Offline or Unknown. If a device is unexpectedly offline, please contact our support.
The Status column provides information on whether the software is running on the respective device. Please refer to the section Camera and device control.
Auto refresh: This option allows you to automatically refresh the page as soon as changes are made or a status changes.
Administration of your Control Center
This section helps you to set up monitoring alerts so that you are notified be notified by e-mail in case of problems.
You can create automatic e-mail notifications so that you are immediately informed of possible problems with your BMAs. These user-defined alerts are created and managed in the Monitoring Alerts section of the Control Center.
Choose from multiple templates, assign the appropriate device, define recipients and receive instant email notifications when a device changes status from Running to no longer operational.
Note: Only admin can set up and manage these alerts. For the user and viewer roles, the Monitoring Alerts section in the Control Center is not visible
Let's start by creating alerts. This is done in three steps:
The conditions are based on the connection status and status of the stream. The three predefined conditions for alerts are explained in the table below:
Condition | Description | Last status | New status |
---|---|---|---|
At least one condition must be selected for the alert. It is also possible to select several conditions. An alert is sent as soon as one of several conditions is fulfilled or occurs. It is also possible to be informed as soon as the error no longer exists, i.e. the corresponding condition is no longer fulfilled:
In the second step, the devices for which the automatic alerts are to apply must be selected. To the left of Device Name/ID, all devices on this page of the list can be selected with one click. If there are several pages, this step must be repeated on each page. To find specific devices or IDs quickly, there is a search function at the top right:
In the third and final step when creating an alert, all recipients must be specified. An email address can be added by clicking on Add. There is no limit to the number of recipients.
It is not necessary for these people to have access to the Control Center for the e-mail notification - any e-mail address can be entered here. You can therefore also select group e-mail addresses for your teams.
A table with all configured alerts is displayed in the Monitoring Alerts section. In the Action column, the respective alert can be edited by clicking on the pencil icon or deleted by clicking on the trash can icon.
The editing process is identical to the creation process that we have already described here.
Bring your devices up to date
You decide when your devices receive an update. Of course, we recommend updating as soon as possible so that you can use the latest functions and benefit from quality improvements (e.g. model updates), bug fixes and security updates.
You have the option of updating individual devices or scheduling updates at specific times;
This makes it possible to carry out the update during less busy hours or during previously announced maintenance windows
Please note that it is not possible to postpone once scheduled updates to a later date
Manage user profiles with access to your Control Center.
This area provides an overview of all users who have access to your Control Center, as well as the ability to add, remove or edit users and user roles.
To add a new user profile, simply click on New User and fill in all the required fields. The new user must set a personal password by verifying the email address via the Forgot your password workflow on the login page.
Only the role or access rights can be changed. If you want to change the names or email addresses of users, you must delete this user profile and then create a new one.
Viewer: This is a read-only authorization for Data Analytics. It enables access to existing scenarios and dashboards. ** User: Can access device configuration as well as data analytics as well as reconfigure devices, create dashboards and create scenarios. Admin: Has the same access rights as User and can also access the administration area.
Download for our Data Center API
The BERNARD Data Center API provides comprehensive options for querying traffic data and moving traffic. This API allows developers to easily access metadata, collect traffic data and retrieve aggregated statistics.
Authentication with a Bearer Token is required to access the API. Please add a Bearer Token to your request header to authenticate yourself.
For detailed information on the parameters and return values of the individual endpoints, please read the corresponding API documentation.
If you have any questions or problems, please contact our
Configuration of the traffic intersections for data preparation
Once the BMA is successfully mounted and configured as described in the "BERNARD Mobility Analyser" operating instructions, open the web browser and enter the following address:
You can log in to the website with your client login. If you have problems logging in or have forgotten your password, client service can help you. Once you have successfully logged in, the user interface shown in Figure 1 will appear.
To create a survey, first open the highlighted "Configuration" tab at the top right of the menu bar.
Next, select the desired tenant to continue with the configuration. The tenant can be used to group measurement series. If you require more than one tenant, please contact customer service. After selecting the tenant, a list opens with the surveys already created.
You have the option of filtering your surveys by date or text content. It is therefore advisable to select the name of the survey so that it can be easily found later and, if necessary, different groupings are possible using the text filter (e.g. location/project number).
A new survey can be created using the "Add element" function. A new field is created in which the name of the survey must be defined. Save the process with the blue button with the memory card symbol.\
To edit a created survey, select the corresponding survey by clicking on it. A user interface then opens below the list of created surveys (see Figure 4). The selected survey can be configured using the highlighted "Edit" button.
A window opens with the key data - name, start date, end date, location of the survey, time zone and types of road users (object classes) (see Figure 5). This key data can be defined step by step. The definition of the key data can be found in Table 1.
Table 1: Definition of the key data of a survey in the BERNARD Data Center.
After successfully configuring the key data of the survey, save this process with the save button at the bottom right (see Figure 5).
The next step is to assign the BMAs used to the survey. To do this, open the selection window (see Figure 7) by clicking on "Add/edit cameras" (see Figure 6).\
This is where you add all the BMAs that you use or have used for this survey. If you have several BMAs in use, you can filter by the name of the BMA, for example, to make it easier to find the BMA you are looking for in the selection field
Once you have selected your BMA, click on "Add selected camera" and it will appear in the "Used devices" table (see Figure 7). If you do not wish to add any further BMAs for the configuration of this survey, save the selection by clicking OK.
In this step, the arms of the intersection are defined. To do this, click on the highlighted "Edit routes" button at the bottom right of the main interface in the "Configuration of the survey" area (see Figure 8).
The window for editing the routes then opens, in which the routes are named and the corresponding orientations are defined.
The routes of the intersection are defined by name (see [6] in Figure 9), angle (see [7] in Figure 9) and directional traffic type (see [8] in Figure 9). By confirming the "Show angle help" checkbox, an angle help can be added to the map section as shown in Figure 9. The definition of the key data of the route (name [6], angle [7], direction [8] and crossing [9]) are listed in Table 2.
The selection "Route has crossing" can be made to include pedestrian crossings in the Excel evaluation. This is only possible if the crossing is defined by a counting line in the Control Center. When selecting this option, an additional field opens which must be filled in. The corresponding counting line used for counting the pedestrian crossings must be entered in this field. In the first line, enter the corresponding crossing using the corresponding UUID from the Control Center. In the second line, you can name the crossing as you wish. Then select which direction (In, Out) points clockwise or counterclockwise.
Table 2: Key data of a route
Once you have filled in the fields as shown in Figure 9 according to the definitions in
Table 2, click "Add new route" to confirm the entry. Repeat the steps for defining the intersection for all routes at the intersection that you want to evaluate in the data center. As soon as all routes are listed, confirm your entry with "OK". (see Figure 11).
For each route, automatic origin destination flows are generated defined by their relations to all other routes (turning traffic, straight ahead traffic) and to the route itself (U-turn).
In the last step of the configuration, you must define the origin destination flows and assign the corresponding zone/line IDs from the configuration in the Control Center to the origin destination flows.
Define the origin destinations flow by selecting your route and clicking on the highlighted "Edit selected turning movement" button (see Figure 12) so that the user interface opens as shown in Figure 13. If the "Edit selected turning movement" field is highlighted in light blue, no origin destination flow has been selected. The individual key data of the selected origin destination flow is defined in Table 3 and must be configured according to their definition.
Table 3: Definition of the configuration of individual key data of a turn-off device turnin movement.
Save the entry with the "Save" button at the bottom right.
At the end, all routes, angles and route assignments to the UUIDs must be checked again.
If there is a unambiguous zone assignment for each intersection arm, make sure that all "Input UUIDs" for entering turning movements are identical. The same applies to exiting turning movements. Here too, the "AusgAbb-UUID" should be identical if the assignment is unambiguous (see Figure 14).
To delete an existing origin destination flow, the route from which the origin destination flow to be deleted originates must be selected. You can now select the unnecessary route and delete it using the red "Delete selected turning movement" button.
To add a missing origin destination flow, select the initial route and click on the blue "Add new turning movement" button to open a new window for configuring the route. The route can be defined as described in chapter 2.5.
Table 3: Definition of the configuration of individual key data of a turning movement
Save the entry with the "Save" button at the bottom right.
Camera mounting - horizontal angle to the object
Camera mounting - horizontal angle to the object
The software does not run; no data is generated. Problem types: a) Docker container and/or software is not running correctly, please contact . b) Data cannot be sent to MQTT endpoint: there are more than 10 MQTT events that have been sent to MQTT broker for at least 10 seconds without success. Please check whether the broker is active. c) Camera not connected: The camera connection cannot be established. Check whether the camera is switched on and whether the camera data (user name, password) is configured correctly.
Name | The name of the origin destination flow is generated for automatically created origin destination flows with the names of the routes and relative orientation to each other (right turning, left turning and straight ahead traffic). You can edit the name in this field as required. |
From route To route | "From route" is the route from which the origin destination flow begins and the "To route" always describes the route where the origin destination flow ends. The "From route" and "To route" are already defined for the automatically generated origin destination flows so that they do not need to be changed if an automatically generated origin destination flow is already configured. If you generate your own origin destination flow, you must select the "From route" and "To route" individually according to the desired origin destination flow. |
Event type | If a counting line (CL) instead of an OriginDestination was used to determine the origin destination flow when configuring the BMA, the counting line must be selected here. The UUID of the counting line with the corresponding direction (in, out) is then selected. |
From-zone UUID | All zone UUIDs of the selected camera(s) are stored in the selection menu of the From zone, even if the counts have already been completed. Make your appropriate selection of the entry zone for the From-zone of the respective origin destination flow. As a name for a zone can be assigned several times, it is recommended that the UUID of the selected zone is compared with the zone in the Control Center during configuration, as the UUID is unambiguous. |
To-Zone UUID | Corresponding to the From-zone, you can specify the appropriate UUID of the To-zone where the origin destination flow ends. |
Note! If only one BMA is used and the From or To zone is always the same, an from or to zone only needs to be defined once in a origin destination flow. The rest is added automatically. |
Warning! The automatic addition also takes place if several BMAs have been used. In this case, the origin destination flows must be adjusted retrospectively. In any case, origin destination flows must be checked at the end. |
Describes the name of the survey that you initially assigned when creating the survey. If required, the name of the survey can be edited in the corresponding field. As it is possible to filter the surveys by name, it is recommended to select an unambigous name. |
The start and end date defines the period for the data analysis. For the start and end date, 00:00 is automatically selected as the time, with the end date including the selected day. Example: A measurement on 01.01.2023 from 0:00 to 23:59 would therefore have 01.01.2023 as the start and end date. |
In order to change the location on the map, the checkbox "Activate map for editing" must first be ticked. You can use the button with the magnifying glass to open a search bar in which you can enter the desired address. The location is defined by left-clicking the marker on the interactive map. To protect the location from changes, the "Activate map for editing" checkbox can be unchecked. |
The time zone is set to the region "Europe/Vienna" by default. It is recommended to select the local time zone of the survey in the menu. |
The traffic types are the vehicle classes that are to be taken into account in the evaluation for this survey. By pressing the Ctrl key, several traffic types can also be selected for a single survey. In order to make the application possibilities of the evaluation more flexible, the selection of the survey can also be adjusted afterwards. If the desired traffic type does not appear, please contact customer service. |
Note: Activate the angle help to read the exact angle from the north axis of the node to the route. |
The name of the route is defined in this field. This name appears both in the evaluation in the Data Center and in the excel file. |
Determine the angle between the road and the intersection. To be able to read an angle, the angle help can be activated using the "Show angle help" checkbox. The center point of the intersection with the axis pointing north represents the zero axis. |
Enter the direction of traffic of the route. Choose between: - Two-way traffic - Only road users approaching the intersection - Only road users leaving the intersection Note! It is also possible to detect wrong-way drivers in a one-way road. In the case of one-way roads, for example, this can be specified as two-way traffic in order to output the traffic in both directions. |
If you have added a counting line for detecting pedestrian crossings during configuration in the Control Center, select this checkbox. The window then expands (see Figure 12). - Enter the corresponding crossing that you have configured - Name the crossing and note the direction in which the crossing is recorded |
Attention! If you are working with several BMAs at one intersection, special care must be taken to ensure that origin destination flow is not stored with IDs of different BMAs. |
The name of the origin destination flow is generated for the automatically created origin destination flow with the names of the routes and relative orientation to each other (right turn, left turn and straight ahead). If required, you can edit the name in this field. |
From route To route | "From route" is the route from which the route begins and the "To route" always describes the route where the route ends. The "From route" and "To route" are already defined in the automatically generated origin destination flows, so that they do not need to be changed if an automatically generated driving relationship is already configured. If you generate your own origin destination flow, you must select the "From route" and "To route" yourself according to the desired origin destination flow. |
Choose between the event types with which you have recorded origin destination flow. If a counting line (CL) was used to determine the origin destination flow during the configuration of the BMA the counting line must be selected here. The UUID of the counting line with the corresponding direction (in, out) is then selected. |
All zone UUIDs of the selected camera(s) are stored in the selection menu of the From zone, even if the counts have already been completed. Make your appropriate selection of the entry zone for the From zone of the respective origin destination flow. As a name for a zone can be assigned several times, it is recommended that the UUID of the selected zone is compared with the zone in the Control Center during configuration, as the UUID is unambiguous. |
If only one BMA is used and the From or To zone is always the same, a From or To zone only needs to be defined once in a origin destination flow. |
Note! If only one BMA is used and the from or to zone is always the same, an from or to zone only needs to be defined once in a driving relationship. The rest is added automatically. |
Attention! The automatic addition also takes place if several BMAs were used. In this case, the routes must be adjusted afterwards. The origin destination flows must be checked at the end. |
Note! To check the configured intersection, it is advisable to view the turning movement counts in the Data Center at the same time. If the turning movement counts already reflect implausible values or the modal split is atypical, the configuration should be checked again. |
Note! If a new origin destination flow is added, its "From route" and its "To route" must be defined indivually. |
Device Offline
Triggers when a device changes its status from online to offline.
Connection: Online
Connection: Offline
Device Error
Triggers when one or more streams change their status from Running or Warning to Not Running.
Stream status: Running or Warning
Stream status: Not Running
Device Warning
Triggers when the status of one or more streams changes from Running to Warning.
Stream status: Running
Stream status: Warning
REST API - Access to the underlying data from Data Analytics or the widgets via API
For each widget in Data Analytics, the underlying data can be queried via a provided REST API. Integration into third-party applications is quick and easy.
As soon as you configure a widget, you will find the API Call item in the side menu. This option is available for every widget.
Execute the call accordingly and test it directly in the dialog box, including the response format, by clicking _Try it out!
The dialog box that appears contains detailed information about what the API call looks like for this widget's data. Copy the code provided and use it as required.
This access token is temporary. For permanent integration in third-party applications, you need a permanent token. Please contact our Support.
We strictly adhere to the OAuth flow documented by Microsoft. There are several Client Libraries that you can use.
Below you can see a widget in Data Analytics that is used for bicycle counting. The corresponding widget type (Traffic Counting) has been selected, the data is aggregated per tag, broken down by object class and direction and filtered by bicycles.
API request
The API call shows the corresponding GET request for this data as shown below:
API-Response:
The REST API is based on _Cube.js_. You can find more information and details about this and how it works in general in this external documentation.
Definition of object classes for Traffic & Parking (Standard & Accuracy+)
The following images are only intended as examples and are not intended to provide information about exact camera distances or perspectives.
Class | Subclass | Definition |
---|---|---|
How you can best reach us
Please report any problems, questions or potential bugs in our Support Center.
Name
Note!
Date
Location of the survey
Time zone
Traffic types
Name
Angle
Direction
Crossing
Name
Event type
From zone UUID
To-one UUID
car
Car includes small to medium-sized cars up to SUVs, pickups and minivans e.g. VW Caddy, Renault Kangoo. This class does not include cars with trailers.
car
van
Vans are vehicles for transporting a larger number of people (between six and nine) e.g. VW Multivan, or are used for deliveries e.g. VW Transporter, Fiat Ducato.
Delivery vans with closed and open loading space are also included, e.g. Iveco Daily.
car
car with trailer
Cars and vans towing a trailer are considered car with trailer. For correct classification, the entire vehicle and at least one of the trailer's axles must be visible.
truck
single unit truck
Single unit trucks are vehicles defined as unit transporters with two or more axles. It is important for the definition that the towing vehicle and semi-trailer cannot be separated from each other.
truck
articulated truck
Articulated trucks are large vehicles with more than two axles in which the articulated truck and semi-trailer can be separated. An articulated truck without a semi-trailer is classified as a single unit truck.
truck with trailer
Single unit trucks or articulated trucks towing an additional trailer are defined as truck with trailer.
bus
-
A bus is a vehicle for transporting a large number of people. This includes coaches, double-decker buses, motor coaches, buses, passenger coaches and school buses.
motorbike
-
The motorbike class includes a person riding a motorized single-track vehicle. This also includes motorcycles with sidecars; e-bikes are not included in this class. Motorcycles without a rider are not taken into account.
bicycle
-
The class bicycle includes a person who actively rides a bicycle. Persons pushing a bicycle are not included in this class and are considered a person. Bicycles without a rider are not included.
person
-
The class person includes pedestrians: Inside as well as people who ride segways, skateboards, etc. ride. This class also includes people pushing a bicycle or baby carriage.
scooter
The class scooter includes a person riding a scooter that is either motorized or not. A scooter normally consists of two wheels and a handlebar.
tram
The class tram refers to a means of public transport that runs on rails along roads or dedicated streetcar routes. Streetcars are usually electrically powered and draw their electricity from overhead lines.
other
-
Vehicles or objects that do not correspond to the above classes fall into the other class. This applies to tractors (with or without trailers), ATVs and quads, forklifts, road rollers, excavators and snow plows.
Evaluation of the generated data for transport planning analyses
As soon as the survey has been created, the processed data is displayed in the Data Center. The data can also be downloaded in the form of an Excel file. To do this, call up the "Data Center" tab.
Select the corresponding tenant to which your survey has been assigned. To make it easier to find the survey you are looking for, you can filter the surveys by name, the survey period (start and end date) and the selected map section.
In the Data Center, you have the following functions to gain insights from a traffic count.
In the Data Center you will find an overview of the BMAs in use, the evaluated traffic object classes, the period of the survey and the resulting duration of the survey, the time zone set for the survey and the location of the survey (see Figure 17).
You can have the daily traffic distribution evaluated for different days, which you can select in the calendar in the "Day for graphs" window.
In addition, the daily traffic distribution can be evaluated for different object classes. To do this, you must select or deselect the relevant obect classes in the "Displayed obect classes and grouping" window.
The daily traffic distribution can also be output for a specific time window on the selected day. To filter for the desired times, click on the start time and drag the mouse to the end time of the time slot while holding down the button. Use the button to extend the time slot to the whole day again.
The calculated daily traffic distribution can be downloaded in .svg, .png and .csv format by clicking on the button.
The total traffic volume for each defined intersection arm can be read in the "Evaluation" window. Based on the total traffic at the intersection , the relative modal split at the individual intersections arms is also calculated.
In addition, the inflow for each intersection arm into the intersection is output and its total traffic volume in the intersection is calculated.
In addition to this evaluation of the traffic volume, the modal split is analyzed by calculating modal split for each object class in relation to the total traffic volume
To better analyze the traffic volume, the weather data for the selected day is retrieved and displayed in the "Day for graphs" window (see Figure 19).
Turning movement counts are generated in the corresponding window for the selected period and the selected object classes of the daily traffic distribution (see Chapter 3.2) (see Figure 20). Above the defined name, the total inflow into the intersection is shown in bold, and the outflow is shown below the line. The distribution of inflows and outflows from and to the individual intersection arms can be found below and above the total number.
The "Download traffic data" button in the survey overview takes you to the download view (see Figure 22).
In the download view, which is shown in Figure 22, you have the option of selecting the time resolution of the measurement data in the evaluation file to be downloaded. You can also divide the evaluation classes into any number of combined classes. It is not possible to exclude individual object classes that were defined during the survey. If individual object classes are not to be included in the Excel evaluation, this must be adjusted in the configuration.
Finally, the date of the Excel evaluation must be specified. You can only select a date within the survey period. If you download the measurement data for several days at the same time, you have the option of downloading individual data records per day or a bundled .zip file with all days.
The evaluation file is an Excel file consisting of several tables that cover the individually configured object classes on the one hand and contain the configured summarized object classes on the other hand. There is also a table with an explanation of the evaluation file. If crossings have been configured for routes, these are created in a separate spreadsheet with all the crossings created.
By default, the entire 24 hours of the selected day are analyzed in the evaluation file.
Lines 1 to 8 have the structure shown in Figure 23. The key data of the survey (name of the survey, counting date, start time and location) is documented and the measurement data in the table is analyzed with regard to the variables "day peak", "morning peak", "evening peak", "day traffic" and "night traffic".
The measurement data collected for the individual origin destination flows are listed below the key data. Line 9 contains the respective From-route for the origin destination flows, which is fully defined by the respective To-Route in line 11.
In the columns "Interval" and "Total hour", the total traffic load for the respective hour and for the respective interval - which corresponds to the time resolution of the measurement - is calculated. The hourly total is the sum of the subsequent hour for the start time, which is in the same row.
In the rows below the 24-hour measurement data, the variables "Total", "Day peak", "Morning peak", "Evening peak", "Day traffic" and "Night traffic" are defined for each origin destination flow (see Figure 25).
In the columns next to the 24-hour measurement data, inflows and outflows from and to the intersections arms as well as the total traffic volumes of the individual intersection arms for the selected time interval are determined for each intersection arm (see Figure 26).
Overview of the traffic count
Daily traffic distribution
Evaluation
Weather data (in new release)
Turning movement counts
Download the traffic count data
Attention!
If no arrow is shown between the individual route arms, this may mean that this orogin destination flow has not yet been configured or that no objects have been detected that fulfill the existing configuration. The configuration should therefore be checked - and adjusted if necessary.
Attention!
In order for the calculated values to be displayed correctly in the evaluation file, you must activate editing in the evaluation file.