In order to quickly offer a technical solution or to provide a professional advice for the next analysis steps, the technical support specialists need to get some general and basic information.
Ticket content should always be in English and provided in a well summarized and structured way in order to be able to provide a quick and appropriate feedback. Not following the guideline will impact the processing time of the ticket.
Related Products: BVMS SDK, Cameo SDK, BVMS
Analyzing BVMS systems interaction with BVMS SDK based application is a challenging task. One needs to determine if the issue is based on wrong implementation of the BVMS SDK functionality, wrong programming practices, functionality and runtime behavior of BVMS system with SDK functionality or BVMS SDK issues. In order to troubleshoot BVMS SDK or Cameo SDK application support needs the following information and logging.
Please prove the following information to support:
Symptom specific Information
How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status?
BVMS stand alone or appliance
Detailed description of the expected behavior of the SDK functionality.
Detailed description of the actual behavior of the SDK functionality.
What type is the standalone SDK application (based on ClientSDK, ServerSDK, or CameoSDK) and on which machine is it running?
Are there additionally client scripts, server scripts or workstation startup scripts?
Do SDK components interact with remote Operator Clients?
Do SDK components interact with the Operator Client UI?
Do SDK components control devices?
Do SDK components link to 3rdParty devices or applications?
Which shared resources are accessed by SDK actions? (Dome cameras, AMG, Operator Client UI)
Do SDK components interact with an unreliable environment? (Unstable network, offline devices, offline PCs, etc.)
Do SDK components properly handle offline situations? (offline devices, configuration changes, etc.)
Please provide source code and/or Log files
The optimal approach is to provide both source code and logging for the problematic BVMS SDK application. If it is not possible to provide the code, we will start the troubleshooting process based only on the logging.
Provide a little sample application that illustrates the BVMS SDK issue and list the reproduction steps.
Add log outputs to the SDK application functionality. The logs should illustrate which BVMS SDK functionality was called at which time. Provide the logs to support.
List of Typical Mistakes that are often seen when troubleshooting BVMS / Cameo SDK based applications
Use of Thread. Sleep() in event handlers - Consequence: loss of events in customer SDK application.
Implementations that are not thread safe - Consequence: unexpected SDK application effects
Unintentional introduction of multithreading issues by using timers - Consequence: unexpected SDK application effects
Application without "speed control" - Consequence: operator overload in case of high event frequency
Lack of configuration change handling - Consequence: data inconsistencies in SDK application (access to no longer existing devices)
Lack of traces/logging in SDK code - Consequence: not detected malfunctions and troubleshooting difficulties
Lack of error tolerance in SDK code - Consequence: unhandled exceptions in SDK application / script
Lack of exception handling - Consequence: SDK application crashes
If you have configured an out of the box system and once the configuration was done you wasn’t able to access the BVRAdmin account, this article will help you to find a solution.
Access to BVRAdmin account is required to perform administrative tasks on the operating system.
This requires the following steps:
In this section you can find details on what information is required during the troubleshooting process to successfully identify a unit in terms of model number, firmware version and unique identifiers. What is also very important always for the troubleshooting is the DIVAR Service log. In addition to that, in some situations network captures from the DIVAR may also be required.
What to do when MIC IP camera is unable to perform the Object Classification in IVA detection?
Based on examples of target objects and non-target objects, the Camera Trainer program uses machine learning to allow the user to define objects of interest and generate detectors for them.
Using Configuration Manager, you can configure the Camera Trainer program using both live video as well as recordings available through your MIC IP cameras.
The camera also includes the latest release of Intelligent Video Analytics application for use on prepositions. Designed for mission-critical applications, the video analytics can reliably detect, track, and analyze moving objects while suppressing unwanted alarms from spurious sources in the image, even in harsh weather conditions. Advanced tasks like multiple line crossing, loitering, idle / removed object detection, crowd density estimation, occupancy and people counting are available for live alarming and forensic search. Object filters based on size, speed, direction, aspect ratio, and color can be defined.
In order to perform Object Classification correctly, please make sure that you have correctly:
set the correct Orientation
Save all the pre-positions again if the orientation stetting is changed
calibrated the camera
A simplified calibration mode reduces installation time significantly because you only need to enter the installation height once for each camera, independent of pre-positions.
After the camera is calibrated, the analytics engine can automatically classify objects as upright person, car, bike, or truck.)
enabled 3D tracking
set it up the tasks and followed the VCA manual.
Please see an overview of object classification in the following article:
How to set up object classification with video analytics
According to the BVMS 11. Release notes > 2.2. Removed functionality chapter > The digital monitor wall functionality has been removed.
This removal has impact on the BVMS Viewer → Decoders are not supported anymore in BVMS Viewer starting with version 11.0
Other devices and functions that have been removed to ensure software security:
Map migration (removed Autodesk design review installation)
Note: The Monitor Group functionality is still available in BVMS Professional/ Plus/ Lite.
With the DSA E2800 Bosch introduced Multipathing. It is a fault-tolerance technique that defines more than one physical path between the camera and its iSCSI storage devices through redundant network connections.
When using this feature, recording of video data and replaying video data is possible even in case of an iSCSI controller failure. To ensure also that outages of infrastructure equipment (e.g. Switch) could be covered, we recommend following Interconnection.
This article describes the easiest method for adding Expansion shelves to a Base unit DSA E-Series E2600, E2700 or E2800.
This article also applies when:
The amount of storage is overloaded and you need additional storage after fully populating the base shelf.
1. Configuration Manager
2. Configuration Client which is included with BVMS
3. Santricity Software
The purpose of this article is to provide a step by step guide about how to perform backup and recovery procedures of the VRM data base in the DIVAR IP 2000 EZ Recording Appliance.
Backing Up the Working Configuration:
1.To backup the working configuration of a DIVAR IP 2000 Recording Appliance, open the Appliance's "Dashboard":
2. From the Dashboard select the "Configuration" tab in the top right hand portion of your browse:
If one of DIVARs IP 5000 AIO is selected on a user profile, the Operator Client opens the site and works fine. One message is displayed when two or more DIVARs are added into the same Enterprise system.
If you already have a DIP 5000 AIO into your Enterprise system and you want to add additional units but you receive the following message, you can solve this by using the steps below:
"Server of configuration database is already in the server list. Remove either the server that is twice in the list or make sure that the configuration database is not cloned between servers."
If you have the option "Extended (security)/configuration mode" active on a VIDEOJET decoder 7000 (VJD-7513) in Configuration Manager, then no video image will be shown and the BOSCH logo will be displayed at the cameo of the monitor output of the decoder.
This is as designed in Configuration Manager, and this mode is to give you the opportunity to enable the SSD Encryption and to disable the USB ports.
Once you are finished changing the extended security features, you must uncheck the check box and the decoder will go back to normal functioning.
The BVMS Logbook database can be moved to another SQL Server.
This article describes the steps that are necessary to migrate the database and describes how to confirm if the migration was successful.
BVMS is using Microsoft SQL Server Express to store its logbook. Based on the information provided by Microsoft (Compare SQL Server 2017 editions), SQL Server Express is limited to a 10GB database size.
This could be insufficient for larger installations or installations that require a very long logbook retention time. Additionally, some organizations have a dedicated SQL server environment which should be utilized by all applications. The BVMS Logbook database can be moved to another SQL Server. This guide describes the steps that are necessary to migrate the database and describes how to confirm if the migration was successful.