During the troubleshooting process, the Central Technical Support team often needs to run several different loggers to gain a more complete understanding of the problem.
You can use custom console traces to regroup and run different loggers that are not combined in the default Server Admin list.
To create and run custom console traces for Security Center, follow the steps from this article.
This document is specifically for DIP-73xx as it's the only DIP with Software Center.
The document details how to upgrade all the way from BVMS 10.1 with Software Center and to BVMS 12.1 with System Manager 2.3
In the Logbook, you can search for particular events, alarms, devices, and strings of events. You have the possibility to save the BVMS Operator Client alarm logbook, before accepting and clearing it.
Regular BVMS 12.1 installer will not run on any DIVAR IP all-in-one platform. The upgrade shall be performed via DIVAR IP System Manager application. Usually, we recommend to upgrade BVMS in steps. Each version should not be more than ~two years apart. This prevents potential issues in the upgrade process.
The internal logs are directly located in the folder C:\ProgramData\Bosch\VMS\Log and then are named like "CameoSdkLog_Instance1.txt.0". To activate the Cameo SDK logging, the "Init" button has to be pressed after setting the checkbox "Internal logging" and entering an instance name - then logging is activated with the given instance name (e.g. "Instance1").
In this scenario, an alarm button is connected to the Adam unit and when this input is activated (close or open), a full screen camera image shows on the display. The display is always logged in the Operator Client for live camera view on the DIVAR IP 7000 AIO.
This document is valid for all VideoView+ versions. Only the release notes of the latest VideoView+ version are fully updated and contain updates for earlier versions as well.
