Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    Thursday
    Short intro and related topics: This article will review the settings required to configure Windows as a NTP time server. Note: If you are running VRM and have the Time Server enabled, you must disable the Time Server before performing the following. Article requirements: Windows Server 2016/ Windows 10
    View full article
    Thursday
    It is possible to add ONVIF compliant cameras to Bosch Video Management System as live only devices or as VSG devices (then the cameras will also record). This article explains how to add an ONVIF camera as VSG device in full Bosch Video Management System (BVMS 10.1). We recommend using Bosch Workstations and Servers. They are fully tested and optimized for Bosch Video Management System.   Article requirements: BVMS installed ONVIF camera. Please refer to BVMS - ONVIF Device compatibility for additional information. PC/ Server/ Workstation
    View full article
    Thursday
    Question   Which is the VSG preparation to support ONVIF Profile T in BVMS 10.0?   Answer   Additionally to ONVIF profile S, BVMS 10.0 supports ONVIF profile T. Profile S concentrates on basic video streaming and configuration Profile T focuses on advanced video streaming like use of H.264, H265 encoding formats, HTTPS streaming and event definition is more precise there Profile T functionality is only supported for devices that are added over VSG For conditional and optional features please refer to the BVMS - ONVIF Device compatibility article. Functionalities available for all devices added over VSG (BVMS 10.0): The ONVIF relays are scanned automatically Relays can be added to the Logical Tree by drag& drop and triggered from there Thee relay status is automatically updated and signaled with an appropriate icon in Operator Client Status and triggering is possible over BVMS scripts Once ONVIF camera is added to VSG, its capabilities are automatically scanned In the “Add ONVIF encoder” dialog it was added a new device properties entry that shows weather AUX is supported by device. The AUX commands are sent to camera vis VSG and can be triggered for an ONVIF device on alarm. Note: most of the ONVIF cameras do not support all in Configuration Client available events   ONVIF vendor mapping:   ONVIF camera connection to VSG and BVMS Operator Client: Live video from ONVIF camera to VSG or Operator Client can be secured with a Secure connection check box in the Add/ Edit ONVIF Encoder dialog. The secure connection is not chosen by default. (Default HTTPS port is 443) If the live video does not have to be secured, it is possible to choose what protocol should be used: TCP, UDP, Multicast, UDP Unicast. Note: The protocol automatically is switched to TCP if Secure connection is chosen:   Ports used between ONVIF camera and VSG: RTP/RTSP/TCP (secured 😞 443 HTTPS: 443/ customizable (requires TCP)   RTP/RTSP/TCP (unsecured 😞 80 HTTPS: 80/ customizable (requires TCP)   Unicast/ Multicast UDP: has to be configured in a camera first control connection via http port (default port 80 or customizable/ RTSP port: 554)   Nice to know: For a better understanding of the  BVMS 10.0 - ONVIF camera integration with VSG , we   encourage  you to join our online Trainings from  Bosch Building Technologies Academy!
    View full article
    Tuesday
    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.  
    View full article
    Tuesday
    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, Operator Client This article describes the initial information needed to start troubleshooting Operator Client Crash.   General Information   SMA validity How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status? BVMS stand alone or appliance Detailed problem description   Symptom specific Information Problem Description   Note down the events that lead to crash Classify the crash reproducible crashes that trigger Windows Error Reporting crashes/ hangs/ freezes that are hard to reproduce, or take long before repeating   Logging Information   Dump file from the crash – refer to the following article How To create BVMS memory dump?  ConfigCollection from the machine where the crashing Operator Client is running.
    View full article
    Tuesday
    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. How to collect Video SDK log files?   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
    View full article
    Tuesday
    This article lists the initial troubleshooting steps and concrete instructions for collecting logging for issues with ONVIF cameras, added to BVMS system. We will classify the different issue scenarios one can have using ONVIF cameras in BVMS system. Depending on the issue the article lists the required logging to start initial troubleshooting.
    View full article
    4 weeks ago
    Operator Client helps you display the original full image circle of a panoramic camera, its image dewarped or you can select a point of interest of the image. Cropping and using ePTZ in a cropped image is possible in Live and Playback Mode. The Image window allows a flexible resizing of the Image pane that displays a panoramic camera or any other camera. This article provides you information on how you can switch the view mode of panoramic camera in Operator Client. Article requirements: Operator Client Panoramic camera PC/ Server/ Workstation
    View full article
    100% helpful (1/1)
    ‎04-29-2021 10:40 AM
    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"/>
    View full article
    100% helpful (1/1)
    ‎04-14-2021 09:53 AM
    What happens when you upgrade the SW of your Management Server form e.g. BVMS 10.0 to BVMS 10.1 and you have not prepared a BVMS 10.1 activation key beforehand? => The System will be unlicensed and Operator Client will not be able to connect to the MS as long the new BVMS 10.1 activation key is not provided to the system via Config-Client. Therefore,   performing the steps from this article is absolutely necessary.
    View full article
    ‎04-12-2021 03:17 PM
    Question Dear Bosch, you have so many nice articles related to BVMS on the knowledge base( 😉 ). I would really like to have a consistent overview of the available information. Answer Sure! Status Article Description   Bosch Visio Design Icons Set of Visio Design icons for Bosch products. 2020-08 Updated BVMS - Device Compatibility This document describes how BVMS works with older and newer Bosch cameras. 2020-08 Updated BVMS - Single port connectivity  This document describes how the SSH functionality works.   BVMS - Configure time services  This document provides a guideline on how to configure time services.   BVMS - Merging VRM systems  This document describes how to merge two VRM systems into a single system.   BVMS - Operator quick guide This document serves as a quick guide for operators. 2020-02 Updated BVMS - Streamlining This document describes the streamlining concept. 2020-02 Updated BVMS - Configuring a Microsoft iSCSI target This document explains how a Microsoft iSCSI target can be configured. 2020-08 Updated BVMS - Deployment guide This document describes how a BVMS system can be deployed from the commandline. This is useful when using software deployment environments. 2020-08 Updated Virtualization - A concept explained This document explains virtualization. 2020-08 Updated BVMS - Upgrade guide Described the process on how to upgrade a system (checklist)   BVMS - BIS Connectivity Describes how to connect BVMS to BIS 2020-08 Updated BVMS - SDK help Provides instructions and examples on how to use the BVMS SDK   BVMS - Keyboard shortkeys Shows a (normal computer) keyboard and the shortkeys that are available for BVMS.   BVMS - OPC Server Describes the functionality available in the OPC server.   BVMS - Mobile Video Service Describes the Mobile Video Service conceptually.   BVMS - GDPR Description on how GDPR impacts BVMS.   BVMS - Network design guide First version composed together with ASA. Feedback welcome! 2020-08 Updated BVMS - Upgrade guide Describes how to upgrade a BVMS system step by step. 2020-09 Updated BVMS - System design guide Previously known as pre-sales guide.   BVMS - Policy based recording Describes the “cameras and recordings” tab, in addition to the product manuals. 2021-01 Updated BVMS - Blueprints Shows general BVMS system design blueprints.   BVMS - Activate demo license Describes how customer can generate and activate their own demo license. Includes link to the LIF file. 2020-08 Updated BVMS - AE Specification Architects and Engineering specification.   BVMS - Automatic login of Operator Client Describes the parameters which allow the operator client to automatically login. Updated!  BVMS - ONVIF Compatibility Lists the tested ONVIF devices.   BVMS - Configuring LDAP Explains how BVMS can be connected to a LDAP environment.   Safe software delivery Describes how customers can check the integrity of the installation zip files.   BVMS - Client installation package Describes how a reduced client installation package can be used. 2020-10 Updated BVMS - Decoding performance Shows the workstation performance   BVMS - Migrating SQL Database Describes how to migrate the SQL database to a different server. 2020-08 Updated BVMS - Securing the security systems Describes how to secure a BVMS system.   BVMS - ANPR by ISS Describes how to configure ISS SecureOS and BVMS to combine ANPR functionality.   BVMS - IEC62676-1 Describes how BVMS meets the requirements specified in IEC62676-1   BVMS Lite - Quick start guide Describes how BVMS Lite can be set-up.   How-to: Transition from Project Assistant to (B)VMS Have you ever wondered how to best transition from the Project Assistant to (B)VMS?   Software-defined video surveillance storage Describes the collaboration between HPE, SUSE and Bosch in modernizing video surveillance storage.   BVMS Person Identification - Data Protection Information The attached document aims to provide concerned parties, such as customers, users, operators or consultants, with an overview of data privacy and protection related features of BVMS Person Identification. 2021-04 Updated Software Service and Support Describes how software moves through the product lifecycle.   VRM eXport Wizard Describes how to use the VRM eXport wizard 2020-11 Updated BVMS Project checklist The BVMS Project Checklist is an Excel-based tool which makes it easier to design a BVMS system.   BVMS - Automated firewall configuration How does BVMS 10.0.1 (or newer) configure the firewall during the installation of the system?   BVMS - Store snapshot of all cameras My customers asks me to store the field of view of the cameras connected to BVMS. Is there an easy way to achieve this without opening every camera manually?   BVMS - Demonstrating (JPEG) cameras How can I use "virtual" cameras to demonstrate BVMS?   How to create CA signed certificates for cameras and distribute  Configure video authenticity / integrity using CA signed certificates New 2020-08 BVMS - Operator collaboration using Slack  Configure BVMS to integrate with Slack. New 2020-08 BVMS - Person Identification Camera Placement Guide  Describes best-practices on camera placement when using person identification. New 2020-10 BVMS - Tattile configuration  Describes how to configure Tattile (LPR) cameras and BVMS.
    View full article
    100% helpful (1/1)
    ‎04-12-2021 03:07 PM
    Compared to hardware, in which it is relatively easy to define an end-of-support concept based on the expected lifetime, software behaves totally different. In theory, when the environment does not change, software can still be running ten years after it has been installed. As new versions of the software are released regularly, it is important for customers to know what they can expect from Bosch Building Technologies when the software is purchased. This document describes how Bosch Building Technologies handles the life-cycle of the BVMS, BIS, AMS, and APE, and in which state a specific release can reside. Additionally this document lists the up-to-date situation for all of those software packages.
    View full article
    ‎04-06-2021 09:11 AM
    Related Products: BVMS, application crash, memory dump This article lists the scenarios in which technical support normally request dump file from a BVMS system. It contains general guidelines how to create a dump file for BVMS system and provides links to more concrete articles, that correspond to particular issues and exact steps to create a dump. BVMS dumps are needed to troubleshoot the following types of issues: Application crashes – dump is expected to provide more information about the cause of the crash and its origin. Memory or handle leaks – dump is expected to point to their origins Deadlocks, freezes and hangs – dump is expected to point to their origins Recommended tool to create BVMS dumps. The recommended tool is Procdump. It is a command line tool which must be started from the command shell. Development provides couple of .bat files that start Procdump with predefined parameters and cover the most common dump creation cases. The tool as well as the set of .bat files are attached to this article: BVMS_DumpTools_V2.zip The batch file names follow a naming guideline: <Executable>_<Dump use case> , where <Executable> is one of: ConfigClient ConfigWizard OperatorClient ManagementServer ArchivePlayer ExceptionTest and <Dump use case> is one of SingleDump TwoDumps DumpOnException DumpOnHang ActivatePostmortemDebugging There are 3 possible error scenarios and corresponding dump creation methods: Dump creation for reproducible crashes that trigger Windows Error Reporting Run the affected application/service (Operator Client, Configuration Client or Management Server Service) Reproduce the steps that lead to the crash Leave the Windows crash dialog open Run the corresponding batch file for creating a single dump: *_SingleDump.bat. E.g. run OperatorClient_SingleDump.bat to create a single dump of the Operator Client process. Provide support with the resulting .dmp file a description of the steps to reproduce the problem ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_onException.zip Dump creation for reproducible memory or handle leaks Run the affected application/service (Operator Client, Configuration Client or Management Server Service) Run the corresponding batch file for creating two dumps: *_TwoDumps.bat. E.g. run OperatorClient_TwoDumps.bat to create two dumps of the Operator Client process. Note that by default, the delay between the two dumps is set to one hour (3600 seconds). Depending on the magnitude of the memory leak, you might want to increase/decrease the delay. To do that, edit file *_TwoDumps.bat: replace value "3600" by a value that fits your needs e.g. a value of "7200" will create two dumps with a delay of two hours. Reproduce the steps that lead to the memory leak. Wait until the second dump was created. Provide support with the resulting two .dmp files a description of the steps to reproduce the memory leak a ConfigCollection Dump creation for crashes/hangs/freezes that are hard to reproduce Deactivate the restarting option for Operator Client / Configuration Client: To deactivate the restarting option for Operator Client / Configuration Client: edit ..\Bosch\VMS\bin\ConfigClient.exe.config or ..\Bosch\VMS\bin\OperatorClient.exe.config. Navigate to section <appSettings> add a new entry <add key = "DisableExceptionHandling" value="TRUE" />. Run ActivatePostmortemDebugging.bat Run the affected application/service (Operator Client, Configuration Client or Management Server Service) As soon as the issue appears, check whether the dump was created. Provide support with the resulting .dmp file description of the steps to reproduce the crash ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_Just-In-Time-Debuger.zip
    View full article
    ‎04-05-2021 05:17 PM
    Question Why I cannot see my camera in the Logical Tree from Operator Client? Answer Please make sure that you have done all the steps below accordingly. Normally, to be able to view a camera in the Operator Client, you need to: Go to the Maps and Structure tab from Configuration Client. Drag and drop the camera in question from the Device Tree to the Logical Tree. Save and Activate the changes. This step is very important because otherwise, you will not be able to see the changes in Operator Client, even though the first 2 steps were carried out in Configuration Client.
    View full article
    ‎04-05-2021 05:08 PM
    In this article we will present some useful examples, Q&A and specific cases in which our customers have requested assistance regarding the ports that must be open within a LAN for all BVMS components
    View full article
    100% helpful (3/3)
    ‎04-05-2021 04:58 PM
    What should you do if you tried to drag an drop the device to the cameo window from BVMS Operator Client and instead having the video, it displays the logical tree?
    View full article
    100% helpful (1/1)
    ‎04-05-2021 04:53 PM
    Question:  What to do if “Management server is not online” message is displayed when you access Configuration Client?
    View full article
    100% helpful (1/1)
    ‎04-05-2021 04:52 PM
    Question:  What the “Storage state failure” alarm message means in Operator Client?
    View full article
    100% helpful (1/1)
    ‎04-05-2021 04:49 PM
    This article explains how to find and calculate the specific size of BVMS logs on your server when the log starts to overwrite your own data.
    View full article
    100% helpful (1/1)
    ‎04-05-2021 04:44 PM
    Various overlays in the video image provide important status information. But what does mean the blinking play button near the yellow exclamation icon?
    View full article
    Top Contributors
    Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist