About Central-Support

 Find attached the FRENCH version of this article!   The DIVAR IP System Manager application includes a dedicated script that simplifies the log file collection for DIVAR IP all-in-one 4000 & 6000 & 7000 gen4.   Step-by-step guide     1.  Sign in to the administrator account To sign in to the administrator account in BVMS operation mode: On the BVMS desktop, press CTRL+ALT+DEL. Press and hold the left SHIFT key immediately after clicking Switch User. Press CTRL+ALT+DEL again. Select the BVRAdmin user and enter the password that was set during the system setup. Then press ENTER.        Note: To go back to the BVMS desktop, press CTRL+ALT+DEL and click Switch user or Sign                        out. The system will automatically go back to BVMS desktop without a system restart.          To sign in to the administrator account in VRM or iSCSI operation mode: On the Windows sign-in screen, press CTRL+ALT+DEL and enter the BVRAdmin password.   2.  In order to collect System Manager logs easily, a script is added to the DIP44/64/74’s Start Menu, called “Export System Manager Logs”:   3.  After running this script, the resulting ZIP-file can be found in: C:\Users\Administrator\Documents\Bosch   The logs gathered in the ZIP-file are as follows: • DIVAR_IP_System_Manager – Installation logs for System Manager • DivarIP – Installation logs for the DIVAR IP AIO’s other software • SysMgmService – Logs copied from C:\ProgramData\Bosch\SysMgmService\log • _DriveInfo.txt – Details about the storage on the DIP • _ProcessInfo.txt – Details on currently running processes • _ServiceInfo.txt – Details on currently running services • _SystemInfo.txt – Windows System Information These files can provide the basic information needed to figure out what happened if a package fails to install or if there are other issues during installation. The ZIP-file is not encrypted and all log files are plain text.    The most System Manager Logs used are the following: • localui.log – any logs from the local UI itself. The start of the process is always finding the installation files on the system. Any trouble in this regard will be reported in this log file. If there are any issues while detecting files or initially validating files, it will be found in this log. • sysmgm-commander.log – backend communication log. Checking any status changes within this log can be helpful to see where in the installation process incidents occur. • sysmgm-executor.log – execution of installations log     Nice to know:   How to get the BVMS Configuration Collection Logs of the system?   💡  For a better understanding of using DIVAR IP AIO 4000 & 6000 we encourage you to join our free online Training from Bosch Building Technologies Academy!   ... View more

Question   Which is the max. iSCSI recording sessions of DIVAR IP AIOs?   Answer   Available details for recent DIP AIOs:     iSCSI sessions iSCSI sessions are the connections from a device to the iSCSI target. There is a limit to the amount of sessions that can be made to an iSCSI target, the limitation is determined by the Microsoft iSCSI target of the operating system, and the hardware which is used for that device (CPU and memory load), as well as the limitations of the software running on the system; VSG, VRM-based recording, BVMS decoding. Each device recording to an iSCSI target, uses one iSCSI session. If a Workstation plays back one or more streams, either through VRM, or direct iSCSI connection, this also uses one iSCSI session per connected Workstation. If instead of VRM playback, direct iSCSI playback is configured, each workstation connecting to the iSCSI target will take one iSCSI session each while playing back.   Nice to know: For a better understanding of using DIVAR IP AIO 4000 & 6000 we encourage you to join our free online Training from Bosch Building Technologies Academy! ... View more

A calibration of the scene is required. If the scene is not well calibrated, it's most likely to receive wrong or no results.   Step-by-step guide   1. Open Configuration Manager and select the camera prepared for this configuration. Authenticate on the camera with its credentials 2. Go to VCA tab > Main Operation Under Operating Mode option > select the profile where the VCA will be configured Under Pre-position option > select 1 3. Go to the Tasks tab   PREPOSITION 1:   (A) Click the + button > (B) select the Trigger and (C) give a name to the task and click the (D) “>” button > (E) Define and draw the fields as you wish and click (F) Finish button once done.   Hint: To add a new field, please click on the drop-down menu and select the option “New Field” Your task will be displayed under the “Task configuration” list. Do not forget to save your configuration!   PREPOSITION 2: Under Pre-position option > select 2 Go to the Task tab Repeat the A,B,C,D,E,F steps from above. Your new task will be displayed under the “Task configuration” list. Do not forget to save your configuration!   🛈  IMPORTANT Please note that the maximum TSL script size is maximal 2000 bytes.  Be aware that the following error message might occur if the script size is exceeded: Why is the error in the pink box when accessing VCA Tasks & Metadata Generation (Config. Manager)?   How to check the size? Note that this is the size when compressed: Option 1 > via VCA task editor Option 2 > Save the script in a notepad and zip this     Useful video:   ... View more

Possible causes and solution(s)   Causes   There might be situations where MIC IP fusion 9000i or Bosch INTEOX cameras cannot write calibration to camera in Configuration Manager (VCA profile and Pre-position). When trying to write the new calibration to the camera, it fails, and the following message occurs: "Calibration upload has failed." This behavior was encountered in: Configuration Manager v7.50/ v7.51/ v7.41 with CPP13 Firmware 8.41.0029 INTEOX cameras Configuration Manager v7.40.0069.0 with CPP7.3 Firmware 7.80.0128 MIC IP fusion 9000i cameras   Solution   Upgrade Configuration Manager to version 7.61.  ✅  Configuration Manager 7.61 is released and available online in Download Store. Download Configuration Manager v7.61 from here Configuration Manager v7.61.0143 Release Letter This must be used in combination with CPP13 Firmware 8.45 or later     ... View more

Possible causes and solution(s)     DHCP lease time is set to 5min Camera requests and acknowledgment should be after 2,5min     Causes   During a Wireshark capture, it was noticed that Bosch CPP7.3 Camera with FW v7.85.0016 does discover, offer, request and ACK. After that, there is no communication anymore with the DHCP server for several minutes.   Since DHCP is not refreshing / DHCP requesting anymore, the **DNS is also losing hostname from the camera. **DNS is filled by DHCP server When the camera is rebooted, DHCP discover, offer, request and ACK are done again (once) and camera is working until it is removed from DNS again, since DHCP fails to renew / Request after 50% lease time.     Solution   Upgrade your camera to FW 7.86.0019 and perform a factory default (access Download Store here). The time effort to fix this in older FW will be planned for early March 2023. ... View more