Security: Video

This article lists the scenarios in which technical support normally request dump file from a BVMS system.

Have a look at this article and learn how to fix the Add Scriptlet button which does not become active. It stays grayed out. Same happens with ClientScript and ServerScript.

This article explains step by step how to add a DIVAR Hybrid 5000 in BVMS Viewer and see Live image of cameras connected to the DIVAR.

License expansions missing after upgrade to BVMS 11 in Remote Portal. Only 1 x MBV-XCHANPLU license activated instead of 16 x MBV-XCHANPLU. What to do?

This article explains how to configure an alarm communication between BVMS and Gmail e-mail address.

Applicable when using the following software application. Bosch Video Management System (BVMS) version 10.0.1 and above. Bosch Configuration Manager version 7.0 and above. Live page on the web browser for IP camera operating on firmware version 7.70.0126 and above.

This article contains a simplified and generalized example, that could be helpful in building a particular tailored script related to implementation of event receiver in BVMS SDK scriplet.

The digital monitor wall functionality was removed since BVMS v11.0, and this is also stated in the release notes.

If you add a decoder that has 2 monitors connected, you must display the Edit Decoder dialog box of the decoder and update the device capabilities of this decoder. For each monitor add a further monitor wall.

Related Products: BVMS SDK, BVMS    Overview: BVMS Scriptlets can be debugged via logging to a logger file or messaging to the Operator workstation. This article describes how to enable BVMS Scriplet logging. You can log to the Server Script log or the Client Script log. Logs are default send to C:\ProgramData\Bosch\VMS\Log   1.Creating Log files ClientScriptLogger – automatically created Creates file “ClientScriptLog.txt” ServerScriptLogger - automatically created  Creates file “ServerScriptLog.txt”   2.Log information to the log files There are 3 methods to log information: Log Info Log Error Log Debug   Examples: [Scriptlet("59c4d66e-9395-4dcc-8d27-90dc2b7a00c4")] public void DemoLogger() { //use refence:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 MessageBox.Show("Hello World"); Logger.Info("Hello World script started"); Logger.Error("Hello World script started"); Logger.Debug("Hello World script started"); // Not writing to ClientScriptLog.txt ! }   3.Logging Location - C:\ProgramData\Bosch\VMS\Log. The logs are automatically collected by the BVMS Configuration Collection Tool. 4.Changing the location of the BVMS Scriplet Logging.   Server Scripts : Logging Directory can be found in the file: C:\Program Files (x86)\Bosch\VMS\AppData\Server\CentralServer\BvmsLogCfg.xml and is defined by the ServerScriptLogAppender path: Default: </appender> <appender name="ServerScriptLogAppender" type="Bosch.Vms.Shared.Logging.Imp.RollingFileAppender, Bosch.Vms.Shared.Logging.Imp"> <file value="%CommonApplicationData%\\Bosch\\VMS\\Log\\ServerScriptLog.txt"/>   Client Scripts : Logging Directory can be found in the file: C:\Program Files (x86)\Bosch\VMS\AppData\Client\OpClient\ApplicationWiring\Nvr\LogCfg.xml and is defined by the ClientScriptLogAppender path: Default: </appender> <appender name=“ClientScriptLogAppender" type="Bosch.Vms.Shared.Logging.Imp.RollingFileAppender, Bosch.Vms.Shared.Logging.Imp"> <file value="%CommonApplicationData%\\Bosch\\VMS\\Log\\ClientScriptLog.txt"/>

This article explains step by step how to play exported recording files from VRM eXporter Wizard in BVMS Export Player.

This article shows step by step how to call a FLEXIDOME IP panoramic 5000 camera preposition in Operator Client. 

This article explains why the Live view shows ‘Authentication failed’ in Video Security App.

This article presents what symptoms appear in BVMS Operator Client if Time synchronization is wrongly set. Also provides some recommendations about what to do to avoid this symptoms. 

This articles explains what does the User Name column indicate in the BVMS Operator Client LogBook.

This article explains how to enable and collect Video SDK Logs for VSDK based applications.

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, BVMS    Overview: Analyzing BVMS systems with SDK components is a challenging task, because the functionality and the runtime behavior of those systems are harder to determine than for a BVMS systems without SDK functionality. In order to troubleshoot BVMS systems with SDK components 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? How often are client scripts triggered? How often are scripts triggered by BVMS event?   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 the Scriplet and/or Log files The optimal approach is to provide both the scriplet and logging. ClientScript logfiles: can be found in the ConfigCollection of Operator Client machines. ServerScript logfiles: can be found in the ConfigColletion of Management Server machines.   Make sure that logging is implemented in the script and that logging is activated in the configuration.  

Check this article and find out how you can avoid displaying black image in Operator Client BVMS v11.0

Can I display more than 1 camera on a single Monitor of Decoder VJD-7513 in BVMS 11.0 when an alarm is triggered?   System Overview: BVMS 11 1 monitor connected to 1 x VJD-7513 that is part of a Monitor Group The monitor has a layout consisting of several image panes Desired status: when an alarm is triggered → pop up the image of the 4 cameras on the same decoder monitor

This article contains a step-by-step guide which explains how you can do the setup for the camera's live view image pane to be displayed in full screen in the Operator Client if a motion alarm is triggered on that camera,