Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    Thursday
    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 Overview: This article describes the initial steps one can take for   troubleshooting BVMS display   issues (during   live view   or   playback). It also summarizes what initial information and logs are needed for support in order to start the issue investigation.   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 Check and eventually update the version of your Graphic Card driver. During BVMS system tests there were documented cases of display issues related with out of date Graphic card divers. ❗   It is important that the Graphic Card driver of the client is up to date. Find the supported version of the Graphic Card driver in the corresponding to your BVMS version Release Notes (https://downloadstore.boschsecurity.com), in the section Hardware drivers.   Symptom specific Information   Problem Description   Is the issue camera type / FW dependent? Are all the devices in the system affected? Is the issue existent for all BVMS Operator Clients in the system? Is the issue existent for hardware decoders, for camera Web Interface or other display Clients? Is the recording, the playback or are both affected?   Logging Information   BVMS ConfigCollector logs keeping the following conditions: From the machine that shows the issue VSDK logging – please follow the steps from the article: How to collect Video SDK log files  VRM logs (in case VRM runs on the same machine like the BVMS MS, then BVMS ConfigCollector logs from the server) for VRM version 3.82 and onwards use VRM Monitor.   The following articles will help you out:    How to access VRM monitor from BVMS Configuration Client? How to collect VRM logs with VRM Monitor (v3.82/ v3.83)? Screenshot of the Dashboard of the VRM for VRM version till 3.81 - contact support to receive BVIP Log collector tool and use it to collect VRM logs Movie showing the display artefacts can be helpful
    View full article
    Thursday
    Related Products Workstations, Z4G4, Microsoft License Question Is it possible to Activate Windows 10 by phone for Bosch Workstations? Answer With introduction of Windows 10, Microsoft disable the phone license activation for Bosch Workstations. Please perform online activation over internet.
    View full article
    Thursday
    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.   Step-by-step guide   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 :How To create BVMS memory dump?  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
    Thursday
    In order to start to analyze and optimize Video Analytics settings for particular customer set up, we need initial information and export of example video. This article describes the absolute minimum information we need in order to start analyzing and optimizing Video Analytics performance. Video Analytics (VA) task performance optimization Please provide the following details:   Symptom specific Information   Problem Description   Describe the expected result from the VA task. It is important to get detailed information of the results VA should provide. Define what is the customer’s priority: High sensitivity - miss as few true alarms as possible, but increases the likelihood of more false alarms! High precision – have less false alarms, but accept the risk to miss true alarm! Using VA is always based on balancing between sensitivity and precision. It is not always possible to get high sensitivity and high precision at the same time.   Provide an export of recorded video that should contain: Meta data: for basic understanding of meta data, please read the latest Software Manual Video Content Analytics for instructions about doing a video export with meta data, please read the article: How to export video including meta data (Export video including Video Analytics meta data).   Couple of examples of false alarms (in case false alarms are the issue) Provide the number of false alarms per time span (per day, per week, etc.) What would be acceptable as a number of false alarms per time span   Couple of   examples of situation that should have caused alarm, but VA did not generate the alarm as expected. In this case please provide the time stamp of the event and short description   Screenshot from the Camera Calibration Verification page - only in case calibration is needed for the particular VA functionality  access the Calibration Verification page of the camera (via the Configuration Manager or Web Interface)  provide screenshot from the verification of each parameter used for camera calibration     Note:  For more information on Camera Calibration and Calibration Verification, please check: How To calibrate camera for Video Analytics?
    View full article
    Thursday
    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
    Thursday
    Related Products: Video SDK Overview: Analyzing issues with Video SDK based application is a challenging task. One needs to determine if the issue is based on wrong implementation of the Video SDK functionality, wrong programming practices, functionality and runtime behavior of the system with SDK functionality or Video SDK issues. In order to start troubleshoot Video SDK application support needs the following initial information and logging. Please prove the following information to support:   Symptom specific Information   Problem Description VideoSDK version VideoSDK issue description What is the expected behavior? What is the issue?   Environment Which shared resources are accessed by SDK actions? (Dome cameras, decoders, etc.) 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 The optimal approach is to provide both source code and logging for the problematic Video SDK application. Try to reproduce the issue with one of the  Video SDK samples (Advanced C# Sample, Complete C# Sample, Simple C# Sample) and provide the result from the test. Source Code Provide a little sample application that illustrates the Video SDK issue and list the reproduction steps. Logfiles Enable VideoSDK backdoor logging, reproduce the issue (note the date and time) and provide the Video SDK logs. How to collect Video SDK log files 
    View full article
    Thursday
    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
    Wednesday
    Answer Web Browsers: o Google Chrome o Microsoft Internet Explorer 11 or higher o Microsoft Edge (Chromium based) o Mozilla Firefox   Important: When using browsers where Mpeg ActiveX is required → VCA, clock & date and recording dot point may not work. For a complete browser functionality, Mpeg ActiveX 6.34 or newer is needed and it is supported only by   Internet Explorer (IE). This is the only browser that allows the VA configuration option (for e.g.).   If you would like to avoid using IE and you want to   configure VA, it is recommended to   use Configuration Manager. According to the Release Letter, Configuration Manager is used for configuration and licensing of the various products. It includes Video SDK 6.3 and latest plug-ins for   VCA configuration. You can Download it from   here.   If you use Firefox, the issue below might arise. In this situation, IE browser/ CM is recommended to be used in order to access the missing elements. Firefox does not allow ActiveX elements . Therefore, some features are missing inside the webpage. Note: VCA related check boxes is fixed in 7.80 for Microsoft Edge. (7.80.0128 Release Letter)
    View full article
    Wednesday
    The Windows Storage Server operating system of DIVAR IP all - in - one 7 000  is  installed on a two SSD drives in redundant (mirrored) configuration. Health status of  the mirrored OS drives can be monitored using a tool called Virtual RAID on CPU  (formerly known as Rapid Storage Technology). Installation and configuration steps  are described below. Step-by-step guide   1. Installation: Download  the setup  from  here Copy the content to a USB drive When the BVMS default screen is shown, press CTRL + ALT + DEL Hold down the SHIFT key while clicking Log off Log in as BVRAdmin Transfer the IATA_CD.exe from the USB drive to the BVRAdmin desktop Double click  the  IATA_CD.exe executable Follow the installation procedure  as shown in the screen shots     2. Email notification: Note: The E-mail notification feature is based on SMTP access without authentication. It is strongly suggested to use this functionality only with a dedicated server in the local network, which is specifically configured for this purpose and doesn’t handle any critical data.
    View full article
    3 weeks ago
    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
    3 weeks ago
    Upcoming with FW 7.10 and CM 6.20, Camera Trainer is a licensable Intelligent Video Analytics module that allows uses to define objects of intereste and train their own detectors for them based on examples of target objects and non-target objects. In contrast to the moving objects detected in general by IVA 7.10, Camera Trainer allows detection of both moving and non-moving objects, separates and immediately classifies them. Training can be done both on live video as well as on recordings available through the respective camera. The resulting detectors can be down- and uploaded for distribution to other cameras.
    View full article
    100% helpful (1/1)
    3 weeks ago
    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
    100% helpful (1/1)
    3 weeks ago
    This Video should help you to understand, what calibration means, why and when to calibrate the cameras.
    View full article
    3 weeks ago
     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
    3 weeks ago
    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
    3 weeks ago
    ⚠️  CAUTION! If a computer on which VRM Server is starte d is simultaneously accessed by multiple  Configuration Manager programs, this can result  in an inconsistent VR M configuration. Ensure  that different people do not make chang es to the configuration at the same time.   Step-by-step guide Open one browser and type in the IP address of the VRM server you are pulling the log from. This will take you to the VRM Monitor web page. Log in with the VRM credentials (default user name is srvadmin); by default, there is no password   3.82 version: Go to Monitoring > System > Logbook The Export  Log bock page allows you to export all or only selected system  log s as a .zip file. Export system  log s Select the desired export  log book options. Export as ZIP  – Click to create a .ZIP file with selected   log  files, for example to send them to the Central  Technical Support Team.   3.83 version: Please note that the interface for VRM v3.83 has changed on the log collection. Therefore, the VRM log collection will be done by accessing Monitoring > System > Export Logbook Export system  log s Select the desired export  log book options. Export as ZIP  – Click to create a .ZIP file with selected   log  files, for example to send them to the Central  Technical Support Team. You can also collect the device maintenance logs from the VRM monitor (for VRM 3.50 or newer) Open the   VRM monitor   and log in with the VRM credentials Go to   Monitoring->   Devices   -> click on the   download icon   next to the camera
    View full article
    3 weeks ago
      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
    3 weeks ago
    Follow the steps from this article and find out how you can integrate the Bosch USB Keyboard "KBD Universal XF" with Bosch Video Client (BVC).   Driver installation is required on the workstation where the KBD Universal XF Keyboard is connected Driver can be download from the official Bosch Security and Safety Systems page. Navigate to Products > Video System > Switching System and Keyboards > Keyboards >   KBD Universal XF   > Downloads > Software Operational Check When connecting the KBD Universal XF Keyboard to a workstation, the LEDs will blink once. This indicates that the keyboard is detected by the workstation
    View full article
    3 weeks ago
    The   Clear   button on the   Configuration Manager   is designed to clear the codes that are self-generated by the IP firmware or the Configuration Manager itself. Follow the steps below, if you want the "Clear" button from Configuration Manager to able to erase the Alarm task script that are self created by users themselves.   Step-by-step guide   When you create your alarm task script, add it within an opening quotes which then the   Clear   button will be able to erase all those codes within the quotes. Alternatively, create your own quotes within your script by following the below rules. In the  Below example,   //{{MyScript_start   is inserted before any script and   //}}Myscript_end   is inserted at the end of the script. By doing this, the   Clear   button will now be able to recognize and detect the manual scripts created by user and erase them.   Example: //{{Myscript_start ControlCode auxon1:={Operation(AuxOn)Number(1)}; if(Motion(1))then auxon1; //r1_o1 //}}Myscript_end
    View full article
    3 weeks ago
    This article shows how to configure Input Alarm and later search for them in the Event search using Web Interface. There are only 3 different search parameters for Event type search, which are "All", "Motion" and "Alarm". Once can search for any alarms during the set time period and channel and in this way indirectly to filter for Input Alarm (if only Input Alarm triggers Recording for a particular channel). It is not possible to directly narrow the search for particular Alarm type (ex. Input alarm).
    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