Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    ‎06-21-2021 11:53 AM
    Do you want to know more about designing a BVMS system?
    View full article
    ‎06-17-2021 12:10 PM
    Depending on the license type you have installed in the Bosch Video Management System (BVMS), you can add a  certain number  and different types of cameras/ encoders.  BVMS s upports 3 rd  party cameras as well, but they need to be compliant to  ONVIF Profile S. This article explains how to add new ONVIF cameras to a system that runs in full Bosch Video Management System (BVMS) via the Configuration Client. We recommend using Bosch Workstations and Servers. They are fully tested and optimized for Bosch Video Management System. Article requirements: BVMS installed ONVIF camera PC/ Server/ Workstation
    View full article
    ‎06-10-2021 09:32 AM
    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
    ‎06-10-2021 12:29 AM
    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
    ‎06-10-2021 12:28 AM
    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
    ‎06-08-2021 09:17 AM
    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
    ‎06-08-2021 09:11 AM
    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
    ‎06-08-2021 09:06 AM
    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
    ‎05-20-2021 03:58 PM
    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-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 (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
    ‎04-05-2021 04:42 PM
    From BVMS 10.0 onwards BVMS is an ONVIF Profile S conformant client. Cameras which are listed as Profile S compliant product on the ONVIF website are supported based on the ONVIF Profile S functionality. In the table below you can find an overview of the tested and supported ONVIF cameras for BVMS.   Version List of tested cameras BVMS 7.5 BVMS 7.5 list of tested ONVIF cameras  BVMS 8.0 BVMS 8.0 List of tested ONVIF cameras  BVMS 9.0 BVMS 9.0 List of tested ONVIF cameras  BVMS 10.0 BVMS 10.0 List of tested ONVIF cameras  BVMS 10.0.1 BVMS 10.0.1 List of tested ONVIF cameras  BVMS 10.1 BVMS 10.1 List of tested ONVIF cameras    The table below shows in which situation a specific camera can be connected to BVMS and is supported. BVMS version BVMS 9.0 and older BVMS 10.0 and newer ONVIF Profile S compliant camera Yes Yes Yes Yes BVMS tested camera Yes No Yes No           Supported camera Yes No Yes Yes   For BVMS version 10.0 and above, please make sure to go through these steps: Please check the List of tested cameras. If the device is not listed in the List of tested cameras, then please check   here   and make sure that your device is ONVIF Profile S compliant. If your camera is not listed in the tested cameras and is not listed on the ONVIF website as Profile S conformant, we cannot help you when you have an issue with this device. You should approach the device manufacturer to certify the device as ONVIF Profile S conformant. For example, if you have an   Axis camera, M1004 model, please fill in your product details in the Application Type, Profile(s), Manufacturer and the Product Name fields, under the   Product Search   option, and press on the “Search” button: 3. If your device is ONVIF profile S compliant you can contact Bosch Central Technical Support and request assistance. Additional information: Cameras listed as tested are owned by Bosch and issues can be fully investigated by Bosch. Cameras not listed as tested are not owned by Bosch. Solving issues might take longer as it requires collaboration with the camera vendor. Bosch support teams might need to refer to the camera manufacturer’s support line to help fixing the issue. We consider the firmware listed on the ONVIF website as the minimum firmware version of a camera. Please let us know if you run into issues with newer firmware versions so that we can investigate those accordingly. If the problem is a firmware regression, we might need to refer you to the camera manufacturer for support.
    View full article
    ‎04-05-2021 04:37 PM
    This article  provides an overview of Operator Client (BVMS 10.0.1) for most used functionality for security operators and incidental users.
    View full article
    ‎04-05-2021 04:31 PM
    This article describes how can you check the status of your Software Maintenance Agreement (SMA) for Bosch Video Management System (BVMS)
    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