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-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
    ‎05-18-2018 10:53 AM
    Restrictions of VRM Configuration utility pre-installed on DLA
    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
    ‎02-12-2019 02:16 PM
    The attached technical note describes idle and removed object detection with Intelligent or Essential Video Analytics in FW 6.30, how to configure it and what the limitations are.
    View full article
    ‎05-21-2018 08:33 PM
    Connections and programming for VIP X1XF and VG5 600 Dome.
    View full article
    ‎05-16-2018 09:34 AM
    After changing the resolution of monitor to UHD (3840*2160), the attached monitors results always black.
    View full article
    ‎02-12-2019 02:18 PM
    The museum mode of Intelligent and Essential Video Analytics is an optimized tracking mode to detect whenever someone tries to reach towards and touch a valuable asset like a museum exhibit. It can also be used in any other application where approaching a sterile zone from a more crowded environment shall be detected. The attached tech note describes when and how to use it with FW 6.30.
    View full article
    ‎02-12-2019 02:18 PM
    Object classification takes an object detected and tracked by either Essential or Intelligent Video Analytics, evaluates its geometric and speed properties, and decides whether the object is an upright person, a bike, a car or a truck. The technical note in the attachment provides an overview of object classification, describes how to configure it with FW 6.30, and what the limitations are.
    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
    ‎05-21-2018 08:40 PM
    This will let you call up cameras on an Allegiant monitor output across the network to a remote site.
    View full article
    ‎05-16-2018 09:36 PM
    Related Products Bosch Video Management System   Issue When opening a new Image pane in Live Mode, the camera image is discolored, i.e. there is a green cast or the image is displayed in black and white. When viewing the same camera image with the webbrowser, the live image is properly colored.   Solution Update the graphics card driver. Refer to BVMS release notes: they list the recommended graphics card driver versions to be used. 
    View full article
    ‎05-21-2018 08:46 PM
    Related Products - VJD-3000 Question How to display MPEG 4 video on VIDEOJET decoder 3000 ? Answer No. VIDEOJET decoder 3000 is only capable of decoding H.264 video.
    View full article
    ‎05-18-2018 01:49 PM
    Related Products All IP encoders Answer Copy/Paste the selection below to your alarm task editor and save. This script will make your encoder trip relay 1 only when IVA rule #1 alarm is active. // Set TempState to monostable mode, 5 seconds OperationMode monostable := { High(50) }; TempState(1) := monostable; if (VCARule(1,1)) then TempState(1) :=true; if (TempState(1)) then Relay(1) :=true else Relay(1) :=false;
    View full article
    ‎05-18-2018 11:58 AM
    Configure a singe mode VIF on NetApp array.
    View full article
    ‎05-16-2018 09:31 AM
    Product Security Advisory: Meltdown and Spectre vulnerability in Common Product Platforms (CPP)
    View full article
    ‎02-12-2019 02:17 PM
    The technical note in the attachment describes how to track ships using Intelligent Video Analytics with FW 6.30, how to configure this and what the limitations are.
    View full article
    ‎09-03-2019 01:41 PM
    Dear users, have you ever wondered how to best transition from the Project Assistant to (B)VMS? This article aims at providing you a recommendation and the answer is quite simple: Use the Project Assistant to its full extent and once the cameras are connected to the target network, perform a network scan using the BVMS Configuration Client, to add the respective cameras to the system. The remaining fine-grained settings can then be tackled within BVMS.  For details, please check out the attached presentation. Let us know, if you have further questions and share your comments below. Best regards, Your Bosch Security App Team    
    View full article
    ‎05-21-2018 08:16 PM
    Related Products VRM Question Can I import Direct-to-iSCSI recordings into VRM? Answer No. iSCSI arrays used in Direct-to-iSCSI recording mode must be formatted when imported into VRM.
    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
    ‎05-18-2018 02:03 PM
    Related Products All Bosch encoders running firmware 4.0 and above Question How can I set, clear and check virtual alarms via CGI? Answer  You can use virtual alarms within encoders as a trigger to have other events take place. This is an example on how to integrate 3rd party devices/software to trigger an event to take place on the encoder.  This event could be used to change any variable via ATSL (Alarm Task Script Language) - example below Virtual Alarms via CGI Set Virtual Alarm: http://160.10.92.40/rcp.xml?command=0x0a8b&type=F_FLAG&direction=WRITE&payload=01&num=1 Clear virtual Alarm: http://160.10.92.40/rcp.xml?command=0x0a8b&type=F_FLAG&direction=WRITE&payload=00&num=1 Check virtual Alarm: http://160.10.92.40/rcp.xml?command=0x0a8b&type=F_FLAG&direction=READ&num=1 Virtual Alarms in ATSL if (VirtualAlarm(1)) then Relay(1) := true; if (!VirtualAlarm(1)) then Relay(1) := false;
    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