+++ 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!
When using the BVMS 9.0 installer on a Windows 10 "October 2018 update" machine (Build 1809) the SNMP services cannot be installed.
Microsoft has changed the way the SNMP services are installed in Windows 10 "October 2018 update".
The SNMP services need to be installed manually.
This can be done by opening the new "Settings App“:
Manage optional Features
It can also be done using Powershell:
DISM /online /Add-Capability /CapabilityName:SNMP.Client~~~~0.0.1.0
Status February 25, 2017
BOSCH offers and confirms that since February 2017 the firmware version 3.180.05-1562 can be used with the LSI MegaRAID Controller. In case there are newer versions supported and recommended with BOSCH DIVAR IP this will be announced in cooperation with the Product Management.
For DIVAR IP units (e.g. DIVAR IP 6000) BOSCH BT Security & Safety Systems offers an firmware update for the internal MegaRADI Controller.
It could happen that in the Megaraid Software the user can see potential non-optimal configuration due, PD commissioned as Emergency Spare error.
There is an article as well from hardware partner: http://www.supermicro.com.tw/support/faqs/faq.cfm?faq=19518
Here we provide the steps to update a DIVAR IP system:
Using MegaRAID Storage Manager utility under OS
1) Open MSM, Right click on Supermicro MegaRAID controller to be updated and click Update Controller Firmware
2) Click Browse to search for new firmware
3) Select the new MegaRAID controller firmware
4) Click OK to continue
5) Check the “Confirm” box and click OK to continue
*** Wait for around 1~2 minutes to complete
6) Click OK once firmware update completed
7) Reboot the system and check firmware version in controller OPROM banner during boot. At the section Revision you can see version 3.180.05-1562
😎 Check firmware version using MSM in OS When selecting the "Supermicro SMC 2208 (Bus1, Dev 0) device you can see on the right the "Firmware Version" = 3.180.05-1562
The firmware *.rom filw is available via the following link - inside the ZIP file:
This Firmware Version is subject of change. Any new version must be announce by BOSCH PRM responsible for DIVAR IP via the BT-ST/ETP-MKP2 organisation and BOSCH support at BT-ASA here in the BOSCH Knowledge Base.
The attached document will provide a basic explanation and simple examples of the interfacing (scripting, calling functions by external applications) functionality in Bosch Video Management System. The interfacing functionality is based on Bosch VMS SDKs. The Bosch VMS SDKs contain all interfaces, object types and methods that are needed for automation and integration to and of Bosch VMS.
The document can be found in the attachments section on the bottom of the page or at the right side of the page. Please look for the attachment icon.
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.
In rare situations it might happen that the mirrored SSD drives used for the Operating system need to be set-up from scratch when not only one, but both SSD drives used in the RAID-1 mirrored setup need to be exchanged with two new drives (e.g. Both SSD have been removed or were missing during first install attempt or imaging process from the recovery DVD. It is strongly recommended to always open a Technical Support Case at the local BOSCH Security Systems Level 1 Support team / help desk. Report the the following details to the support: Is the system registered at BOSCH? What is the System Serial-No.? What is the storage capcity of the new inserted two SSD drives at the rear side of the used DIVAR IP 70000 R2 system?
DIVAR IP 7000R2 and DIVAR IP 6000R2
DIVAR IP 6000 2U W/O HDD
DIVAR IP 6000 2U 4X3TB
DIVAR IP 6000 2U 8X3TB
DIVAR IP 6000 2U 4X4TB
DIVAR IP 6000 2U 8X4TB
DIVAR IP 6000 3U W/O HDD
DIVAR IP 6000 3U 16X3TB
DIVAR IP 6000 3U 16X4TB
DIVAR IP 7000 2U W/O HDD (R2)
DIVAR IP 7000 2U 4X3TB (R2)
DIVAR IP 7000 2U 8X3TB (R2)
DIVAR IP 7000 2U 8X3TB (R2)
DIVAR IP 7000 2U 8X4TB (R2)
DIVAR IP 7000 3U W/O HDD (R2)
DIVAR IP 7000 3U 16X3TB (R2)
4000GB HDD DIVAR IP 6000/7000
For recovery of DIVAR IP 6000 R2 or DIVAR IP 7000 R2 one should use only the DVD provided with the particular device. Do not use the DVD for recovery if you are not sure that it is the one delivered with the system. In case the DVD is lost or damaged request the respective ISO image from Bosch Technical Support.
Request the ISO image from Bosch Technical Support:
Provide the Serial Number of the device
What is the reason for the recovery
Why it is not possible to use the recovery DVD
This troubleshooting guide, will guide you through the recovery steps of an DIP, without video data loss
General note: Using a Bosch DIP system without video data disks is a non supported use case, its mandatory to equip the system with data disks to recover the system.
Step 1 - Preperation
Download the attachment repair.zip and unzip the content
Prepare an USB-stick, rename it to SCRIPT
Copy the repair.txt extracted of the attachment on the USB-stick
Insert the USB-stick into an USB-slot of your machine
Insert the BOSCH r ecovery DVD into the DVD-drive
Step 2 - Create RAiD1
Boot the machine and enter the Intel RAiD MENU pressing CTRL + I
Navigate to CREATE RAiD VOLUME and hit enter
Set RAiD level to RAiD1(Mirror), navigate to CREATE VOLUME and hit enter
Exit the RAiD controller, navigate to EXIT and hit enter
Reboot the machine (e.g. press CTRL + ALT + DEL)
Step 3 - System Recovery
During the reboot, boot from DVD, press ENTER as the line will displayed
In the System Management Utility, click on CONSOLE
Type into command line "diskpart.exe" hit enter
Type into command line "list volume" hit enter and search for your USB-stick called SCRIPT, note down the assigned drive letter (LTR)
End diskpart.exe by typing on the command line "exit" hit enter
Type into the command line "diskpart.exe /s [YOUR_USB_DRIVE_LETTER]:\repair.txt" hit enter
Wait until the script has been finished and CLOSE the console
Step 4 - System Recovery
On the System Management Utililty click on SYSTEM RECOVERY (back to factory default)
NOTE: Do not select Initial Factory Setup, this will wipe all existing data!
As the recovery has been completed, click on OK to confirm and reboot
Do not eject the DVD and follow the instructions on your screen to initialize the system.
The attached technical notes give a short introduction to scripting alarm and counter tasks with Intelligent and Essential Video Analytics in FW 6.60. It also provides a broad selection of example scripts for explanation as well as including real world application examples.
Firmware The table below lists the firmware versions which are used in the BVMS 8.0 system test. Bosch Video Stitcher 18.104.22.168 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 22.214.171.124 BVMS SDK 126.96.36.199 RCPP 188.8.131.52 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.
MTU and MSS
MTU stands for "Maximum Transmission Unit."
MTU is a networking term that defines the largest packet size that can be sent over a network connection. The MTU is typically limited by the type of connection, but may sometimes be adjusted IT network settings. The typical value of the Network MTU is 1514 Byte. If a system sends packets over an Ethernet network that are larger than this size, the data will be fragmented into smaller packets. When referring to Ethernet MTU this includes 4 Byte checksum. The 1514 Byte is the interface MTU without the Ethernet Checksum.
In cae there are limitations by the type of connection, the packets will then need to be reassembled on the receiving side (e.g. Bosch video management software or Bosch hardware decoder). However, it can be beneficial to optimize the packet size on the sender side (e.g. IP camera) to the exisitng network infrastructure.
As MTU maximum packet size is layer 1 related, the IP MTU that you can be adjusted at the BOSCH device configuration (Configuration Webpages or with the help fo BOSCH configuraiton software like "Configuraiton Manager"). The BOSCH GUI refers to this as “Network MTU”. BOSCH products can manage fragmented data.
MSS stands for "Maximum Segment Size"
The MSS value is calculated from the MTU. MSS = MTU – (layer 3 TCP header [20 Byte] + Layer 2 IP header [20 Byte]+ Layer Ethernet 1 [6+6+2 = 14 Byte])
For example looking at CPP 6 Platform – like FLEXIDOME IP panoramic 7000 MP in Firmware version 6.50.0128 you can adjust and find the following values:
Network MSS (in Byte) - default value = 1460
iSCSI MSS (in Byte) – default = 1460
Network MTU (in Byte) – default = 1514
MTU and MSS can be adjusted at all released firmware versions 4.x and later.
Here some screenshots as example based on Firmware 06.50.0128
The attached document describes the different components that Bosch Video Management System offers to to establish a connection between Bosch Video Management System and a 3rd party management system. This description helps you in writing your own commands for controlling Bosch VMS from inside your management system.