Important Cookie Information

This website uses absolutely necessary cookies. If you consent to the use of convenience cookies, please click “Yes, I agree.” By clicking on “Privacy Settings.” you can change this setting at any time and withdraw your given consent.
Icon downsee more
You can find detailled information in
our Privacy PolicyIcon forward-rightIcon upsee less

Privacy Settings

Decide which cookies you want to allow.You can change these settings at any time. However, this can result in some functions no longer being available. For information on deleting the cookies, please consult your browser’s help function.

Decide which cookies you want to allow.
Icon downread more
You can change these settings at any time. However, this can result in some functions no longer being available. For information on deleting the cookies, please consult your browser’s help function.
Icon upread less

Related Products: Bosch Video Analytics for Firmware 6.40 and above
This article contains how to Videos that explain what calibration is, why and in which cases is it necessary to calibrate the camera and how to calibrate and verify the calibration.
Camera Calibration Introduction
This Video should help you to understand, what calibration means, why and when to calibrate the cameras.
Camera Calibration Paramenters
Understanding the calibration parameters.
DINION and FLEXIDOME camera calibration specifics
Specific calibration methods based on camera sensors for DINION and FLEXIDOME camera family.
Bosch Security - Video Analytics - Moving cameras calibration specifics
Specific calibration methods based on camera sensors, moving camera family.
Panoramic cameras calibration specifics
Specific calibration methods based on camera sensors, panoramic camera family.
Manual calibration, sketch calibration
Calibrate the camera using the measured values or with the help of calibration elements. Verify if the camera perspective about the scene is accurate.
Calibration verify function
How to verify if the camera perspective about the scene is accurate.
... View more

In December 2017 information about two vulnerabilities in modern processors were published. These exploits are often referred to as Meltdown and Spectre. Due to the nature of the flaw, many processors(AMD, ARM, Intel, etc.) are considered vulnerable. In order to use the exploit, an attacker needs to execute malicious code on the target system. It is thus generally advised to protect systems from unauthorized access (e.g. by using a strong password policy). BOSCH IP Cameras and BOSCH Encoders are based on Common Product Platform (CPP) designs. Each CPP uses a specific System-on-Chip (SOC), or a family of SoC’s, which inherit various CPU cores. Some of them include ARM cores, which are considered vulnerable. We therefore have analyzed our Common Product Platforms if they are affected, with the result: • Our Common Product Platforms CPP-ENC, CPP3 and CPP4 are not affected by the vulnerabilities. • The processors used in the SoC’s of our Common Product Platforms CPP6, CPP7 and CPP7.3 are affected. As we do not allow 3rd party code being installed or executed on our cameras, successful exploitation is considered not possible with Meltdown or Spectre. In short, our IP cameras and encoders are not vulnerable to Meltdown or Spectre exploitations. In general we recommend to always keep your device Firmware up to date.
... View more

In the Manual of the VideoJet decoder 8000 at Point 6.1: Setting up the decoder with Configuration Manager Before you can operate the unit within your network, it must have a valid IP address for your network and a compatible subnet mask. Notice! As a default DHCP is enabled in the unit’s network settings. With an active DHCP server in the network you must know the IP address assigned by the DHCP server to operate the unit. The following default address is preset at the factory: 192.168.0.1 The correct inital IP address is: 192.168.0.200
... View more

Some devices that demand 60W or less are not powered by the NPD-9501A Midspan
The Midspan was released before the standards on mega poe were crystallized into accepted definitions at the IEEE standardization body. This device specifically targets to support power application to Bosch products that could not be served by lower capacity power source equipment.
Using power devices that are not listed for this product in the datasheet migth result in power failure.
Currently known
NPD-9501 Midspan will not work with UHO-PoE-10 Housing
Solution
For products demanding 60W or less advise to use NPD-6001B Midspan.
... View more

Possible Communication Issue between BVMS 8.0 Central Server and Video Recording Manager (VRM) 3.70 and 3.71 with BVMS 8.0 installed on different Servers.
Problem Identification
Communication can get interrupted and configuraiton might fail if the below desribed actions are not performed. If your system is affected or not is described here as follows:
There can be authentication issues between the BVMS Central Server and the Video Recording Manager in case they are installed on different Servers.
It is possible to see reports at the BVMS 8.x system alarms that VRM reports wrong version
Please check in the VRM debug logging if the following logline indications can be found
CONFIG;DEBUG;SENDING XPATH /SYSTEM/DEVICES/DEVICE as well as HAS NO CONFIGURED NODE, SET TO CONFIGURED
CONFIG;INTERNAL;/SYSTEM/DEVICES CHANGED IN CONFIG. DEVICEID= [DEVICE IP]\0;SYSINFO;INTERNAL;LINE 1 HAS NO CONFIGURED NODE, SET TO CONFIGURED
Solution
In general please keep in mind, that it is strongly recommended to use VRM 3.71.0029 with BVMS 8.0. Do not use any older VRM version like 03.71.0022. The 03.71.0029 and Releaseletter is available at the BOSCH DownloadStore (status update 2018-10-26). https://downloadstore.boschsecurity.com/FILES/Setup_VRM_03.71.0029_win32.zip Release Letter: https://downloadstore.boschsecurity.com/FILES/Bosch_Releaseletter_VRM_3.71.0029.pdf
At the VRM system / server, please check and ensure that the following Microsoft software packages are pre-installed:
.NET framework 4.6.2 or higher
Redistributables for Visual Studio 2015
In case one component is missing, please perform the following steps:
Download the missing Microsoft components. Note: When using BVMS 8.0 the VRM is typically a 32-Bit VRM software. Therefore the 32-Bit Microsoft packages are needed. Component that was seen as missing is the >> “Visual C++ Redistributable for Visual Studio 2015” https://www.microsoft.com/en-US/download/details.aspx?id=4814 Please choose the 32-Bit version of that when using with 32-Bit VRM and the >> .NET framework 4.6.2 or higher (NDP462-KB3151800-x86-x64-AllOS-ENU.exe) https://www.microsoft.com/en-US/download/details.aspx?id=53344
Stop the VRM (rms.exe) service in Windows services
Install those components with Administrator rights at the VRM server Reboot the server after installation of the Microsoft components
Check if the VRM service is running and if needed Re-Start the VRM (rms.exe) service
Check that the combination of messages are not longer seen in the VRM debug logging
The VRM package is enhanced and useres should no longer run into this issue with VRM 3.81 and newer versions. Please be aware that BVMS releases are tested with certain VRM verions. This still can offer to install a newer VRM than originally rolled-out in the BVMS overall installer. For all VRM versions 3.7x and below 3.81 it is needed to add this packages.
... View more