About Central_Support

Step-by-step guide   The RCPP command to enable/ disable the privacy masks - CONF_PRIV_MSK_POLY - 0x0bd8   Fixed cameras: the command does not have simple ON/OFF feature for fixed cameras. So first one should request the current privacy mask configuration using the READ mode of CONF_PRIV_MSK_POLY - 0x0bd8 to disable use the payload from the READ command and disable the privacy mask in question.  http://camera_ip/rcp.xml?command=0x0bd8&type=P_OCTET&direction=WRITE&payload=0x0008000000808080001c000100000400000000002d530c512d532c684d382c684d380c51001c000100010400000000005f4419c07f2919c07f2980005f448000    Read out the existing mask setting first: http://160.10.11.174:80/rcp.xml?command=0x0bd8&type=P_OCTET&direction=READ&num=1 There are 8 masks. Change the value to 00 to disable and 01 to enable Note: 00/01/02/03/04/05/06/07/08 → refer to the privacy mask ID Need to have the rest of the payload included as this will keep the polygon shape during toggling    Moving cameras: MIC IP starlight 7100i → Mask OFF: http://160.10.110.167/rcp.xml?command=0x0BD8&type=P_OCTET&direction=WRITE&num=1&payload=0x000C00030100000000000000   MIC IP starlight 7100i → Mask ON: http://160.10.110.167/rcp.xml?command=0x0BD8&type=P_OCTET&direction=WRITE&num=1&payload=0x000C00030000000000000000   Note: In this case in the camera WebInterface, under Settings-Camera-Privacy Masks, there is a Disable Masks check box ... View more

When a FLEXIDOME multi 7000i (IR) or FLEXIDOME panoramic 5100i (IR) does not boot up or is unresponsive.   Possible causes and solution(s)   Symptoms   The symptoms that you will see is the camera is not able to boot up and is unresponsive. If the Status light next to the reset button stays red or has any other abnormality.  In this situation the Status light behaves the same even after a factory default, by pressing the reset button for over 15 seconds. Normally a camera will operate as below. The Status light should start as Red while booting, then should change to Green after the boot process finishes Affected cameras FLEXIDOME multi 7000i, FLEXIDOME multi 7000i IR. if the cameras have been operating using FW lower than FW 8.71 (FW 8.71 safe to use). FLEXIDOME panoramic 5100i, FLEXIDOME panoramic 5100i IR.  if the cameras have been operating using FW lower than FW 8.70 (FW 8.70 safe to use).   Causes   The old FW (listed by camera above) is incorrectly using the memory and is causing unrecoverable wear out to the memory. Causing the camera to no longer reboot and leaving the camera entirely unresponsive. The fix was made to protect the camera from experiencing this type of memory issue. Development had noticed this problem in 2022 in their lab and thus made a fix early in 2023. But due to not fully understand the long-term ramifications, the FW continued to be available. The affected FW has now been removed from the Bosch Download store.   Solution   Bosch always requires the customer to upgrade their cameras to the latest FW. Because bugs like this are found and fixed, and if not updated, can cause permanent damage to the cameras. If a camera experiences has experienced these symptoms, there is no solution, camera will need to be replace.  To protect the cameras that are still operating. The customer needs to immediately upgrade their camera(s) to the latest FW. Details of the FW related to this memory issue. For the FLEXIDOME multi 7000i (IR) - FW 8.71 is where the memory issue was fixed. The first camera from production with the fixed FW was SN: 404732537614033358. For the FLEXIDOME panoramic 5100i (IR) - FW 8.70 is where the memory issue was fixed The first camera from production with the fixed FW was SN: 404706337415070019. ... View more

Question   Can the cameras added to DIVAR Network to record on VRM in DIP 7000 AIO (central BVMS server)?   Answer   If you have for example a DIVAR 7000 AIO as central BVMS server and also, on the same network, you have a DIVAR Network Video Recorder (NVR) to which cameras are connected to and recording, the recording is typically handled by the NVR itself. Therefore, in this case the cameras added on the NVR will continue recording only there because the NVR manages the recording and storage of video footage from them. The Bosch Video Management System (BVMS) on the DIVAR 7000 AIO can be used to view cameras connected to the DIVAR NVR by adding the NVR in the Devices menu from BVMS Configuration Client. By activating after adding it to the Maps and Structures, users can access and view the cameras through the BVMS Operator Client. The cameras will appear with a green dot and a label mentioning that the NVR is handling the recording.   ⚠️ In order to let recording be handled by the DIVAR 7000 AIO, the cameras need to be added directly into VRM.   If the cameras are connected to the NVR only for live purposes, and in the same time you want them be added to the VRM for recording, please note that the BVMS system was not designed for such implementation and therefore we cannot recommend it. 💡  Regarding viewing the cameras, when the DIVAR network is added into BVMS, please see the article below: How to add my DIVAR Hybrid 5000 in BVMS Viewer and see Live image of cameras connected to the DIVAR? ... View more

