Blickfeld WebGUI Tutorial
Explore all software features available for Blickfeld LiDAR sensors.
This tutorial provides a comprehensive overview of all software features and covers the Qb-series in one guide.
To view the GERMAN version of the tutorial, use this link.
Status: MIRIAM Release v2.17
Blickfeld WebGUI
1.1 Login
1.2 User Management
3.1 Sensor Setup
3.2 Zone Management
3.3 Scan Pattern
3.4 Network Setup
3.5 Push
3.6 Flow
4.1 Firmware
4.2 Diagnostic
4.3 Maintenance
To view the GERMAN version of the tutorial, use this link.
Dashboard Overview
1.1 Login
1 Dashboard | 2 | 3 | 4 | 5
4
The sensor is shipped in “Factory user” mode; serial number and password are printed on the device label.
To access the sensor, enter the serial number in the browser.
https://qb2-<SERIAL/NUMBER>/
Accept potential safety indications (self-signed certificate) and proceed to sensor login.
Sign in with the username and password as printed on the device label. On first login, the user has to change the password. You can either request the sensor to suggest a password or use a self chosen password which is evaluated:
A password reset by Blickfeld is possible.
All sensors
Confidential
Dashboard explanation
1 Dashboard | 2 | 3 | 4 | 5
5
Side-panel with various configuration options
Sensor status
Current user
Dark/light mode
Show/hide side panel
Currently installed firmware
Sensor serial number
Logout
User management
Fold in/out
All sensors
Confidential
Side panel explanation
1 Dashboard | 2 | 3 | 4 | 5
6
Initial start page when connecting to a Blickfeld LiDAR in the web browser
Visualization of the 3D point cloud data
Device configuration and dashboard (depending on your sensor) with various features & options: sensor setup, zone management, scan pattern, network setup, data push, Blickfeld Flow configuration
System configuration options like firmware uploads, maintenance and diagnostic reports
Smart sensor documentation
All sensors
Confidential
1.2 User Management
1 Dashboard | 2 | 3 | 4 | 5
7
How to add a new user:
All sensors
Confidential
1.2 User Management - User Account settings
8
Option to change the password
Option to generate a new application key
Overview of application keys
All sensors
Confidential
Viewer
2. Viewer
General Interface Explanation
1 | 2 Viewer | 3 | 4 | 5
10
All sensors
Return to the initial view of the point cloud
Fullscreen option
Date & Time
Sensor serial number
Live point cloud
Confidential
2. Viewer
Interface Explanation
1 | 2 Viewer | 3 | 4 | 5
11
By default, the foreground with its detected objects is displayed in color (blue); the background in grayscale
Zones slider to show/hide previously set zones. Active zones are colored in yellow, inactive zones in grey, intruded zones are red
Raw slider shows the live view of the point cloud without separation into fore-/background
Color slider to color the entire point cloud by intensity
Status of detection and malfunction detection (ON or WARNING)
Qb2
QbProtect
QbVolume
The point cloud scene can be recorded and saved directly to the pc running the browser.
You can extend the recording button and view the options to specify your recordings, e.g. To use a specific point cloud type, to disable zone states etc. in order to reduce data load for longer recording times.
Manually adjust the recording time (by default 1min)
Confidential
2. Viewer
Useful shortcuts
1 | 2 Viewer | 3 | 4 | 5
12
C
B
+
-
Color the point cloud by intensity
Display a bounding box around detected objects
Increase the point size
Decrease the point size
T
+
Tracking visualization
L
Show/hide labels of detected objects
V
+
Align video perspective of RTSP-Stream with current configuration in the viewer
All sensors
R
Z
Show/hide previously set zones as required
Show/hide the live view of the raw point cloud
General
Depending on license
G
Show/hide grid on the floor
F
Show/hide all foreground points (detected objects)
Confidential
2. Viewer
Quick edit for zones and categorized zone configuration panel
1 | 2 Viewer | 3 | 4 | 5
13
By double clicking on a zone, you enable the quick edit mode in the viewer to quickly enable simple zone changes.
Drag the yellow dots / handles to
Double click anywhere else to save. This feature works for every zone type.
Qb2
QbProtect
QbVolume
Confidential
2. Viewer
Alarm History for Security Applications
1 | 2 Viewer | 3 | 4 | 5
14
On-device alarm history records and replays zone states and object streams in the WebGUI viewer
Intruded zone name “x” + timing of intrusion
Qb2
QbProtect
Confidential
2. Viewer
1 | 2 Viewer | 3 | 4 | 5
Alarm History for Security Applications
15
By clicking an event, the viewer shows the motion replay of this event, not the live point cloud. Detection is not interrupted during replay.
Additionally, unique URLs are created per each event, which can be shared with colleagues via a link. This directly shows the event in the requested perspective.
If the device is not rebooted, it keeps a motion replay in memory (ca. +/- 10s around the timing of intrusion), and ca. 60 events are stored permanently.
Qb2
QbProtect
Confidential
2. Viewer
1 | 2 Viewer | 3 | 4 | 5
Alarm History for Security Applications
16
Alarm history export:
Save & download alarm history on your PC. Either download all events or select single events you want to safe by ticking the boxes.
Alarm history upload & replay mode:
The saved alarm history events can be replayed in the WebGUI.
This can be used to efficiently inspect and analyze events, e.g. from remote installations. Click the upload button to upload events from your local device.
You can see exported events & the background, and you can do motion replay to gain an understanding of the scene (post-event analysis).
Qb2
QbProtect
Confidential
2. Viewer
1 | 2 Viewer | 3 | 4 | 5
Alarm History for Traffic Applications
17
Qb2
QbProtect
The event history of traffic applications (only available for Qb2) shows the classified vehicle types, their velocity and timing of speed measurement as well as their dimensions. We can (currently) distinguish 4 different vehicle types: car, car with a trailer, van, truck. This is shown within the object label.
By clicking on the recording icon in the event history, the recording of alarm events can be paused. This pause mode helps preserve relevant event data (e.g. from nighttime monitoring) and prevents it from being overwritten during inactive periods.
This feature is available for QbProtect as well.
Confidential
2. Viewer
1 | 2 Viewer | 3 | 4 | 5
Alarm History and disqualification of alarms in harsh weather conditions
18
Qb2
QbProtect
Fog detection:
Weather conditions like strong fog may cause false alarms as it builds up noise clusters that look like objects. This is why we detect the fog and send out warning messages to the user.
Fog can be detected by comparing the mean photon count of the current scene to the mean photon count of the initially created background. A threshold value is set in order to create a disqualification alarm when necessary.
The warning message can be seen in the diagnostics report as well in the alarm history with the events marked accordingly.
Rain detection (for traffic zones only)
The traffic zone algorithm is able to detect rain and remove e.g. trails of water behind a car for correct car length calculation and classification. The rain presence information is displayed in the WebGUI in the respective event. The rain filter can be deactivated via API.
Confidential
2. Viewer
Worldmap Viewer, available in the Blickfeld Dashboard
1 | 2 Viewer | 3 | 4 | 5
19
Geo-Coordinate output for objects and zones:
This feature enables the display of objects and zones with precise geolocation on a world map within the Blickfeld Dashboard. Integration is achieved via a Node-RED flow within the Blickfeld Flow environment. The world map can also be opened in a separate browser tab for an extended view.
The map provides a clear 2D overview of the scene, showing all defined zones and detected objects. Tracked objects are visualized with their movement paths, while zone intrusions are highlighted in red. Intruding objects are automatically marked as such.
Requirement:
To ensure accurate geolocation, the sensor must be properly configured. The sensor’s position needs to be defined with geo-coordinates during setup. Any changes made in the WebGUI are reflected in real-time on the world map viewer.
Qb2
QbProtect
Confidential
Configuration
3. Configuration
1 | 2 | 3 Configuration | 4 | 5
Configuration Dashboard
21
The configuration dashboard provides a clear overview of all configurations and comes with preconfigured settings that can be used as-is or fine-tuned as needed. The available actions are depending on device license - this example shows the Qb2.
All sensors
You can reset object tracking to defaults via the dashboard. Advanced tracking parameters are described in the documentation and can be configured via API.
Confidential
3. Configuration
1 | 2 | 3 Configuration | 4 | 5
Configuration Dashboard
22
Successful action (green)
Busy action (orange)
Failed action (red)
Inactive action (grey)
All sensors
Confidential
3. Configuration
3.1 Sensor Setup Overview
1 | 2 | 3 Configuration | 4 | 5
23
Choose between 2D or 3D view
Coloring according to range can be adapted manually
Add another sensor to edit the sensor setup
The sensor setup shows a snapshot of the point cloud - this is not a live view.
To create a new snapshot of all point clouds, use the refresh button.
Select a sensor to edit the setup
Swarm mode allows multiple sensors to sync their settings (like scan patterns and zones), visualize their combined data, and track objects detected together. This requires a low-latency and high-bandwidth between all sensors in the swarm.
Define the exact coordinates of the sensor’s position and place a map in the background of the point cloud
Set an interval at which the point cloud will be fetched for processing
Show/hide the point cloud of a sensor
Create a new snapshot of the sensor’s point cloud
Show / hide snapshots of devices
Delete sensor from the sensor setup
Qb2
QbProtect
QbVolume
Confidential
3. Configuration
1 | 2 | 3 Configuration | 4 | 5
3.1 Sensor Setup Overview
24
Points colored in white are located on the ground plane of the orientation grid
Sensors to be setup can be selected here
Use the side panel on the right or the arrows to pull/drag the sensor’s point cloud in the orientation grid
The point cloud can be moved along the X, Y, Z -axis or be rotated
Click to trigger alignment processing
Alignment strategies:
AUTO (vertical point cloud alignment according to gravity vector);
ACCELEROMETER (if no plane is found, alignment will rely on accelerometer data)
or PLANE SEGMENTATION (largest plane is used for alignment)
In case a device different from the local device is added to the sensor setup (e.g for swarm applications), this section will display the fully qualified domain name (FQDN) and the serial number. When the user management is activated, enter the application key.
Multiple point clouds can be automatically orientated to each other
Qb2
QbProtect
QbVolume
Confidential
3. Configuration
1 | 2 | 3 Configuration | 4 | 5
3.1 Sensor Setup - Alignment Example
25
Example:
Automatic sensor alignment / vertical point cloud alignment
Qb2
QbProtect
QbVolume
Confidential
3. Configuration
3.1.1 Sensor Setup - Geolocation & Trigger mode
1 | 2 | 3 Configuration | 4 | 5
26
Using the geolocation function, a map can be placed in the background.
For this, the corresponding coordinates must be entered; the map is then generated automatically.
Multiple map providers are available, e.g.: BingMaps, BayernAtlas and OpenStreetMap
The trigger mode allows you to set an interval at which the point cloud will be fetched for processing by Blickfeld Percept Pipeline.
Currently, this can be set to XX minute(s), hour(s) or day(s).
For example, in some volume monitoring applications, volume data and the corresponding point cloud is only needed once per day.
Qb2
QbProtect
QbVolume
Confidential
3. Configuration
3.1.2 Zone Management Overview
1 | 2 | 3 Configuration | 4 | 5
27
Qb2
QbProtect
QbVolume
Security: Detects whether an intrusion has occurred or not
Exclusion: Excludes points inside the zone from further processing
Occupancy: Detects whether is a region is occupied or not
Volume: Measure the quantity of a pile of material
Enable or disable point cloud visualisation and zone labels
Select how the point cloud is displayed.
Full: Complete point cloud
Filtered: Points inside exclusion zones are filtered out
Foreground: Point cloud containing only foreground/points that do not belong to environment background
Coloring of the entire point cloud related to distance, height or intensity values
Pre-defined viewer camera positions on the point cloud
Zone types - depending on license
Overview of all zones
Recording feature
Traffic: Detects and classifies vehicles
Confidential
3. Configuration
3.1.2 Zone Management Overview
1 | 2 | 3 Configuration | 4 | 5
28
Only valid for Qb2 and QbProtect: This section combines all parameters related to the processing of the point cloud. Changes to these parameters will have major effects to what will be considered a detection.
Reset/Rebuild background
Open Perception Configuration
Qb2
QbProtect
Confidential
3. Configuration
3.2.2 Zone Management - Point Cloud Visibility Example 1
1 | 2 | 3 Configuration | 4 | 5
29
Qb2
QbProtect
QbVolume
Point cloud type “Filtered”: Points within an exclusion zone are not shown
Confidential
3. Configuration
3.2.2 Zone Management - Point Cloud Visibility Example 2
1 | 2 | 3 Configuration | 4 | 5
30
Full vs. foreground point cloud
Qb2
QbProtect
QbVolume
Confidential
3. Configuration
3.2.1 Zone Management - Perception Configuration
1 | 2 | 3 Configuration | 4 | 5
31
Algorithms separating the input point cloud into foreground and background.
Background: Points in the point cloud that are static over a certain period of time are included in our background model (static: only once initial | dynamic continuous over time), e.g. walls, floors, etc.
Foreground: Visualisation of all points that are not yet known to the background model, e.g. moving or newly appeared objects.
Initialization frames are the frames received by the sensor, used to create the initial background view. Make sure that the scene does not contain moving objects (foreground points) when refreshing/rebuilding the background so that these initialization frames only consist of background.
This feature controls the update rate of the background view. An higher value will result into a faster convergence of elements in the scene to the background.
This feature requires a trade-off between fast noise reduction (e.g. due to vegetation or other scene changes) and sensitivity (e.g. objects which actually raise an alarm might be merged to the background too quickly).
This feature controls how much noise the background/foreground is expected to have
In this example, it takes 57 frames for an object to change from foreground into background
Add object awareness (BETA) to motion detection using the dynamic background mode. If object awareness is enabled, the model update is freezed for areas around detected objects. This can be very helpful to avoid that stalled objects, which stay in the scene for a while or objects which are following similar paths, cause the generation of an invalid background model.
Qb2
QbProtect
Confidential
3. Configuration
3.2.1 Zone Management - Perception Configuration
1 | 2 | 3 Configuration | 4 | 5
32
Algorithms separating the input point cloud into foreground and background.
Static - With the static background, the initial background is built once. The new point cloud is then compared against it repeatedly (only suitable for static scenes).
Initialization frames are the frames received by the sensor, used to create the initial background. Make sure that the scene is empty when refreshing/rebuilding the background so that these initialization frames only consist of background.
Minimum distance of a point to the recorded background, to be considered foreground. Points with a distance below this value will not be considered for detection.
Qb2
QbProtect
Confidential
3. Configuration
3.2.1 Zone Management - Perception Configuration
1 | 2 | 3 Configuration | 4 | 5
33
In this section, you can further filter the foreground using point clusters
Specify the minimum number of neighbor points a single point must have within the specified search radius to be considered a foreground point. Points that do not fulfill this criterion will not be used for further processing and detections.
Specify the radius in meters in which the search for neighbor points is performed for each point.
In this example:
Between 0.0 and 0.01 m2, an object is considered as “small”
Between 0.01 and 0.16 m2, an object is considered as “medium”
Between 0.16 and 1.6 m2, an object is considered as “large”
In this section, users can define the minimum value that the surface area of an object's bounding box should exceed to be categorized as an object. This can be defined separately for a small, medium, and large objects
Only the surface area of the bounding box sides are considered
Qb2
QbProtect
This button activates the event history. State and object data is then captured event-based, e.g., when an intrusion occurs. By default, the capture window is +/- 10 seconds around the event. The data is intended for event analysis and fine tuning of configurations.
Confidential
3. Configuration
3.2 Zone Management - Security Zone
1 | 2 | 3 Configuration | 4 | 5
34
Newly generated zones can be placed with the arrows via drag & drop or with the side panel
Delete zone
Customizable zone name
In the list, active zones are colored in white, inactive zones are diagonally dashed.
The zone that is currently being edited is highlighted in green.
Security Zone 2
Security Zone 2
Intrusions can be triggered according to number of points, object size or movement direction.
Maximum points
To trigger an intrusion, an object must fulfil all of these conditions.
Minimum active intrusion duration of an object before alarm is triggered.
Maximum ‘0’ points means a minimum of 15 points, no matter how many.
Zone (de-)activated
Alarm will be held for this time (minimum). When configured to 60s: A 60s idle period (=no detected intrusions) is required before a new alarm can be raised.
Qb2
QbProtect
Feature see slide 36
Confidential
3. Configuration
3.2 Zone Management - Security Zone
1 | 2 | 3 Configuration | 4 | 5
35
Qb2
QbProtect
Minimum lifetime of an object in the scene before alarm is triggered.
When set to “Any”, this feature allows to consider an object as intruder if at least one point of it is inside the intrusion zone (very sensitive, see GIF above). When set to “Center”, the center of the object has to be inside the zone to be triggered.
When the movement direction parameter is active, an arrow in the security zone shows the object’s movement direction that triggers an alarm. You can turn the zone in the desired direction via “rotate”.
In this example, intrusions are triggered by object size: Large and medium
Minimum track length of object before an alarm is triggered.
Minimum active intrusion duration of object before alarm is triggered. Example: Frame rate 2 Hz, minimum intruding duration 2s, confidence of 50% ⇒ Detections in 2 out of 4 last frames raise an alarm
Alarm is triggered when an object moves in a specific direction. When switched on, an arrow inside the zone visualizes the direction that triggers an alarm. This now also supports turnarounds.
Confidential
3. Configuration
3.2 Zone Management - Directional Security Zone
1 | 2 | 3 Configuration | 4 | 5
36
Security Zone 2
Security Zone 2
Security Zone 2
Example: Only OUT zone is triggered
Example: IN & OUT zones are triggered
Qb2
QbProtect
In this example, intrusions are triggered by movement direction.
Security Zone 2
Security Zone 2
Directional security zones raise an alarm when an object is moving across a boundary plane / the zone middle-plane in inbound direction.
-> Alarm while the intruding object is being tracked
-> Alarm will be disabled when the intruding object is leaving in the reverse direction (outbound)
Example: Only OUT zone is triggered
The tampering feature is disabled by default (set to 0). It monitors whether the sensor’s view of a defined zone is being blocked. The coverage threshold determines when an alarm is triggered. E.g., if the visibility of a zone drops below 80% of its background visibility, a coverage alarm is raised. This allows the system to detect if the sensor is partially obstructed or tampered with. Individual tampering events are available via the Percept gRPC event service, in the WebGUI event history, and through ONVIF. The current zone coverage level is visualized in the WebGUI viewer, but not available via RTSP.
Confidential
3. Configuration
1 | 2 | 3 Configuration | 4 | 5
3.2 Zone Management - Security Zone - Test Events
37
For easier testing of security applications in the field (e.g. VMS installations), test events can be manually triggered, marked with the Flask icon.
Via gRCP API or Blickfeld Flow, we allow to inject test events of a security type (intrusion or tampering) with a desired duration. If the Flask icon is selected (turns yellow), the generated test events from this security zone are visualized in the viewer as a standard event. The event history depicts these injected test events also with the Flaks icon for easier identification. The replay it not supported for test events.
If you want to test an event, click on the flask icon.
Once the test event is generated, the icon turns yellow.
Confidential
3. Configuration
1 | 2 | 3 Configuration | 4 | 5
3.2 Zone Management - Polygon Zone
38
Qb2
QbProtect
It is possible to create polygon zones for security and volume applications.
With this feature, users can define flexible zone shapes, which can be helpful in more complex scenarios where box shapes are not sufficient.
For instance, by using multiple sensors it is possible to protect non-rectangular objects like airplanes, cargo etc. or create volume zones around complex, free standing stockpiles.
This is done by defining a sequence of points (e.g. by the track of a walking person or arbitrarily defined points) which will form the ground area of the polygon. The ground area can be extruded by a certain height. This new zone covers both the object- and point based zones as well as volume zones. Polygon zones are created via API and can be visualized in the WebGUI.
Example security use case
Example volume use case
QbVolume
Confidential
3. Configuration
3.2 Zone Management - Exclusion Zone
1 | 2 | 3 Configuration | 4 | 5
39
Points detected inside the exclusion zone won’t trigger an intrusion in the security zone (exclusion of fore- and background points). For volume applications, the points inside the exclusion zone are not considered for volume calculations.
Qb2
QbProtect
QbVolume
Confidential
3. Configuration
3.2 Zone Management - Volume Zone
1 | 2 | 3 Configuration | 4 | 5
40
Define the shape of the environment that contains the volume of interest
This feature interrupts the volume calculation when an occupancy zones is occupied.
In this example, Occupancy Zone 1 or 2 can be chosen
Discretisation of the base area, whereby a higher resolution (smaller value) means a more accurate approximation of the actual volume.
Filled automatically when Tare function is executed (existing volume within the zone is subtracted from the actual measured value)
Define the shape of the environment that contains the volume of interest
This feature interrupts the volume calculation when an occupancy zones is occupied.
The angle of repose of a granular material is the steepest angle of inclination in relation to the horizontal plane at which the material can be heaped up without sagging.
When the estimated coverage is below the configured threshold, the state output will be disabled - useful to automatically disable the zone when the viewport to the zone area is blocked or the sensor temporarily failed.
Qb2
QbVolume
Confidential
3. Configuration
3.2 Zone Management - Volume Zone
1 | 2 | 3 Configuration | 4 | 5
41
Define the shape of the environment that contains the volume of interest
Configure height of cylinder which is attached to the bottom of the cone.
Qb2
QbVolume
Confidential
3. Configuration
3.2 Zone Management - Occupancy Zone
1 | 2 | 3 Configuration | 4 | 5
42
This feature inverts the logic of the zone. If enabled, the zone will output an intrusion whenever the zone is below the defined amount of points..
Minimum number of points required for the zone to be counted as occupied.
Qb2
QbProtect
QbVolume
Occupancy zones can be linked to security and volume zones. When they are occupied, the corresponding security or volume zone is disabled.
Confidential
3. Configuration
3.2 Zone Management - Traffic Lane Zone
1 | 2 | 3 Configuration | 4 | 5
43
Qb2
Throughout a traffic lane zone, an object’s position and velocity are tracked. At the end of the zone, an event is generated in the alam history, including the final complete point cloud of the vehicle. The goal is to monitor traffic in a certain lane, classify vehicle types and track its speed.
We can (currently) distinguish 4 different vehicle types: car, car with a trailer, van, truck. This is shown within the object label.
Users are required to specify the expected velocity of passing vehicles in this area since this serves as input parameter for the algorithm
Confidential
3. Configuration
3.3 Scan Pattern
1 | 2 | 3 Configuration | 4 | 5
44
All sensors
Confidential
3. Configuration
3.3 Scan Pattern
1 | 2 | 3 Configuration | 4 | 5
45
Currently running scan pattern
Create a new scan pattern via ‘+’
Former created scan patterns are saved
Scan pattern name
Open point cloud to view scan pattern changes live
Specifies the sensor’ laser energy for each laser pulse. The higher the laser energy, the further the detection capability (horizontal spacing is increased when the laser energy is increased)
The frame mode specifies the point cloud frame's composition and can be used to fine tune the LiDAR to specific use cases
If enabled, the point cloud has a denser region along the horizontal direction. The extent and density of this region can be set by the user.
UP: The laser will only be triggered during the ramp-up phase, this mode results in a more uniform motion deformation for fast objects
UP & DOWN: The laser will trigger during both up and down ramping phase, the point cloud frame is the combination of the two. Recommended only for high frame rates or scenes without fast moving objects
This feature defines the fraction of the vertical FoV that has a denser region: 0.2 equals 20% of the FoV.
This feature defines how dense the foveated region will be. A factor of 2 will increase the density by that factor compared to the rest of the FoV.
Tradeoff between density and image generation time
All sensors
Confidential
3. Configuration
Uniform vs. Classic Scan Pattern
3.3 Scan Pattern
1 | 2 | 3 Configuration | 4 | 5
46
Number of scanlines for a single frame
Horizontal angular spacing. Choose a lower value to have a denser point cloud
The classic scan pattern does not benefit uniformly from increasing the scanline count in a frame. The uniform scan pattern is an optimization that tries to provide an optimally homogeneous point cloud given the system’s constraints. To configure the scan pattern, the vertical field of view, the target frame rate and the pulse mode are used.
All sensors
Confidential
3. Configuration
3.4 Network Setup
1 | 2 | 3 Configuration | 4 | 5
47
Blickfeld offers multiple ways to connect the sensor to your network
Add NTP server for time synchronization. If nothing is added, the device uses one of the standard NTP servers.
Select the appropriate time zone, typically corresponding to the sensor's location.
Default time zone is UTC
All sensors
The WiFi feature is disabled by default.
Use the Blickfeld antenna and press the “Enable & reboot” button to activate the WiFi feature.
Confidential
3. Configuration
3.5 Push
1 | 2 | 3 Configuration | 4 | 5
48
Overview of previous data push formats
Select to enable/ disable/delete
Enter output format name
Enable/disable
Select the source stream data type: HEALTH, OBJECTS or STATES
Select output encoding: JSON, JSON_FLATTENED, or PROTOBUF
Select output target: Currently only Mqtt
Data endpoint
Option to create user authentication
MQTT Broker | MQTT Port
MQTT Client ID
All sensors
Confidential
3. Configuration
3.6 Flow
1 | 2 | 3 Configuration | 4 | 5
49
Sample Blickfeld Flow:
Low-code programming for event-driven applications
All sensors
Confidential
System
4. System
1 | 2 | 3 | 4 System | 5
4.1 Firmware
51
Overview of release history
Notifications for new releases / patch updates
Current Firmware
Except for the manual update a internet connection must be given.
!
All sensors
Hold to re-install
Click to view highlights of the release
Click to always update to the latest firmware automatically
Option to manually upload the firmware update
Click to update
Confidential
4. System
1 | 2 | 3 | 4 System | 5
4.1 Diagnostic
52
All sensors
Click to open detailed status display (right side)
Health states: OK
Option to download a complete diagnostics report
Health states: WARNING (yellow exclamation mark)
Option to run a self test and download the report
Confidential
4. System
4.1 Maintenance
1 | 2 | 3 | 4 System | 5
53
Sensor reboot option
Factory reset option
Export/Import options allow the user to export application-related configurations and import them on any other Blickfeld device
Assign a license to a Qb2 (e.g. QbProtect). Only Blickfeld can generate license keys.
All sensors
Confidential
4. System
4.1 Maintenance
1 | 2 | 3 | 4 System | 5
54
This demo shows how to use the export and import feature.
Goal: Export the configuration, manipulate the zones and later import the original configuration (exported earlier).
First, setup two zones in the scene. Then, navigate to System and open Maintenance on the left side. Press the Export button. The sensor's configuration is now downloaded and saved to your PC running the browser. Secondly, edit the scene according to your needs. To import the original configuration, navigate to Maintenance. Press Import and select the file. A list of Import options appears, select accordingly what you want to import (in this case Zone Management) and press Apply.
Finally, navigate back to Zone Management. The original zones are restored.
All sensors
Confidential
4. System
4.1 Maintenance
1 | 2 | 3 | 4 System | 5
55
If recovery mode was triggered due to repeated boot attempts, a boot firmware section will appear, displaying the currently installed firmware version. From here, the user can simply boot into the existing firmware without needing to upload or install a new version.
All sensors
Confidential
4. System
4.1 Maintenance
1 | 2 | 3 | 4 System | 5
56
Qb2
QbProtect
QbBasic
The Blickfeld Services button in the WebGUI maintenance tab now allows you to grant Blickfeld Support remote access to your device. This requires standard outbound HTTPS access.
With this, Blickfeld can get access to the sensors and connect remotely for support.
Confidential
Documentation
5. Documentation
1 | 2 | 3 | 4 | 5 Documentation
58
How to access
the sensor’s documentation:
All sensors
Confidential
5. Documentation
VMS & PSIM Integration for Security Projects
1 | 2 | 3 | 4 | 5 Documentation
59
QbProtect can be integrated into a growing number of Video Management Systems (VMS) and Physical Security Information Management Systems (PSIM), including:
In the documentation you can find detailed information on how to integrate Blickfeld LiDAR into your VMS and PSIM via ONVIF, and how to implement the RTSP-stream.
QbProtect
Qb2
Confidential
Contact us for support!
+49 89 230 69 35 83
Blickfeld GmbH
Barthstraße 14
80339 Munich
Germany