Security: Video

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 customer explains step by step what can be done when DIVAR IP 7000 server stopped recording suddenly and the Video Recording Manager service is not running.

You can call desired pre-positions (PTZ) of Bosch IP cameras by using OSRD protocol or BiCom protocol. Please check this aticle to find some examples and detailed explanation.

There is an issue with VRM versions lower than 4.0 where the retention time for recordings from VSG instances is set incorrectly. There are a few things that usually cause the recording mode to be set incorrectly. Find out more details from this article!

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.  

This article provides an answer if the  an OS upgrade to Win2016 can be performed on old DIP 3000, DIP 6000 or 7000 R1.

BVMS Version 10.0: please note that the export mechanisms provided in the BVMS Configuration Client might not export the user-data. Check this article for more details!

Have a look in this article to learn how you can add ONVIF cameras to Configuration Manager through VSG managed by VRM.

Have a look at this article and learn what you should check when your cameras do not record and when going to VSG and recording, it stands that 'ANR not configured' or 'No more blocks available'

Take a look at this article and learn how you can wire the camera alarm input of DINION IP starlight 6000i

When the camera operates in automatic Night-Mode and the switching interval is too fast the camera built in protection mechanism will intervene to prevent premature wear of the mechanical IR-Cut filter.

This article explains how to find the source (details of the workstation) and credentials that are used to attempt to login into BVMS (when the attempt has failed)

Follow this step-by-step guide and learn how to configure RAID 5 on your DIVAR IP AIO 7000 GEN3.

This article gives you the solution to fix the behavior when the recording doesn't work for VG4 AutoDome camera and when the Bosch logo is displayed in the cameo

Remote VCA configuration through the camera's device page (website) now can be performed with Bosch Configuration Manager version 7.60 and later.

When smoke or fire is been detected, AVIOTEC will sent a Smoke/Fire event to the Alarm Management and at the same time trigger it’s output.  Using this output status, we are able to trigger the Alarm Management.

Check this article and find out what the Start Manual Recording button of VRM Camera Cameo does in BVMS Operator Client

This article describes how you can upgrade a BVMS license to a higher version via Bosch Remote Portal. ( eg. from BVMS 11.0  to BVMS 11.1.x )

If the Host Type was set to other value than “Factory Default” for DSA E2800 and you want to integrate it with BVMS, the targets will most likely not be scannable and there will be no recordings at all.