B101 & B401

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

Device update

Products (BMA, Mobile BMA, BCA, B101/B401)

Update size: ~130MB

Improvements & Bugfixes

• 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

Data Center

Parking - Current and historical parking utilization

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

Control Center

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

​

• 1 x BMA

• 2 x Pole mounting clamps

• 1 x Power cable

Use this documentation to learn more about the technologies and products of Bernard Technologies and how to use them.

Who is this documentation for?

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 protection and security

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.

Disclaimer

1. mounting the camera

The camera is attached to the pole by using clamps. These adapt to the diameter of the pole.

2. Drilling of a second hole

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

Pole-mounted battery (optional)

1. Positioning the battery

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.

2. Connecting the battery

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.

Technical data of battery

Requirements for poles

Diameter min. 10 cm

To ensure successful charging of the battery box, the following steps must be followed in the order indicated:

1. Charger is disconnected from the mains (must not be connected to 230 VAC!)

2. Connect charger and rechargeable battery

3. Connect charger to mains (230 VAC)

4. <Charging in progress...>

   • Bulk LED = charging in progress

   • Absorption LED = charging in progress

   • Storage LED = charging process completed

5. Disconnect charger from mains (must not be connected to 230 VAC)

6. Wait <30 seconds>

7. Disconnect charger and battery

8. Test: After successful charging, the voltage of the battery should be at least 13.5 VDC

Installation

Instructions for setting up a mobile traffic survey.

1. Location

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.

2. step by step instructions

1. the mobile system must be attached to a fixed infrastructure

2. 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.)
3. to prevent easy removal of the mobile BMA, install two padlocks through the ratchet element of the tensioning straps
4. place the BMA on the top element of the telescopic mast and fix it in place with a twist-and-push movement
5. attach the BMA to the back of the lower pole strap

6. use the supplied reusable cable tie and pull it hand-tight
7. connect the 2-pin black/blue plug to the BMA. Make sure that the plug is inserted straight
8. Next, connect the 2-pin gray plug to the back of the battery box and close the plug fuse
9. lift the battery box and place the battery box in the middle guide of the C-profile

10. if the battery box is in the correct position, you can insert a padlock through the hole at the lower end and close it
11. loosen the twist lock on the mast element and raise the mast to the desired height

12. 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

13. check the current alignment of the BMA using the Control Center

14. you can adjust the alignment around the vertical axis by rotating the mast element

15. to change the alignment around the horizontal axis, the mast must be fully retracted and the cover of the sensor opened

16. turn the optical part of the sensor up or down to obtain the desired alignment and close the cover of the sensor

17. carry out steps 12 - 14 again

18. finally, place the mast lock around the twist lock of the lowest mast element and secure it with a padlock
19. Now you can set your sensor via the Control Center and configure the current traffic survey in the Data Center

Dimensions

Data protection and security

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.

*) for optimum alignment and calibration according to installation instructions

Function modes:

Parking Mode ANPR:

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.

Parking Mode GDPR:

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.

Data protection and security

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.

Disclaimer

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.

Sensor placement

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.

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).

BERNARD Mobility Controller (BMC) 2.2

The BERNARD Mobility Controller (BMC) serves as an interface between 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. ( and ))

• 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.

BMA

• The Classification has been improved, especially the classes Single Unit Trucks and Vans. This affects the Traffic& Parking - Standard and Accuracy+ models.

BERNARD Control Analyser

• 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.\

Control Center

• 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.

Data Center

• Bug fix for the grouping of the turning movement counts

1. Orientation

Good positioning and alignment of the optical sensor is crucial in order to guarantee optimum detection accuracy. Detailed instructions can be found in the section.

2. Mounting the sensor

The sensor is attached to the poles using clamps. These adapt to the diameter of the pole.

3. Mounting the compute module

The compute module is attached to the poles using clamps. These adapt to the diameter of the pole.

4. Connection the sensor with the compute module

The sensor is connected to the computer unit using the network cable supplied.

5. Power supply

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.

