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
In order to start to analyze and optimize Video Analytics settings for particular customer set up, we need initial information and export of example video.
This article describes the absolute minimum information we need in order to start analyzing and optimizing Video Analytics performance.
Video Analytics (VA) task performance optimization
Please provide the following details:
Symptom specific Information
Describe the expected result from the VA task.
It is important to get detailed information of the results VA should provide.
Define what is the customer’s priority:
High sensitivity - miss as few true alarms as possible, but increases the likelihood of more false alarms!
High precision – have less false alarms, but accept the risk to miss true alarm!
Using VA is always based on balancing between sensitivity and precision. It is not always possible to get high sensitivity and high precision at the same time.
Provide an export of recorded video that should contain:
for basic understanding of meta data, please read the latest Software Manual Video Content Analytics
for instructions about doing a video export with meta data, please read the article: How to export video including meta data (Export video including Video Analytics meta data).
Couple of examples of false alarms (in case false alarms are the issue)
Provide the number of false alarms per time span (per day, per week, etc.)
What would be acceptable as a number of false alarms per time span
Couple of examples of situation that should have caused alarm, but VA did not generate the alarm as expected.
In this case please provide the time stamp of the event and short description
Screenshot from the Camera Calibration Verification page - only in case calibration is needed for the particular VA functionality
access the Calibration Verification page of the camera (via the Configuration Manager or Web Interface)
provide screenshot from the verification of each parameter used for camera calibration
Note: For more information on Camera Calibration and Calibration Verification, please check:
How To calibrate camera for Video Analytics?
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.
This article provides a step-by-step guide about how you can disable UPnP of Bosch IP cameras & multicast scan from Configuration Manager.
One of the reason why UPnP (Universal Plug and Play) is enabled in our devices is because ONVIF uses this to scan the ONVIF device in the network.