Security: Video

This only happens when you perform the export in BVMS Operator Client.

This is the old way as for Project Assistant versions < 1.3.

This article provides an overview of object classification, describes how to configure it and what the limitations are.

This article explains how you can change the IP Matrix Passcode PIN when using Configuration Manager version lower than 7.50 & VIDEOJET decoder 7000 (VJD-7513) FW version lower than 10.22.

Use the keyboard connection on the back of the unit to connect a Bosch Intuikey keyboard using one of the following methods.

This camera does not have the auto-focus functionality in the same sense as Autodome / Mic cameras.

The 95 W midspan is a high-power PoH (Power Over HDBase T) device that provides data and power between an Ethernet switch and an IP camera.

Use the CTFID tool (Configuration Tool for Imaging Devices) for configuring the camera. Find in this article the download link and the release note.

Follow this article to avoid getting the message: “Changing orientation is not possible because of the mounted illuminators”.

Is DIVAR IP 6000 R1 compatible with VRM v.3.83.0021 (64-bit) and BVMS Viewer 10.1?

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  Overview: 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   Problem Description SMA validity 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.   SDK Components 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?   SDK Interactions 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?   Environment 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.)    Logging Information   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. Source Code Provide a little sample application that illustrates the BVMS SDK issue and list the reproduction steps. Logfiles 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 cleaning the bubble is required, use the following procedures and comply with all the warnings listed in this article.

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 recommendation could be applied if the storage is overloaded, as there are several Onvif cameras running through it.

The method from this article shows you how to generate an updated certificate for Bosch IP Camera's and VRM Servers

Find out from this article how to pass a special connection string to request a multicast stream via RTSP from a BOSCH IP camera or IP encoder.

MTU stands for "Maximum Transmission Unit." MSS stands for "Maximum Segment Size"

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) SMS gateway Dibos/ BRS 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.   Article requirements: 1. Configuration Manager 2. Configuration Client which is included with BVMS 3. Santricity Software   Step-by-step guide