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
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.
This article lists how to configure ANR feature in BVMS and how correctly to set up iSCSI and direct replay.
Configuration of ANR in BVMS system
Insert SD card into camera and power it on.
In Configuration Client, select Devices page.
Device password and CHAP password. There are two possible configuration set ups - to configure password for both device and iSCSI connection or to leave both without password. Choose and configure one of them (3.1 or 3..2).
3.1. Set device user password and CHAP password
3.2. No CHAP password for ANR
Note: Mixing the parameters between the two options 3.1 and 3.2 will lead to issues in direct replay from SD card.
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.
BVMS v10.1 and BVMS v11.0 come with a checkbox where you can logon to the Operator Client with Windows Credentials.
If you want to use this function, you need to set up the BVMS Configuration Client and browse the AD users-groups. Then, the users can sign in to Operator Client with their Windows-Credentials.
BVMS is a data-driven video management system that supports predictive solutions by establishing a decision center delivering actionable insights to customers.
The latest version offers a map-based tracking assistant and improved geographical awareness with online maps. Read on to learn how to configure the map-based tracking assistant.
The map-based tracking assistant requires a license. Before beginning, check the license in Configuration Client by accessing the License Inspector, which is found under the Tools menu.
The value of the Online map and Map-based tracking assistant licenses must list "True" in the License Limit column.
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.