Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    ‎02-12-2019 02:11 PM
    The technical note in the attachment details device-specific as well as version-specific differences of Intelligent and Essential Video Analytics from FW 4.0 up to FW 6.60.
    View full article
    ‎10-10-2018 03:08 PM
    rectrieve live video with Video Security Client Software for Windows version 2.2
    View full article
    ‎06-06-2019 03:13 PM
    Background information: The Bosch Video Client is a 32bit application, CFM 5.50 and newer are 64bit applictions. 32bit applications can only R/W 32bit files (where as 64bit applications can R/W to both 32 & 64bit files), so in order for BVC to access the CFM database, this database also needs to be 32bit. Problem Description: If you need to configure newer devices with newer FW, you will need to install the relavant CFM version (e.g. CPP 7.3 Camera with FW 7.10.xxxx would require min CFM 6.20.xxxx), by installing the new CFM this will upgrade the original database to 64bit. Leading to an issue that BVC can not open the database! Solution: Reinstall CFM <5.5.x once more which will cause the database to be migrated back to 32bit. Important Notes: Strong database encryption must not be activated, otherwise BVC will fail to start.
    View full article
    ‎02-14-2019 12:55 PM
     Related Products: Video Analytics for Firmware 6.60 and above This article describes how to count with Bosch Video Analytics with How to Video and a Technical Note on the topic. View the video to get initial idea how to set up the feature, short explanations on the prerequisites and an example configuration.    For in depth description of the feature counting please check the attached Technical Note. It provides background information and technical details and can support you to configure and optimize a particular counting scenario.  How to Video: People counting default scenario Learn how to configure the default scenario - People counting: A predefined scenario that can be used to count people that are crossing a specified / specific line.   Technical Note on Counting The attached document describes in depth the count feature of Video Analytics. It explains how to plan the camera perspective and best practices for camera view, the set up for the scenario people counting and the options to access the counter data.   Note: If needed you can get additional how to information on camera calibration.
    View full article
    ‎03-29-2019 10:38 AM
    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. 1. Detailed description of the expected behavior of the SDK functionality. 2. Detailed description of the actual behavior of the SDK functionality. 3. 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? 4. 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? 5.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.)  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. 1.Source Code Provide a little sample application that illustrates the BVMS SDK issue and list the reproduction steps. 2.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.   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
    ‎02-14-2019 12:57 PM
    Related Products: Video Analytics for Firmware 6.60 and above Technical Note on Intrusion Detection The technical Note  attached to this article contains detailed technical description of Intrusion Detection, set up guidance for different usage scenarios and best practices. It is useful to get in depth knowledge about Intrusion detection or to find the answer of frequently asked questions.   Intrusion detection without calibration Learn how to use the default scenario - Intrusion detection no camera calibration: A predefined scenario that can be used to detect intruders in small areas and controlled environments   Intrusion detection one field   Learn how to use the default scenario - Intrusion detection one field: A predefined scenario that can be used to detect intruders in small areas.   Intrusion detection two fields   Learn how to use the default scenario - Intrusion detection two fields: A predefined scenario that can be used to detect intruders in large outdoor areas.  Note: If needed you can get additional how to information on camera calibration.
    View full article
    ‎02-12-2019 02:15 PM
    The attached technical note describes h ow to benchmark and differentiate video analytics solutions.
    View full article
    100% helpful (1/1)
    ‎03-18-2019 11:22 AM
    Related Products: Video Analytics for Firmware 6.60 and above This article covers traffic monitoring of Bosch Video Analytics with How to Videos (one already available and one in planning) Default scenario of wrong way detection Learn how to use the default scenario of wrong way detection: A predefined scenario that can be used to detect an object that is traveling the wrong way.   Default scenario traffic incidents This predefined scenario is designed to detect common traffic incidents on roads: Wrong way – triggers an alarm if object travels in wrong direction Pedestrian – triggers an alarm if pedestrian is on the road Slow vehicle – triggers an alarm if vehicle moves slower then predefined speed. Stopped vehicle – triggers an alarm when vehicle is stopped longer than predefined time span. Dropped object – Triggers and alarm if an object is dropped on the road   This how to video shows in detail how to use the predefined tasks Wrong way, Slow vehicle and Stopped vehicle.   Note: If needed you can get additional how to information on camera calibration.  
    View full article
    ‎02-12-2019 02:16 PM
    The attached technical note describes the camera tamper detection options available with FW 6.30: Scene too dark / bright, global change, reference image check
    View full article
    ‎11-19-2019 01:22 PM
    Symptoms The Activation Key provided from SLMS cannot be activated in BVMS. During the introduction of BVMS 10.0 the BVMS Lite16, 32, and 64 base licenses were not introduced and succeeded by BVMS Lite 10.0 (8 channel base package). Existing BVMS Lite customers might still want to upgrade to BVMS 10.0. Solution The LIF file attached to this article (in the zip archive) can be imported in BVMS Lite 10.0 installations using the license manager (the license manager can be found in the "Tools" menu of the BVMS Configuration Client). Once imported, BVMS Lite 16, 32, 64 systems that are covered under SMA can be upgraded.    
    View full article
    ‎05-23-2019 07:45 AM
    Question  What's new in version 1.2? Answer Next to general stability improvements and bug fixes, version 1.2 of the Project Assistant introduces the following new features: Support of Flexidome IP 8000i Wi-Fi camera with regard to wireless commissioning .txt file import now supports tags to be somewhere in the column header, e.g. “IP address [ip]”, where for version 1.1 only the [ip] tag was allowed in the column header exclusively Software sealing support for cameras with firmware 6.60+ Extended report information Related News Project Assistant project file import functionality in Configuration Manager 6.10 Bosch portable camera installation tool is available and can be used in combination with the Project Assistant (check out the corresponding how-to video in this community)   PS: For detailed information, please refer to the release letter attached.
    View full article
    ‎10-30-2019 08:07 AM
    Symptoms During the introduction of BVMS 10.0 the BVMS Plus unmanaged site expansion licenses were not introduced, even though this functionality was announced to be available. Solution The LIF file attached to this article (in the zip archive) can be imported in BVMS Plus 10.0 installations using the license manager (the license manager can be found in the "Tools" menu of the BVMS Configuration Client). Once imported, the purchased licenses (MBV-XSITEPLU-100) can be activated.
    View full article
    ‎04-26-2019 11:03 AM
    Related Products: BVMS / MVS / VSDK Overview: On request from development to provide a dump file from MVS system please follow the steps in the solution section. Solution: Reproduce the issue Download the Microsoft debugger procdump (https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx). The procdump tool is also attaced to the article https://community.boschsecurity.com/t5/Security-Video/How-To-create-BVMS-memory-dump/ta-p/7326?advanced=false&collapse_discussion=true&filter=includeTkbs,location&include_tkbs=true&location=tkb-board:bt_community-tkb-video&q=dump&search_type=thread  When application is crashing, do not click any buttons on the appeared error window that will change the program state. Run the procdump.exe from the directory where you copied the tool with following command line (Start - cmd): procdump.exe –ma <name of the programm exe> <dump file name>.dmp In the case of MVS you need to do that for all 4 MVS services: - Bosch.MVS.SourceProvider.BVMS.Service.exe - Bosch.MVS.DataStorage.Service.exe - Bosch.MVS.SourceProvider.MobileCamera.Service.exe - Bosch.MVS.Transcoder.Service.exe
    View full article
    ‎04-01-2019 12:33 PM
    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. 1. Detailed description of the expected behavior of the SDK functionality. 2. Detailed description of the actual behavior of the SDK functionality. 3.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? 4.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? 5.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.)    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. Make sure that logging is implemented in the script and that logging is activated in the configuration. 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
    ‎12-06-2018 03:48 PM
    For larger projects, where many cameras need to be commissioned, the question might come up on how to tackle it in the most efficient way using the Project Assistant. In the end, a Project Assistant file can comprise up to 500 cameras. Especially if multiple contributors perform the commissioning step in parallel, you need an appropriate approach. For visualization reasons, let's use a simple example. Let's imagine we have a project that comprises 500 new cameras in total. 250 cameras for building A and another 250 cameras for building B. Here are two options: Creating multiple (sub-) projects and merge them in Configuation Manager If you cannot use Dropbox for synchronisation via the cloud, you can simply create 2 projects - one for building A and one for building B. Both projects can be prepared ahead of time, e.g. in the office, and exported in order to share them. Sharing the exported as well as encrypted project files can be done via E-mail, thumb drive, any of the major cloud storage services, etc.*. Now let's assume that there is one contributor working on building A and one working on building B. After each contributor has commissioned his or her 250 cameras each, they can themselves export the project files. To re-combine or merge both sub-projects, we have introduced a Project Assistant project file import feature in our Bosch Configuration Manager 6.10. This feature allows you to conveniently import multiple project files at once and to easily integrate them into your existing system structure. Please, check out the corresponding "How to import project files into Configuration Manager 6.10" article in this community. * Restrictions due to project file size might apply depending on the sharing medium. The synchronization functionality is only available for Dropbox. Using the Dropbox Synchronization feature This feature let's you plan and preprare a project ahead of time, e.g. in the office, which can then be shared via Dropbox with multiple other contributors as needed. That means everyone that was "invited" to work on this project has access to the same project file, where there is only one "master" version residing in the cloud that is accessed and synchronized via Dropbox. Consequently, you can avoid managing multiple versions of the same project file. Therefore, depending on the internet connectivity of all contributor's devices, you can see the real-time progress of the project, no matter if you are in building A, building B or even in the office. All updates to the project are immediately synced via Dropbox among all contributors. If you want to know how to setup it up, please check out the following videos:   Of course, the Project Assistant project file import feature in our Bosch Configuration Manager 6.10 is also available for futher configuration and system integration for this option, as well.
    View full article
    ‎05-22-2018 04:57 PM
    Related Products DIVAR AN 3000 DIVAR AN 5000 How to configure Monitor B output for Divar AN 3000-5000 Solution see attachment.
    View full article
    ‎05-22-2018 05:01 PM
    How to export the Archive Player in IE
    View full article
    ‎11-26-2018 04:14 PM
     This article explains how to exchange the battery on the DIVAR Hybrid and Network in a safe way.
    View full article
    ‎02-12-2019 02:19 PM
    Never lose track of an object of interest! Intelligent Tracking automatically zooms in to and follows a selected Intelligent Video Analytics object as far as possible with the camera. For AUTODOME / MIC IP 7000, this means automatically steering the camera to zoom in to the object and follow it. For a FLEXIDOME IP panoramic 7000, Intelligent Tracking is available in the Virtual PTZ video and steers the dewarped cut-out. For DINION / FLEXIDOME IP 7000 / 8000 cameras, Intelligent Tracking can steer a region of interest (ROI) stream. The technical note in the attachment discribes how to set Intelligent Tracking up with FW 6.30 and lists the differences based on the camera types.
    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