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.
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.
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.
The attached documents should help you to make the upgrade process as smooth as possible. The upgrade itself is not restricted to BVMS software only. The supported software and firmware versions can be found in the release notes of the related BVMS version.
An attachment is added to this article for each BVMS version. Currently the upgrade guides for BVMS 8.0 and 9.0 are attached to this article. From BVMS 10.0 onwards a description on how to migrate systems has been included as well.
+++ 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!
The attached document describes the settings you must perform after having installed BIS and BVMS on the different computers. Ensure that the installations of BIS Server and BVMS Management Server were performed successfully on separate computers. Additionally you must have purchased and activated an OPC Server License for BVMS.
The document can be found in the attachments section on the bottom of the page or the right side of the page. Please look for the attachment icon.
Firmware The table below lists the firmware versions which are used in the BVMS 8.0 system test. Bosch Video Stitcher 126.96.36.199 VideoSDK 6.12.0078 Firmware MPEG-4 4.15.0002 Firmware CPP3 5.74.0004 Firmware CPP4 6.41.0037 Firmware CPP5 6.30.0047 Firmware CPP6 6.41.0037 Firmware CPP7 6.41.0037 Firmware CPP7.3 6.41.0037 Firmware CPP-ENC 5.53.0004 (for VIP X1600 XFM4) Firmware CPP-ENC 5.97.0005 (for VJT XF E family, VIDEOJETdecoder 3000) Firmware X1/X2 2.53.0005 VIP XD HD 1.8 VJD 7000 54.8.2 VJD 8000 9.00.0134 VRM 3.70.0056 VSG 6.42.0010 iOS 9.0.2 / 9.3.5 / 10.3.1 Web Client 11.0.96 Software The table below lists the software versions which are used in the BVMS 8.0 system test. BIS 4.3, 4.4, 4.5 DiBos 8.7 BRS 8.10/8.11 Allegiant MCS 2.94 / 2.95 Intuikey Keyboard 1.96 DVR FW Version 2.3.2 (DVR400 / 600) 3.61 (DIVAR 700) 2.5.0 (Divar AN 3000/5000) 1.2.1 (Divar Network/Hybrid) SQL Server 2014 Operating systems Operator Client Windows 8.1 64-bit; Windows 10 64-bit creators update (1703) Config Client Windows 8.1 64-bit; Windows 10 64-bit; Windows Server2012 R2 64-bit; Windows Server 2016 64-bit. Management Server, Mobile Video Service Windows Server 2008 R2 SP1 64-bit; Windows Server2012 R2 64-bit; Windows Server 2016 64-bit. Cameo SDK 188.8.131.52 BVMS SDK 184.108.40.206 RCPP 220.127.116.11 Hardware drivers NVIDIA Quadro Quadro Pro Driver for Microsoft Windows 7/8.1 (64-Bit) 385.08 (28.June 2017) Quadro Pro Driver for Microsoft Windows 10 (64-Bit) 385.69 (21.September 2017) AMD FirePro Unified Graphics Driver for Windows 8.1/10 (64- bit) 17.Q3 (27.July 2017) Bosch strongly urges customers to use the driver and software versions mentioned above. This ensures that the software can perform its task reliably.
Compared to hardware, in which it is relatively easy to define an end-of-support concept based on the expected lifetime, software behaves totally different. In theory, when the environment does not change, software can still be running ten years after it has been installed. As new versions of the software are released regularly, it is important for customers to know what they can expect from Bosch Building Technologies when the software is purchased. This document describes how Bosch Building Technologies handles the life-cycle of the BVMS, BIS, AMS, and APE, and in which state a specific release can reside. Additionally this document lists the up-to-date situation for all of those software packages.
In this article we cover the following basic questions:
How to Factory Default a NetApp E-Seires unit by using BOSCH tools and NetApp WEB GUI?
How to download the NetApp Support Bundle of a reachable online NetApp Storage Array
How to Factory Default a NetApp E-Series that you bought via BOSCH sales channel? Using the BOSCH Configuraiton Manager 6.00 or 6.01 the NetApp models E2600, E2700 and E2800 can be managed. Especially we recommend to use the BOSCH Configuration Manager version 06.01 when using a NetApp E2800 to have all models (also former models E2700 and E2600) supported. Also in the BOSCH Configuraiton Manager 6.01 the Basic configuration for the initial setup is helpful as well as the Factoury Default option and Clear option is available. Of cours the NetApp E2800 offers also a WebGUI by using the IP of the management port of a controller. The following screenshot made from the BOSCH Conmfiguration Manager shows the options available in the tab "Basic Configuration" when a NetApp E-Series (DSA E-Series) is already added to a VRM system in the Configuraiton Manager. The Button "Defaults" is used to trigger the "Reset Storage Array" mechanism of NetApp. At a E2800 all configuration is eliminated but the Management Port IP still remains to ensure that the WEB GUI of NetApp and the communiction of the BOSCH Configuraiton Manager can still work.
How to download the NetApp Support Bundle of a reachable online NetApp Storage Array In the Tab "My Devices" of the Configuration Manager 6.01 and newer versions you can also now download the Support Bundle (collection of logfiles) from a NetApp E2800 stroage system. Select the NetApp E2800 in your device tree that is added to a VRM system and right-click on it. There you find "File Download" and "Maintenance Log..." - Choose that to download the NetApp Support Bundle.
When scanning a QR or Data Matrix code on a label using the Project Assistant app, it can happen that you get an error message that the MAC address cannot be found (1) or that only part of the address is correctly extracted (2).
First of all, there are different types of labels:
product labels (on the device)
box labels (on the outside of the box/packaging)
installer / UX labels (inside the box /packaging)
Symptom (1) can only happen when scanning a product label because some QR or Data Matrix codes do not contain a MAC address, depending on the product, even though the MAC address is available in plain text right next to the code.
The box and installer label codes, however, always contain the MAC address information.
Symptom (2) can happen when scanning certain installer labels due to legacy formatting.
We have further standardized the labels so that the symptoms mentioned above will be resolved. There will be a transition period, however. As an alternative for symptom 1, you will have smooth experience when preferably scanning the box label. If you encounter symptom 2, we ask you to enter the MAC address manually or use the December 2018 release of the Project Assistant (version 1.2)
PS: For full transparancy on QR code / Data Matrix content and/or troubleshooting purposes, you can use conventional code scanning apps available in the resepective app stores.
BVMS Lite is a BVMS edition which can be downloaded and activated free-of-charge. How can I set-up a basic (live and recorded video) BVMS Lite system?
First, you need to download the software package, active the BVMS Lite license and install the software. This is described in this article: BVMS - Activating a license.
Second, you need to prepare an iSCSI environment which is suitable for recording video. Any Windows Server based operating system will do. This is described in this article: BVMS - Configuring a Microsoft iSCSI target.
Last, you need to add cameras to the system and start the recording. This is described in this youtube video: How to add a new camera using Configuration Client (BVMS).
Now, have a look at the Operator Client quick guide and you're ready to go!
Where can I get more information on advanced functionality?
Once the software (configuration client or operator client) is running you can press F1 at any time to open the embedded software help! All of the advanced functionality BVMS offers is explained in the help files.
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: