Important Cookie Information

This website uses absolutely necessary cookies. If you consent to the use of convenience cookies, please click “Yes, I agree.” By clicking on “Privacy Settings.” you can change this setting at any time and withdraw your given consent. Icon down see more You can find detailled information in our Privacy Policy Icon forward-right
Icon up see less

Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    ‎04-16-2019 06:09 AM
     BVMS customers can download camera updates free of charge, in order to integrate approved, third-party cameras. BVMS scans for third-party cameras, automatically configuring motion and other key events; it also enables installers to configure the most important settings for third-party cameras from a single user interface, without the hassle of having to access the websites of other camera manufacturers. The attached files include a list of compatible cameras and the ONVIF mapping files for each specific BVMS version.
    View full article
    ‎04-08-2019 12:44 PM
      Related Products: VRM, Genetec Security Center Overview: It is possible to use VRM free of charge (no extra VRM license is required) within Genetec Security Center. Genetec is sending encrypted secret to the VRM server with the number of the licensed channels. When VRM receives and validates this, it can be used for that number of channels for 24 h. A periodic license update is send by Genetec, so the VRM licensing is guaranteed as long as it is used with Genetec Security Center. Default settings, if not extra configuration is needed or done. -License for 1000 Cameras - License update is done every hour   How to license more than 1000 cameras or change the license update period for VRM within Genetec Security Center: Open the Config Tool and Launch a Video Task Select the Archiver Go to the Resource Tab and click on Extensions From the Tab Installed extensions select Bosch. In the Tab VRM add a new VRM and/or select already configured VRM. Click on Advanced settings and add the following parameters If you need to license the system with more than the default 1000 licenses – create the parameter with Name VrmLicenseRequestCount and as value put the required number of licenses. The parameter name is case sensitive If you need to change the duration of the period between each license request (there is always one license request when the archiver starts) – create the parameter with Name VrmLicenseRequestPeriod. The duration of the period is in milliseconds. The default value is one hour. If the value is set to 0, the license request are disabled. The parameter name is case sensitive     Press Enter to confirm the entry and then Close Press Apply and then OK. At the webpage of the VRM one can check if the number of licenses is changed.                    
    View full article
    ‎04-04-2019 12:52 PM
    In all VRM installation packages the required .NET framework package is included in the VRM installation routine. As Microsoft Operating Systems are expected to get and have the latest security updates applied before installing any new software component like VRM (Video Recording Manger) or VSG (Video Streaming Gateway), the installer will successfully finish the installation routine. The same is valid for BOSCH DIVAR IP product range:  The DIVAR IP Appliance installer contains Microsoft update packages available from Microsoft at the time BOSCH creates the Appliance installer. But all Microsoft Updates release after the Appliance installer release date are not included in the BOSCH package. It is therefore recommended to check for Microsoft updates whenever a Bosch DIVAR IP Appliance installer is installed. For VRM (Video Recording Manager) stand-alone Systems and Servers with VSG (Video Streaming Gateway) installed, it is also strongly recommended to check for Microsoft OS updates before the VRM Master Installer is installed/updated. Note: In case an error code 5100 is shown during the VRM Software installation, please ensure that all Microsoft updates for the used Operating Systems are installed and run the BOSCH Software installer after that once again. For more details Microsoft provides more informaiton here: https://blogs.msdn.microsoft.com/astebner/2008/10/13/net-framework-setup-verification-tool-users-guide/ For older BVMS and VRM installations please also refer to the following previous article: https://community.boschsecurity.com/t5/Security-Video/-/ta-p/416
    View full article
    100% helpful (2/2)
    ‎04-04-2019 12:00 PM
    Possible Communication Issue between BVMS 8.0 Central Server and Video Recording Manager (VRM) 3.70 and 3.71 with BVMS 8.0 installed on different Servers. Problem Identification Communication can get interrupted and configuraiton might fail if the below desribed actions are not performed. If your system is affected or not is described here as follows: There can be authentication issues between the BVMS Central Server and the Video Recording Manager in case they are installed on different Servers. It is possible to see reports at the BVMS 8.x system alarms that VRM reports wrong version Please check in the VRM debug logging if the following logline indications can be found CONFIG;DEBUG;SENDING XPATH /SYSTEM/DEVICES/DEVICE as well as HAS NO CONFIGURED NODE, SET TO CONFIGURED CONFIG;INTERNAL;/SYSTEM/DEVICES CHANGED IN CONFIG. DEVICEID= [DEVICE IP]\0;SYSINFO;INTERNAL;LINE 1 HAS NO CONFIGURED NODE, SET TO CONFIGURED Solution In general please keep in mind, that it is strongly recommended to use VRM 3.71.0029 with BVMS 8.0. Do not use any older VRM version like 03.71.0022. The 03.71.0029 and Releaseletter is available at the BOSCH DownloadStore (status update 2018-10-26). https://downloadstore.boschsecurity.com/FILES/Setup_VRM_03.71.0029_win32.zip Release Letter: https://downloadstore.boschsecurity.com/FILES/Bosch_Releaseletter_VRM_3.71.0029.pdf At the VRM system / server, please check and ensure that the following Microsoft software packages are pre-installed: .NET framework 4.6.2 or higher Redistributables for Visual Studio 2015 In case one component is missing, please perform the following steps: Download the missing Microsoft components. Note: When using BVMS 8.0 the VRM is typically a 32-Bit VRM software. Therefore the 32-Bit Microsoft packages are needed. Component that was seen as missing is the >>   “Visual C++ Redistributable for Visual Studio 2015”            https://www.microsoft.com/en-US/download/details.aspx?id=4814 Please choose the 32-Bit version of that when using with 32-Bit VRM and the >>  .NET framework 4.6.2 or higher (NDP462-KB3151800-x86-x64-AllOS-ENU.exe)       https://www.microsoft.com/en-US/download/details.aspx?id=53344 Stop the VRM (rms.exe) service in Windows services  Install those components with Administrator rights at the VRM server Reboot the server after installation of the Microsoft components Check if the VRM service is running and if needed Re-Start the VRM (rms.exe) service Check that the combination of messages are not longer seen in the VRM debug logging The VRM package is enhanced and useres should no longer run into this issue with VRM 3.81 and newer versions. Please be aware that BVMS releases are tested with certain VRM verions. This still can offer to install a newer VRM than originally rolled-out in the BVMS overall installer. For all VRM versions 3.7x and below 3.81 it is needed to add this packages.
    View full article
    ‎04-04-2019 09:19 AM
    Symptoms transparant data transmission at a Encoder VideoJet Multi 4000 or VIP-X16-XF-E stops / does not work any longer in case of a power outage and restart of the device. Diagnosis when e.g. controlling a Bosch Autodome 7000 and PTZ via Transparent Data not working after reboot of the encoder, this is caused by an issue in the released firmware. It doesn't matter if it is Firmware 6.30.0047 or 6.30.0059. As a power outage should happen not too often the solution below is offered to fix this. Solution The solution is via a workaround using an ATSL script in the encoder to re-set the COM port baud-rate upon a reboot/restart of the encoder (which should in normal practice not happen to often). Please add th following scritp to the Alarm Task Editor tab either via CM or Web interface. //The 1st line set the board rate, 2nd line sets the port type RS232 = 1 or RS485/422 = 2 RcpCommand setCOMBaudrate := { Command( "rcp.xml?command=0x027e&type=T_DWORD&direction=WRITE&protocol=TCP&payload=9600&num=1" ) }; RcpCommand setCOMMode := {Command("rcp.xml?command=0x0208&type=T_OCTET&direction=WRITE&protocol=TCP&num=1&payload=2")}; if (true) then setCOMBaudrate, setCOMMode; If the device has a password set then 2 additional perimeters need to be added UserName() and Password(""). RcpCommand <name of RCP command> := { Command( "Bla Bal Bla" ) UserName(Service) Password( "enter the service level password here" ) }; There will be no furhter release or fix provided by BOSCH status of 2019-03-19 as the ATSL script resolves this.
    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
    ‎04-01-2019 12:31 PM
    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
    ‎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
    100% helpful (3/3)
    ‎03-26-2019 03:21 PM
    Introduced Firmware signature and firmware file encryption to protect IP cameras
    View full article
    100% helpful (1/1)
    ‎03-26-2019 02:54 PM
    Question How can I migrate the full configuration (including server configuration and user settings) of a BVMS system from one server to another? (please note that, currently, the export mechanisms provided in the BVMS Configuration Client do not export the userdata. This is a known problem and being worked on. Until then this work-around should be applied). Answer Stop the BVMS Central Server service on the existing server from the Windows task manager or Services overview. Stop the BVMS Central Server service on the new server from the Windows task manager or Services overview. Copy the contents of the directory C:\programdata\Bosch\VMS\UserData on the existing server to the same directory on the new server (via the network or other media). Copy the "elements.bvms" file located in the directory C:\programdata\Bosch\VMS\ on the existing server to the same location on the new server (via the network or other media). Start the BVMS Central Server service on the new server from the Windows task manager or Services overview.
    View full article
    ‎03-21-2019 11:14 AM
    Related Products: BVMS Operator Client, BRS Overview: BVMS CS gets from BRS the camera states and the events. BVMS OC connects to BRS for camera live view and playback. The BVMS OC to BRS connection is DCOM based (BVMS CS to BRS connection - either web services or DCOM). Troubleshooting and information providing steps: 1. Connectivity issues between BVMS OC and BRS. We speak for BVMS OC to BRS connectivity issue when: BVMS CC scans the BRS and BVMS CS gets the camera states and events (red dot on camera icon when the camera is recording for example) but BVMS OC get no live view or playback from the BRS cameras.      Step 1.  Check if the cameras are correctly configured in BRS and that BRS itself gets live view and recording from the cameras Step 2. DCOM "ConnectionServer" is not registered correctly. "dcomcnfg.exe" navigate to "Component Services - Computers - My Computer - DCOM Config" check if entry "ConnectionServer" is listed. if there is no such entry, register the ConnectionServer out of the installation dir. Open console and navigate to the BVMS installation DCOM directory, e.g. C:\Porgram files (x86)\Bosch\VMS\DCOM type "ConnectionServer.exe /regserver" - press enter refresh DCOMconfig window and check if entry "ConnectionServer" is listed. Restart OC and BRS cameras should work. Step 3. Check and correct the DCOM settings on OC. start dcomcnfg go to Computer and then to MyComputer right click on MyComputer and open properties switch to DCOM-Security Go one after other to both tabs "Edit Limits" and for the accounts "Everyone" and "Anonymous" check all the checkers under the option "Allow" restart the PC   2. BVMS OC doesn’t get BRS cameras Live View, but playback from the same cameras works. Reproduce the issue, note the date and time. Is there other BVMS OC machine where the liveview works as expected? Is the live view working in BRS itself? provide the answer to the above questions and the BVMS OC Configuration Collector Logs to technical support   3. BVMS OC doesn’t get playback from BRS cameras, but gets live view from the same cameras Does the BVMS OC find the time line of the recording? Is it possible to get the playback of the camera on the BRS Appliance itself? Is there other BVMS OC machine where the playback works as expected? Is the playback working in BRS itself? Reproduce the issue provide the answer to the above questions and the BVMS OC Configuration Collector Logs to technical support
    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
    ‎03-17-2019 06:55 PM
    Question How can I find the source (details of the workstation) and credentials that are used to attempt to login into BVMS (when the attempt has failed)? Answer The username that is used to login is saved into the BVMS logbook and can be found by searching the logbook from the Operator Client (username of login is "blabla").   The details of the workstation (mainly the IP address) is logged into the BVMS client log files. These can be found on the workstations in the directory: C:\ProgramData\Bosch\VMS\Log (Hint: for log file analysis a lot of free / open source tools are available. Snaketail is one of these tools, and can be found here.) Open the BVMSClientLog.txt (there could be multiple files which are all related to a different timeframe) and search for the phrase "InvalidCredentialException". If an user has tried to login to the system the following log lines should be present in the log file: 2019-03-17 18:31:53,668 75516 [GUI Thread] INFO Bosch.Vms.Frontend.OpClient.Wcf.DataAccessServiceClient ConnectAndAuthenticate - Call failed with InvalidCredentialException 2019-03-17 18:31:53,670 75518 [GUI Thread] INFO Bosch.Vms.Frontend.OpClient.ServerManagement.CentralServerManager AuthenticateAtMainServer - Main-Server 192.168.20.190: WCF online authentication result is WrongUserOrPassword This needs to be checked for every workstation which runs the BVMS Operator Client.  
    View full article
    ‎03-08-2019 01:21 PM
    Related Products Autodome 7000 HD, MIC 7000i, and MIC 9000i Question  Why is the minimum FW version 6.52.0003 for these models? Answer In November 2018 an internal hardware (HW) change was made to these models that requries this new minimum FW verison. The new HW version isn't bckwards compatible with older FW versions. Question If the unit has been upgraded to a higher version, how do I get the 6.52.0003 FW? Answer This FW verison was only released for these three models, so it isn't available on the Bosch Download Store. At this time, please contact Technical Support to obtain this FW. It will be available on the individual Produvt catalog pages by March 11, 2019 (or sooner).
    View full article
    ‎02-22-2019 11:41 AM
    Question  What's new or fixed in Project Assistant 1.2.2? Answer Next to general stability improvements and bug fixes, version 1.2.2 of the Project Assistant introduces the following new feature on all three platforms: Allow re-configuration of a camera, e.g. wirelessly adjust the field of view of a FLEXIDOME IP starlight 8000i , while local recording is running. One bug fix worth mentioning explicitly is that we addressed a connectivity issue, which was faced, when connecting wirelessly to multiple FLEXIDOME IP starlight 8000i cameras one after another. Related News We have published a new Excel template file that makes the import of existing information into the Project Assistant even easier. Feel free to check out the updated Knowledge Base article. Further information can be found in the release letter attached. Best regards, Your Project Assistant Team!
    View full article
    ‎02-20-2019 05:40 PM
    +++ Update: new Excel template file with detailed explanations of all parameters +++ Intro: The Project Assistant offers two ways of importing existing project data: Option 1) Importing a .bpassist file, which was exported from the app at some point and which contains all information and data ever created/entered inside the app for that specific project. Simply select the "Project Assistant" mode >> click "continue" >> and press "import". Option 2) Importing from a tab-separated text file. This option may be useful, if you have existing project data, e.g. in an Excel spreadsheet, which you want to transfer into the Project Assistant for further use. This article deals with option 2 and explains the steps potentially needed before you can refer to the steps explained in the following Youtube video ("Import from file"). Let's assume you already have existing project data prepared in an Excel spreadsheet and you want to transfer that data into a format that can be imported to the Project Assistant Go to the Bosch Security Systems DownloadStore and download the provided template file "example_project_import_report_template.txt" or the NEW Excel file " 2019_02_20_example_project_IMPORT_template.xlsx" , which also includes detailed instructions and explanations on each parameter. Import the .txt template file into Excel by opening the template file with Excel and following these steps:  Select "delimited" as well as "My data has headers." Select "Tab" in the Delimiters section and finish up the Excel import by pressing "Finish". INSTEAD, you can also use the NEW Excel file, where you can avoid the above described initial import step of the .txt file.   [Option A] According to the provided data columns, copy and paste your existing data from your initial spreadsheet file into the template file (you do not need to populate every column of the template) [Option B] This option works the other way around. Use the Project Assistant header tags, e.g. [ip], [mac], etc., which you can find in the template file and add these tags to the column headers in your initial Excel spreadsheet (cf. screenshot below). The Project Assistant is capable of searching the .txt import file for these tags and of filtering out the corresponding columns (no matter the order of the columns). Go to "Save As" in Excel and save the newly populated template file as a "Unicode Text (*.txt")" file   Transfer the file to where you can find it with the Project Assistant and start the app Create a new project Set a password for the project itself as well as default passwords for the cameras that you would like to assign That's it - Now it is time to refer to the Youtube video mentioned above Enjoy using the Project Assistant and feel free to share your feedback with us!  
    View full article
    ‎02-19-2019 10:34 AM
      Related Products: DIVAR IP 7000R2 and DIVAR IP 6000R2   CTN  SAP # Description   DIP-6180-00N  F.01U.308.406  DIVAR IP 6000 2U W/O HDD  DIP-6183-4HD  F.01U.308.452  DIVAR IP 6000 2U 4X3TB  DIP-6183-8HD  F.01U.308.453  DIVAR IP 6000 2U 8X3TB  DIP-6184-4HD  F.01U.308.454  DIVAR IP 6000 2U 4X4TB  DIP-6184-8HD  F.01U.308.455  DIVAR IP 6000 2U 8X4TB  DIP-61F0-00N  F.01U.308.456  DIVAR IP 6000 3U W/O HDD  DIP-61F3-16HD  F.01U.308.457  DIVAR IP 6000 3U 16X3TB  DIP-61F4-16HD  F.01U.308.458  DIVAR IP 6000 3U 16X4TB  DIP-7180-00N  F.01U.314.520  DIVAR IP 7000 2U W/O HDD (R2)  DIP-7183-4HD  F.01U.314.521  DIVAR IP 7000 2U 4X3TB (R2)  DIP-7183-8HD  F.01U.314.522  DIVAR IP 7000 2U 8X3TB (R2)  DIP-7184-4HD  F.01U.314.523  DIVAR IP 7000 2U 8X3TB (R2)  DIP-7184-8HD  F.01U.314.524  DIVAR IP 7000 2U 8X4TB (R2)  DIP-71F0-00N  F.01U.314.525  DIVAR IP 7000 3U W/O HDD (R2)  DIP-71F3-16HD  F.01U.314.526  DIVAR IP 7000 3U 16X3TB (R2)  DIP-6704-HD  F.01U.308.459 4000GB HDD DIVAR IP 6000/7000      Overview: For recovery of DIVAR IP 6000 R2 or DIVAR IP 7000 R2 one should use only the DVD provided with the particular device. Do not use the DVD for recovery if you are not sure that it is the one delivered with the system. In case the DVD is lost or damaged request the respective ISO image from Bosch Technical Support.  Solution:  Request the ISO image from Bosch Technical Support:   Provide the Serial Number of the device Issue description: What is the reason for the recovery Why it is not possible to use the recovery DVD
    View full article
    ‎02-14-2019 01:02 PM
    This Video should help you to understand, what calibration means, why and when to calibrate the cameras.
    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-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
    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