How can I use "virtual" cameras to demonstrate BVMS?
Demonstrating a video surveillance system typically requires a couple of cameras. However, when you only have a couple of cameras, the screen can look boring and empty. Did you know you can use the video streaming gateway to pull in any online JPEG picture as a camera into BVMS? This makes your demonstration more interesting! Additionally, you can set-up your own webserver and host customer JPEG images yourself. You can find a warehouse example below, fully based on JPEG based static images.
The attached document describes how to configure JPEG cameras.
My customers asks me to store the field of view of the cameras connected to BVMS. Is there an easy way to achieve this without opening every camera manually?
The embedded BVMS script engine makes this easy to achieve. The attached document explains how to achieve this and included an example script.
How does BVMS 10.0.1 (or newer) configure the firewall during the installation of the system?
The firewall configuration dialog is a fixed step in the setup process and will allow automatic configuration of all required firewall settings to run BVMS. The applied rules and settings can be found in the readable command script file "C:\Program Files\Bosch\VMS\bin\FirewallConfig.cmd".
The firewall rules that have been applied with the setup cannot be reverted and must be manually changed/removed if required.
Related Products: Configuration Manager 7.00 and above.
This article shows how to use recorded video in Configuration Manager in order to calibrate a camera and to configure a task.
Camera Calibration using Recorded Video
It is possible to calibrate camera using already recorded video in Configuration Manager 7.0. This feature is independent of the camera firmware version.
Configure a Video Analytics Task using Recorded Video
It is possible to configure a Video Analytics Task, using already recorded video in Configuration Manger 7.00 and above. This includes initial Task configuration, verification and then further performance analysis over the time and fine-tuning of the task parameters.
Note: There are multiple video analytics how-to videos in the following lists:
Calibration playlist: https://www.youtube.com/playlist?list=PLz97rFi-OzLfI2F4sP-ocX3BhX0rtJvgt
Video Analytic how-to playlist: https://www.youtube.com/playlist?list=PLz97rFi-OzLdPrzs-SR-g1oo4RkV9mvf5
Related Products: BVMS Operator Client
This article describes the initial steps one can take for troubleshooting BVMS display issues (during live view or playback). It also summarizes what initial information and logs are needed for support in order to start the issue investigation.
Check and eventually update the version of your Graphic Card driver.
During BVMS system tests there were documented cases of display issues related with out of date Graphic card divers. It is important that the Graphic Card driver of the client is up to date. Find the supported version of the Graphic Card driver in the corresponding to your BVMS version Release Notes (https://downloadstore.boschsecurity.com), in the section Hardware drivers.
Please prove the following information to support.
Is the issue camera type / FW dependent
Are all the devices in the system affected
Is the issue existent for all BVMS Operator Clients in the system
Is the issue existent for hardware decoders, for camera Web Interface or other display Clients
Is the recording, the playback or are both affected
Please provide Log files
BVMS ConfigCollector logs keeping the following conditions:
From the machine that shows the issue
Including VSDK logging – please follow the steps from the article How to collect Video SDK log files
VRM logs (in case VRM runs on the same machine like the BVMS MS, then BVMS ConfigCollector logs from the server)
Movie showing the display artefacts can be helpful
The password for the local admin and diagnostic port is set to the same starting with E2800 controller firmware 11.40.2 or later.
In case a user does not know his password any longer, it is not possible to reset and re-configure this password by using the diagnostic port (serial port on the rear side near the uplink ports of the controller). With controller firmware older than 11.40.2 it was possible to reset the Administrator Password needed for configuration. But older NetApp controller firmware cannot and must not be used any longer due to other technical reasons. When accessing the Management Port IP to enter the WEB GUI of the NetApp E2800 system for configuraiton or support data collection, the Administrator Password is required. For the time being this is reported to NetApp to work out a solution for all NetApp customers and BOSCH.
Solution and Procedure:
Right now, BOSCH and our customers have no documented instruciton or procedure to remove / reset the password. We are working ont hat with high preassure and awareness. We kindly ask all customers requiring access to the configuraiton but having not the Administrator Password on hand for configuraiton, to reach out to BOSCH support and ask to sent the requewst immediately up to a Levle 3 Ticket to the Gatekeeper team at BOSCH BT-SC/ETP-MKP2 or BT-VS Support in the BU.
The RAID combines two or more physical drives into a logical unit presented as a single hard drive to the operating system. There are currently six basic RAID levels: RAID 0, RAID 1, RAID 0+1, RAID 1+0, RAID 3, RAID 4, RAID 5 and RAID 6.
The scope of this article is to provide basic information for the levels RAID 5 and RAID 6 and to compare them from point of view of performance and security.
Hot spare is a drive that acts as a stand by drive in RAID 1, RAID 5 or RAID 6 volume. It is fully functional drive that contains no data and is not used during normal operation. If a drive from the volume fails, the controller reconstructs the data from the failed drive to the hot spare drive.
A RAID 5 array is designed to protect against the failure of a single disk within the array. Because of the way that RAID 5 works, the total capacity of one disk is lost to overhead. If, for example, a RAID 5 array contained five 10TB disks, then the array’s usable capacity would be 40TB.
A RAID 5 (with Hot Spare disk) array can be configured to treat one of the disks as a hot spare. Then one of the disks is reserved as a replacement in the event that a disk fails. For the above example with five 10TB disks, this would decrease the example array’s usable capacity to 30TB.
A RAID 6 array is designed to protect against two simultaneous disk failures. However, the price for this extra protection is that two disks' worth of capacity is lost to overhead. As such, a RAID 6 array made up of five 10TB disks would have a usable capacity of 30TB because 20 TB is lost to overhead.
The performance during Normal Operation is measured in IOPS (Input/output operations per second) and as a sum for all the disks (excluding the Hot Spares and decreased for writing parity data) in the array. As a rule of the thumb, the higher the overhead associated with writing parity data (in the above example RAID 5 with Hot Spare causes the same overhead like RAID 6) the lower the IOPS.
The reason for implementing RAID arrays is to secure the data. The level of protection does not directly correlate with the overhead. From the above example both RAID 5 with Hot Spare and RAID 6 have same capacity, but offer different level of protection. In case of failure of RAID 5 array with Hot Spare, the Hot Spare is activated and the rebuild process start immediately. The system can recover from a single disk failure and during the recovery, process is vulnerable to second disk failure. Therefore, RAID 5 and RAID 5 with Hot Spare disk offer the same level of protection – single disk failure. In contrast, if a disk fails at RAID 6 array, the recovery will start only after the faulty disk is replaced manually. However, if during the recovery process second disk fails, the RAID 6 array will stay functional.
Time is everything: meetings, public transportation, religion, transactions: the whole world is working because the concept of “time” exists. Within a security (or any other) system this is not different: recording schedules, logging, authorizations, encryption keys, timelines, all of these concepts can exist because of time. As a result, time can either make or break a system: problems can appear only due to a time difference of a couple of seconds between two system components.
The attached document describes how time services can be configured in a BVMS environment.
When working with previous versions of BVMS, remote connectivity was cumbersome due to the amount of port mapping that needed to be configured. BVMS 7.5 provides a new method of remote connectivity utilizing Secure Shell (SSH) Tunnelling.
The attached document (attachments can be found on the bottom of the page) describes the set-up and configuration of the SSH functionality in BVMS.
In BVMS 10.1 we have added the capability for a management server (or DIVAR IP) to act as a bridge between a corporate network and a video network. We have described the configuration of this scenario in the BVMS 10.1 - Unteaming network interface cards document.
please find the release information about Configuration Manager 7.00.0111.
Configuration Manager 7.0 introduces a complete rework of the user interface, following the latest Bosch application style guide, with many improvements in readability, compactness and improved navigation for a better user experience.
Look-and-feel according to latest Bosch style guide, improvements on readability of form elements.
Screen space optimization due to higher density of presented information, optionally vertical navigation bar.
Scaling invariant user controls enable smooth support for high DPI screens.
Avoiding horizontal scrolling by adaptive column reduction.
New easy to use filters, supporting “Google”-like free text matching on various identifiers as well as down into device properties.
VCA pages with new sub-navigation, larger video presentation for easier task setup, improved calibration and Camera Trainer pages, in-field editing, object filter page, and providing tooltips and direct links to help pages.
Strong password demand during first start of the program. Working without password prompts extra warning pop-up and requires specific user action.
Certificate creation now allows including usage. This enables fully automated batch certificate creation for larger sets of devices. The creation dialog shows the progress of key creation.
Support for new AUTODOME IP 7000i and MIC IP 7100i with firmware 7.52, introducing changes and enhancements on picture settings and pre-position settings pages.
Setting an alternate home position is now possible for applicable moving cameras.
Support for new DINION and FLEXIDOME IP 3000i series with firmware 7.51.
An RCP+ message and/or a SNMP trap from cameras, if time sync fails, can be configured.
Assignment option for CHAP password on DSA E series storages added. Password must be from 12 to 16 characters long.
Playback permission is configurable for IP Matrix since decoder firmware 9.60.
Support for Bosch Video Client (BVC) and BVIP Lite Suite is excluded.
The configuration backup of the Configuration Repository is now referring to the MAC address of a device instead of the IP address.
Network scan is now also possible for IPv6 networks.
Context menu and some configuration pages cleaned-up for decoders.
Improved feedback on firmware upload status and errors.
The character ‘+’ is not allowed anymore for camera passwords since it is also blocked in cameras from firmware 7.50 onwards.
The image posting tab is moved from ‘Network’ to ‘Recording’, and a link to configure accounts was added.
Secure crypto-coprocessor version is now displayed on camera’s compatibility tab.
Configuration Manager 7.0 has excluded support for Bosch Video Client and BVIP Lite Suite. Installing it over an existing installation of a previous version will encrypt the database with strong encryption and thus render it unusable for the older software.
Please refer to the release notes for details:
The software package will be loaded into ST4 the next days and uploaded to the product catalogue with the next sync.
It has already been uploaded to DownloadStore as well.
The attached manual provides information for Mobile Video Service (MVS) within Bosch Video Management System. You can find:
- how to configure the router and Internet Information Service (IIS)
- how to add MVS to BVMS
- user guide
- some troubleshooting tips
The attached document describes the different components that Bosch Video Management System offers to to establish a connection between Bosch Video Management System and a 3rd party management system. This description helps you in writing your own commands for controlling Bosch VMS from inside your management system.