• 1 x B101 / B401

• 1 x Cable with 2,5 / 5,5 mm DC-Jack

For reasons of readability, the masculine form has been chosen in the text, the information refers to all genders.

List of abbreviations

Fundamentals

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.

General safety instructions

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.

Explanation of symbols

Personnel qualification

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.

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.

Schematic structure TLS- BMC - BMA

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.

Description of the BMC

Device dimensions

Block diagram

Terminal connections

Power supply

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.

Transportation, packaging disposal and storage

Only open and completely remove the packaging at the actual installation site.

Transportation

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.

Storage

If possible, the device must be stored in a dry and dust-free place. Avoid direct UV radiation.

Installation

The installation of the BMC in combination with one or more BMAs is described below.

1. De-energize the system

2. Snap the Power Supply onto the DIN rail. For a cable length > 5 m: Set the DC voltage to 30 V using "+V Adj".

3. disconnect all connection blocks from the BMC

4. 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.
5. 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.

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.

7. 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)

Commissioning

1. Switch on the system.

2. The power LED on the power supply should light up

3. 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.

4. 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

5. 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.

LED display

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.

Configuration of the BMC in the BERNARD Control Center

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)".

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.

Maintenance

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.

Cleaning

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.

Malfunctions

If the system malfunctions, the following points should be checked one after the other.

Decommissioning, dismounting and disposal

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.

Regulations

DSGVO

No personal data is read or processed in the BMC. This means that the use of the BMC is harmless under data protection law.

Safety

The BMC complies with the Electromagnetic Compatibility Directive 2014/30/EU. This results in the CE certification affixed to the underside of the device.

Environmental management

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.

Modification

It is not permitted to modify the BMC in any way. Any modifications will invalidate the manufacturer's service and liability with immediate effect.

Data protection and security

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.

Disclaimer

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:

What data can be generated?

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.

What needs to be considered for a successful analysis?

Camera setup

In the table below you will find detailed information on the requirements, settings and positioning of the camera.

Specifications for the environment

Hardware specifications

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.

What needs to be considered for a successful analysis?

Specifications for the environment

Hardware specifications

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.

What data can be generated?

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. ​These classes are recognized by our software.

What needs to be considered for a successful analysis?

Camera setup

In the table below you will find detailed information on the requirements, settings and positioning of the camera.

Specifications for the environment

Hardware specifications

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

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).

What data can be generated?

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).

What needs to be considered for a successful analysis?

Camera setup

In the table below you will find detailed information on the requirements, settings and positioning of the camera.

Specifications for the environment

Hardware specifications

Requirements

• DC power supply unit with 12 to 48 V output voltage and at least 20 W (B101) or 60 W (B401) output power.

• 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)

Installation

• 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.

Configuration

Network

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.

Control Center

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.

Troubleshooting

What data can be generated?

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.

Positioning of the camera

**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 or a 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.

General recommendations for camera positioning:

• 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

What must be considered for a successful analysis?

Camera setup

In the table below you will find detailed information on the requirements, settings and positioning of the camera.

Specifications for the environment

Hardware specifications

Management of your BERNARD devices

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.

Camera settings

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.

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.

Models

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:

Event triggers

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:

Event types

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:

Details on event triggers

Data transmission

General monitoring

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.

Status of the device connection

Device status

Status of the streams

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:

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

The BERNARD Data Center API provides comprehensive options for querying traffic data and moving traffic. This RESTful 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.

https://datacenter.bernard-gruppe.com/api/v3/docs

If you have any questions or problems, please contact our support team

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.

How to get the URL for your specific API

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.

Example

Retrieve device status

1. call the Swagger UI

2. the API call gives you information about the device status as follows

{
  "boxStatus": {
    "connectionState": "CONNECTED",
    "runtimeState": "DISABLED"
  },
  "id": "676cac42-f3d6-416d-ac83-3f54f1c0bb43",
  "name": "7th NE parking garage entrance",
  "statusId": "676cac42-f3d6-416d-ac83-3f54f1c0bb43",
  "tags": [
    {
      "name": "Roxxon Energy Corporation"
    }
  ],
  "type": "P100"
}

