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 Community

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    Friday
    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. The attached fact sheet lists the cameras that support Camera Trainer. The attached technical note describes in-depth what Camera Trainer is, how it works, what to use it for and what not, and how to configure it. The configuration is also shown in the following how-to videos: Setup Camera Trainer Camera learning phase with recorded video   Configure Camera Trainer Task   Backup Camera Trainer Configuration - Method 1   Backup Camera Trainer Configuration - Method 2 Setup VCA Masking
    View full article
    Thursday
    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
    Monday
    Question What's new or fixed in Project Assistant 1.2.3? Answer This release concentrates on general stability improvements and bug fixes. We could address three findings thanks to your feedback: Keyboards on Samsung devices sometimes got stuck (Android only) Dropbox sync showed unexpected behavior when sharing a project Wireless Connectivity Flexidome IP 8000i: “Camera found nearby – connect” dialog although being properly connected to the camera already
    View full article
    100% helpful (2/2)
    a week ago
    Combined firmware package 6.60 – applicable to all platforms The Release Letter of the combined firmware package for all platforms 6.60.1321 provides information about the dependencies between firmware versions for a better understanding of the upgrade process of devices with older firmware. CCP4 and CPP6 devices: Due to an internal file system being introduced to CPP4 and CPP6 since firmware 6.10 and architectural changes thereof, a direct upgrade from firmware below version 6.10 to latest firmware is only possible via intermediate firmware 6.1x. CPP4 cameras with firmware versions below 6.10 need to upload this package twice. For example, when having firmware 5.92 on a CPP4 device, you need to load the CPP all common firmware file two times: >  First time this is loaded the device will be updated to the 6.11.0021 which is part of the common file. >  Second time you load the common firmware file, the update to 06.50.0128 will be performed. CPP6 cameras with firmware versions below 6.10 need to upload the separate firmware version 6.1x first to receive the latest firmware version. This means that intermediate firmware version 6.1x for CPP6 needs to be requested from your technical support. A support ticket to Level 3 team at MKP PRM group via the support ticket system is needed. In case we see a high demand for that a new combined firmware file might be created by PRM. Only after receiving and uploading firmware 6.1x, you can upload combined firmware package for all platforms 6.50.0620 or CPP6 specific firmware  6.50.0128.  CPP5 devices: This combined firmware cannot be applied to CPP5 products with firmware version older than 5.91. It is required to upgrade to intermediate firmware 5.91 first This means that intermediate firmware version 5.91 for CPP5 needs to be requested from your technical support. Only after receiving and uploading firmware 5.91, you can upload combined firmware package for all platforms e.g. 6.50.0620 or CPP5 specific firmware  6.30.0059. To find a combined firmware file in the downloadstore you can use the folowing URL syntax: https://downloadstore.boschsecurity.com/index.php?type=fw&filter=CPP or you use the CPP 6.50 combined file here: https://downloadstore.boschsecurity.com/FILES/KnowledgeBase/CPP_FW_6.50.0620.fw and Releaseletter of that combined firmware package: https://downloadstore.boschsecurity.com/FILES/KnowledgeBase/Bosch_Releaseletter_CPP_FW_6.50.0620.pdf Note: Upgrading from versions lower than 5.5x To upgrade to a newer firmware version using this combined firmware package, firmware versions before 5.5x require an intermediate update cycle using the respective platform firmware version mentioned above. Restrictions: This firmware and its included platform firmware builds are not applicable to MPEG-4 products. The final firmware version for VIP-X1600-XFM4 modules is FW 5.53. No newer firmware will be provided for these modules. Configuration Manager cannot upload this Combined Firmware file to VIP-X1600-XFM4 modules. Use the module’s web page instead for uploading; or use the separate firmware file. The final firmware version for CPP3 devices is FW 5.74. No newer firmware will be provided for these products. The Combined Firmware file does not load onto VG4 AUTODOME or AUTODOME Easy II via the browser when running a firmware version before 5.52.0017. The specific platform file should be used instead. (Note: In case any link might not work to the current DownloadStore, see attached a copy PDF of the Release Letter.) How to get and request a BOSCH Legacy Firmware: The procedure to request and get an legacy firmware that is no longer online in the web is as follows: Customers are kindly requested to reach out to the local BOSCH Support (L1 and L2 team). Bosch Level 2 will ask for the exact BOSCH Commercial Type Number (CTN). The local BOSCH team can check the Global End of service date. The project background (How many of these devices/cameras) need to be collected.  The relevant BOSCH Technical Support (e.g. Level 2) can explain and check if there is the chance to update the project and included management software in order to be able to use the latest BOSCH device firmware as the goal is to have a non-vulnerable product in productive environments. In case there is no newer firmware available (hardware was discontinued), a commercial hardware upsell can be recommended. In general all firmware that is not available on the product catalog, and for all firmware files that are ranked to have vulnerabilities, this need to be documented in a Technical Support case. In case legacy firmware is anyhow needed and requested by our customers, the Bosch Technical support will start an approval flow. The BOSCH Level 3 Technical Support will provide a form/document that must be signed by the installer/endcustomer. See an example PDF (empty) "Example_Aged_Software_Release_form.pdf" attached to this article. Such a form will be prepared by the BOSCH Level 3 Technical support team and provided to our customer/installer in order to confirm that legacy firmware is then used on the risk of the installer and customer (See text and legal note in the PDF). In the future BOSCH plan to introduce and setup a self-service portal for all customers to simplify this process. ___________________________________________________________________________ The above mentioned combined firmware 6.50 supports: CPP7.3 HD and UHD cameras update from FW 6.40 or newer to latest FW 6.50 CPP7 UHD cameras update from FW 6.30 or newer to latest FW 6.50 CPP6 UHD cameras update from FW 6.10 or newer to latest FW 6.50 CPP5 encoders update from FW 5.91 or newer to latest FW 6.30 CPP4 HD cameras update from FW < 6.10 to intermediate FW 6.11 update from FW 6.10 or newer to latest FW 6.50 CPP3 cameras and encoders update from FW 4.54.0026 or newer to latest FW 5.74 CPP-ENC VIP-X1600-XFM4 encoders: update from FW 4.2x or newer to latest FW 5.53 VJT XF and VJD-3000 update to latest FW 5.97 The combined firmware package includes the following build versions: CPP7.3 FW 6.50.0128 CPP7 H.264 6.50.0128 CPP6 H.264 6.50.0128 CPP5 H.264 6.30.0059 CPP4 H.264 6.50.0128 CPP4 H.264 6.11.0021 CPP3 H.264 5.74.0010 CPP-ENC H.264 5.97.0005 for VJT XF family, VJD-3000 and VJC-7000 CPP-ENC H.264 5.53.0004 for VIP X1600 XFM4 For detailed description please refer to the separate release letters. Customers can upload such combined firmware packages by using multi-select in the Configuration tool "BOSCH Configuration Manager" (currently available in version 06.01.0157 at the BOSCH DownloadStore or Product catalog > Video Software > Video Management Systems > Configuration Manager) When using the multi-select option in Configuration Manager, please make sure this combined firmware package for all platforms can be uploaded to all the devices selected and there are no additional requirements or intermediate steps needed for any of the devices in question. This article has status of 31st of October 2018 and changes in this procedure might be introduced. When changes are done, then this article will be updated. Therefore check this article from time to time.
    View full article
    3 weeks ago
     Time is everything: meetings, public transportation, religion, transactions: the whole world is working because the concept of “time” exists. Within a security (or any other) system this is not different: recording schedules, logging, authorizations, encryption keys, timelines, all of these concepts can exist because of time. As a result, time can either make or break a system: problems can appear only due to a time difference of a couple of seconds between two system components. The attached document describes how time services can be configured in a BVMS environment.
    View full article
    ‎03-29-2019 01:24 PM
      How to identify Hardware errors based on beep codes Relates to: IP Storage/PC HW - DIVAR IP 6000 R2 and DIVAR IP 7000 R2 Both DIVAR IP units running the BIOS from American Megatrends Inc. (A.M.I) There are PRE BOOT or POST BOOT beeps. Please see the following Acoustic Error Codes. Short Beeps Beeps BOOT Description Possible Root Cause 1x short PRE Ready to Start No error   2x short PRE + POST Can´t restore Parity RAM 3x short PRE Errors in the lower memory block (first 64 Kbytes) RAM 4x short PRE System-Timer error Motherboard 5x short PRE Processor malfunction CPU 6x short PRE No RAM installed RAM 7x short PRE Exception interrupt error CPU 8x short PRE Display memory error Graphic card 9x short PRE CMOS/ROM checksum error CMOS battery, CMOS 10x short PRE CMOS read error Motherboard, CMOS-Clear-Jumper 11x short PRE L2 Cache malfunction Cache, CPU or Motherboard Repeated short PRE + POST Problem with the power supply to the motherboard Motherboard Long Beeps Beeps   Description Possible Root Cause 1x long PRE + POST Power Supply error Power Supply or Motherboard 3x long PRE Error in keyboard interface Motherboard Repeated long PRE + POST Power Supply Malfunction: To high or low voltage Power Supply or Motherboard Beep Combinations Beeps   Description Possible Root Cause 1x long + 1x short PRE Fatal Error on the Mainboard Motherboard 1x long + 2x short PRE + POST Video Problem Graphic card malfunction or wrong installed 1x long + 3x short PRE + POST Video Error Broken RAM-DAC (Digital Analogue Converter) 1x long + 6x short PRE Keyboard-Controller malfunction Keyboard 1x long + 8x short PRE Video Memory malfunction RAM on the graphic card 1x long + 9x short PRE ROM-BIOS-Checksum error ROM-BIOS (Battery or Motherboard error) 2x long + 2x short PRE + POST Video error Video-ROM error or video graphic malfunction 3x long PRE Keyboard-Interface or RAM malfunction Motherboard or RAM 3x l + 3x s + 3x l PRE + POST RAM malfunction RAM
    View full article
    4 weeks ago
    Keeping an eye on system messages and to collect logging data at a central site just got a whole lot easier:  Syslog feature is implemented in all IP BOSCH Products for many years. Since latest firmware versions a GUI on the WEB-page of the IP cameras was added. The BOSCH IP cameras as network devices can continuously send system messages via Syslog. This funciton must be activated and configured before as a devinded Syslog IP as destination for those messages must be activated and network administrators need to monitor those data. There are many different monitoring tool on the market. Configuration and technical analysis functions of those are in responsibility of those software vendors. Known tools are PRTG NETWORK MONITOR from PAESSLER Kiwi Syslog Server EventLog Analyzer from ManageEngine and many more. Especially for incidents that happen unpredictable and do not necessarily trigger an alert message can be analyzed with syslog even throughout reboots of equipment (switch reboot / IP camer reboot etc.) as the syslog reconnects to the destination server. As well in cases were many system items are involved this can be very helpful (several switches / many IP cameras involved). By using the BOSCH Configuration Manager or Bosch Configuration Client software can help to quickly setup the syslog function for many cameras in just a few mouseclicks. In current firmware generation 6.xx for BOSCH IP video products a enhanced user webpage to configure loggings that are also sent out via syslog  Event Logging Software Sealing Debug Logging  In case this syslog function need to be was introduced and added. At the Configuration webpages those extra logging can be collected and downloaded. With Syslog logging data can be sent to a syslog server.     
    View full article
    4 weeks ago
    The attached manual provides  information for Mobile Video Service (MVS) within Bosch Video Management System. You can find:  -  how to configure the router and Internet Information Service (IIS) - how to add MVS to BVMS - user guide - some troubleshooting tips
    View full article
    a month ago
    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-17-2019 12:26 PM
    Related Products: BVMS, application crash, memory dump This article lists the scenarios in which technical support normally request dump file from a BVMS system. It contains general guidelines how to create a dump file for BVMS system and provides links to more concrete articles, that correspond to particular issues and exact steps to create a dump. BVMS dumps are needed to troubleshoot the following types of issues: Application crashes – dump is expected to provide more information about the cause of the crash and its origin. Memory or handle leaks – dump is expected to point to their origins Deadlocks, freezes and hangs – dump is expected to point to their origins Recommended tool to create BVMS dumps. The recommended tool is Procdump. It is a command line tool which must be started from the command shell. Development provides couple of .bat files that start Procdump with predefined parameters and cover the most common dump creation cases. The tool as well as the set of .bat files are attached to this article: BVMS_DumpTools_V2.zip The batch file names follow a naming guideline: <Executable>_<Dump use case> , where <Executable> is one of: ConfigClient ConfigWizard OperatorClient ManagementServer ArchivePlayer ExceptionTest and <Dump use case> is one of SingleDump TwoDumps DumpOnException ActivatePostmortemDebugging There are 3 possible error scenarios and corresponding dump creation methods: Dump creation for reproducible crashes that trigger Windows Error Reporting Run the affected application/service (Operator Client, Configuration Client or Management Server Service) Reproduce the steps that lead to the crash Leave the Windows crash dialog open Run the corresponding batch file for creating a single dump: *_SingleDump.bat. E.g. run OperatorClient_SingleDump.bat to create a single dump of the Operator Client process. Provide support with the resulting .dmp file a description of the steps to reproduce the problem ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_onException.zip Dump creation for reproducible memory or handle leaks Run the affected application/service (Operator Client, Configuration Client or Management Server Service) Run the corresponding batch file for creating two dumps: *_TwoDumps.bat. E.g. run OperatorClient_TwoDumps.bat to create two dumps of the Operator Client process. Note that by default, the delay between the two dumps is set to one hour (3600 seconds). Depending on the magnitude of the memory leak, you might want to increase/decrease the delay. To do that, edit file *_TwoDumps.bat: replace value "3600" by a value that fits your needs e.g. a value of "7200" will create two dumps with a delay of two hours. Reproduce the steps that lead to the memory leak. Wait until the second dump was created. Provide support with the resulting two .dmp files a description of the steps to reproduce the memory leak a ConfigCollection Dump creation for crashes/hangs/freezes that are hard to reproduce Deactivate the restarting option for Operator Client / Configuration Client: To deactivate the restarting option for Operator Client / Configuration Client: edit ..\Bosch\VMS\bin\ConfigClient.exe.config or ..\Bosch\VMS\bin\OperatorClient.exe.config. Navigate to section <appSettings> add a new entry <add key = "DisableExceptionHandling" value="TRUE" />. Run ActivatePostmortemDebugging.bat Run the affected application/service (Operator Client, Configuration Client or Management Server Service) As soon as the issue appears, check whether the dump was created. Provide support with the resulting .dmp file description of the steps to reproduce the crash ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_Just-In-Time-Debuger.zip
    View full article
    ‎04-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
    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