Possible causes and solution(s)   Symptoms   MVS gets error message “Videoprovider not available” when trying to log on. Also, the BVMS Configuration Client shows the X mark on the MVS.   Solution   Try to deactivate IPv6 and remove/ re-add the MVS to the BVMS Configuration Client again If the issue persists, remove and reinstall the MVS part only in BVMS Check if there is the possibility for a Virus Scan Software or the Firewall to block the BVMS ports. All the BVMS internal ports need to be allowed for communication All involved units must be reachable via DNS Hostname and IP address among themselves. Therefore, please check if DNS is working correctly and BVMS and MVS can be reached via Hostname and IP. Edit the Windows hosts file and add MVS Edit both “host” files from the folder Windows\system32\drivers\etc IP_of_MS Hostname_of_MS IP_of_MVS Hostname_of_MVS   In the MVS PC, add a new entry at the end: In the MS Server, add a new entry at the end: Restart the IIS and then the MVS services (all 4 services) make sure that there is no other application using IIS (e.g., Intelligent Insights also uses IIS) Be sure that Microsoft .Net Framework 3.5 and 4.6 are installed on the MVS server. Please also see from the configuration manual the used ports section and open them, especially the Management Server and MVS: configuration_manual_en (azureedge.net) If all necessary MVS ports are open and not blocked and the issue persist à check if there is a certificate selected in the https bindings. Per default this should be "BoschVMS". The instructions how to check this, you can find in - https://resources-boschsecurity-cdn.azureedge.net/public/documents/Mobile_Video_Service_Technical_Service_Note_enUS_9388559115.pdf Page 15, section Adding the HTTPS binding Try to create the https binding for the specific MVS IP in the IIS settings (in BoschIVS and not in the Default Web Site😞 Try to delete this file (C:\ProgramData\Bosch\MVS\Config\XmlDataStorage.xml) and restart all MVS services(especially the "Bosch MVS Data Storage Service" is important).    In case there is no solution to the issue after checking all the steps above, further investigation with the Central Technical Support team is needed and the logs are very much necessary to understand what's going on on the installation. Therefore, before contacting the Central Technical Support team, be sure that you have collected the Config Collector Logs and you will provide the support team with all the steps already preformed by you before reaching them. How to get the BVMS Configuration Collection Logs of the system?   ... View more

RPS/RPS LITE v6.14.100 firmware upgrade wizard fails during control panel update   Technical Bulletin   RPS/RPS LITE v6.14.100 firmware upgrade wizard fails during control panel update February, 2024 Issue Some customers may encounter failures when attempting to upgrade or downgrade a control panel using the RPS Firmware Update Wizard in RPS/RPS-LITE v6.14.100. The update process will begin to process and then fail, stopping with a Could not update firmware error message. Also corrects GV4 Receiving Error "Data for some of the items have been corrupted during receiving". Customer Impact Customers that have upgraded their current RPS install to RPSv6.14.100 will most likely NOT encounter this issue. Customers that are installing RPSv6.14.100 on a PC for the first time, may encounter this firmware failure issue due to a missing Microsoft Windows C++ redistributable package. This is due to the RPS CRC check functionality failing. RPS uses standard Windows dll runtime libraries for the CRC check. Microsoft provides the required libraries as part of the Microsoft Visual C++ 2005 Redistributable package. If the package is not installed on the machine running RPS/RPS LITE v6.14.100, the failures will occur. Resolution Visit Bosch.com for the Microsoft Visual C++ 2005 Redistributable package to install on the machine running RPS: https://commerce.boschsecurity.com/us/en/Remote-Programming-Software For technical issues contact the Bosch Central Technical Support Team.  ... View more