1. the different statuses of the devices are defined as follows in the API documentation

1. you can also retrieve the status of the individual streams. The API provides the following results

[
  {
    "id": "fd02a4c9-5e55-4100-a2fd-d76d16993bce",
    "name": "",
    "model": "traffic-detector-urban-standard-fast",
    "streamStatus": {
      "state": "NOT_OPERATIONAL",
      "errorReason": [
        "ENGINE"
      ]
    },
    "enabled": true
  }
]

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.

Scheduling 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

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

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.

Adding a new user profile

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.

Editing an existing user profile

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.

Types of user profiles

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.

General

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.

Creating alerts

Let's start by creating alerts. This is done in three steps:

Condition for the alert

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:

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:

Select device for the alert

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:

Define recipient

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.

Edit or delete alerts

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.

Configuration of the 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:

https://datacenter.dashboard.bernard-gruppe.com/

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.

Selection of the tenant

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.

Definition of key data (location, date and class selection)

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).

Adding / editing of cameras

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.

Editing of the routes

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.

Configuration of the routes

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).

Configuration of turning movements / Definition of origin destination flows

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.

Checking the configuration

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).

2.2 Deletion and adding of origin destination flows

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.

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.

Overview of the survey

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).

Daily traffic distribution

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.

Evaluation

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

Weather data

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

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.

Download the analysis file

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.

3.7 Evaluation file

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).

API call

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!

Curl command

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.

Authentication

We strictly adhere to the OAuth flow documented by Microsoft. There are several Client Libraries that you can use.

Example of a request

Bicycle counting

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:

https://example.com/cubejs-api/v1/load?query=
{
   "measures":[
      "CrossingEvents.count"
   ],
   "dimensions":[
      "CrossingEvents.classification",
      "CrossingEvents.direction"
   ],
   "segments":[],
   "filters":[
      {
         "member":"CrossingEvents.streamId",
         "operator":"equals",
         "values":[
            "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
         ]
      },
      {
         "member":"CrossingEvents.classification",
         "operator":"contains",
         "values":[
            "bicycle"
         ]
      },
      {
         "member":"CrossingEvents.lineId",
         "operator":"equals",
         "values":[
            "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
         ]
      }
   ],
   "timeDimensions":[
      {
         "dimension":"CrossingEvents.timestamp",
         "granularity":"day",
         "dateRange":"This week"
      }
   ],
   "order":{}
}

API-Response:

{
  "queryType": "regularQuery",
  "results": [
    {
      "query": {...},
      "data": [
        {
          "CrossingEvents.classification": "bicycle",
          "CrossingEvents.direction": "in",
          "CrossingEvents.timestamp.day": "2021-11-02T00:00:00.000",
          "CrossingEvents.timestamp": "2021-11-02T00:00:00.000",
          "CrossingEvents.count": "235"
        },
        {
          "CrossingEvents.classification": "bicycle",
          "CrossingEvents.direction": "out",
          "CrossingEvents.timestamp.day": "2021-11-02T00:00:00.000",
          "CrossingEvents.timestamp": "2021-11-02T00:00:00.000",
          "CrossingEvents.count": "234"
        },
        {
          "CrossingEvents.classification": "bicycle",
          "CrossingEvents.direction": "in",
          "CrossingEvents.timestamp.day": "2021-11-03T00:00:00.000",
          "CrossingEvents.timestamp": "2021-11-03T00:00:00.000",
          "CrossingEvents.count": "203"
        },
        {
          "CrossingEvents.classification": "bicycle",
          "CrossingEvents.direction": "out",
          "CrossingEvents.timestamp.day": "2021-11-03T00:00:00.000",
          "CrossingEvents.timestamp": "2021-11-03T00:00:00.000",
          "CrossingEvents.count": "249"
        }
      ],
      "annotation": {...}
    }
  ],
  "pivotQuery": {...}
}