About Central_Support

Question   What is it required for offline troubleshoot in case of false alarm in the IVA rules from cameras?   Answer   The VCA task editor can be used for easy analytic configuration or for troubleshooting. In case of false alarm in the IVA rules from one of the cameras, to troubleshoot offline (without traveling to the site) the following is required: 1. Exported video using VRM Export Wizard How to export VRM recordings of cameras & convert them to mp4-file (VRM eXport Wizard 2.0)? How to export VRM recordings of cameras & convert them to mp4-file (VRM eXport Wizard 2.10)? 2. Copy the script with the VCA Task Editor from Config Manager -Paste the script to a notepad text file 3. Send 1&2 to the system integrator or the person who will help to improve the IVA config.  Note Export with native format from BVMS does not have IVA metadata. Also, .mov or .MP4 or .wave etc format do not have IVA metadata.   Is it possible to offline troubleshoot analytic task in BVMS Operator Client?   Yes! An installer doesn’t need to travel to customer's site for fine tuning the configuration, when a Camera Analytics task brings false alarms.   Get some playback, use forensic search to fine tune the tasks and transfer the Task syntax (copy it) to the camera VCA settings.   Get forensic search task rules transferred into the camera for further live alarm purpose   1. Operator Client forensic search image: Right click on the image: Advanced → VCA task editor   2. Copy the script text complete as it is.   3. Paste into new text file on desktop (save copy) 4. Paste into Configuration Manager on Task config page, right click again Advanced –> VCA task editor. 5. Save, and verify tasks for live alarming.   How to copy your analytic task with the VCA Task Editor in Configuration Manager?   Refer to this article: How to copy the IVA configuration?   Troubleshoot analytic task in BVMS Operator Client   Open BVMS Operator Client. Click on Playback and then load exported video Click on the forensic search icon. Right click anywhere on the image and go to Advanced -> VCA Task Editor Paste the copied code from Configuration Manager (How to copy the IVA configuration?) Now you can troubleshoot the analytic setup remotely and during a different time of day ... View more

Question   What is the difference between individual & common search: Multi-camera Forensic Search (BVMS>=12.1)?   Answer   Common search Individual search Use cases find (any) person appearing for the selected cameras in a selected time range find a car (with specific color) entering the parking lot Use cases find a person appearing in the selected zones (ie. next to any entrance/exit), that might be different per camera find a car moving on a specific street, observed by multiple cameras Mode 1: Common camera search common search task (or tasks) can be configured for all the open cameras the same search parameters will be used for all the cameras search task needs to be configured only once Mode 2: Individual camera search search tasks can be configured separately for each camera (ie. different line crossing tasks per camera) all combined into a single searching process and results Video: One search task applied to multiple cameras (whole image): Video: Each camera can get an individual search task: ... View more

Adding cameras to a completely new green field BVMS installation, or to existing systems requires some manual configuration steps. The new feature allows to reduce configuration effort for larger amount of cameras. A csv (table) file including IP-Addresses, camera names, credentials, Logical tree assignment and related user group access can be prepared in advance. This file can be imported to the Configuration Client in one shot for 250 cameras by using the new csv (table) file mass configuration feature. New menu option "Import from csv file" available when right clicking on a VRM pool within the Device Tree of the Configuration Client. The option is not offered for Live only or Local storage cameras.  A csv template is provided in the samples folder of the BVMS 12.1 installation path.   A template for csv import can be found after the installation of BVMS 12.1 here: C:\Program Files\Bosch\VMS\Samples\MassConfigurationTemplate.csv Or download it from here.   Step-by-step guide   CSV file column explanation:   All columns should be defined in header line of the csv file NetworkAddress- IP address of encoder, cannot be empty and cannot be duplicated. EncoderName- Name of encoder to import, cannot be empty. CameraNames- Name of cameras of current encoder, cannot be empty.  Multiple cameras should be separated with a semicolon. UserName - User name for authentication to encoder, can be empty. Password - Password for authentication to encoder, can be empty. LogicalTree - Paths in logical tree where cameras should be added.  Multiple paths should be separated with semicolon.  If the value is empty, then the cameras are not added to the logical tree.  The "/" is only mandatory for the root node, for other folders it is optional.  The root node name should not be added to the folder path.  If a path does not exist, it will be created. Permissions - Permitted user groups.  Multiple user groups can be separated with a semicolon.  If the value is empty, then the camera can be accessed for all groups.  If non of the operators should have access to the camera, then only "Admin Group" should be specified. In the following case the Usergroup permission cannot be set: Column User group= value given. Column Logical tree= empty. This is because permission can be given only to cameras available in the Logical Tree.    Rules for csv (table) file creation: The delimiter between columns must be a comma. Semicolon delimiter does not work!  Excel uses the operating system's list separator to determine the default delimiter for CSV files. In English-speaking countries, the default list separator is usually a comma (",") while in many European countries, including Germany, the default list separator is a semicolon (";"). Different values within one column can be separated by using semicolon (e.g. User groups: UG1; UG2; UG3; UG4 250 devices can be imported with one single run (file). Several files can be imported one after the other.   It must contain the header line with all correct column names Import will fail if mandatory fields are empty: NetworkAddress, EncoderName, CameraNames User Groups listed in the csv file must exist before import Already existing devices cannot be overwritten (same IP-Address) Multichannel encoder cannot be added when devices are offline. However, Encoder with only one line (analog camera) can be added when online as well as offline, using the csv import. It is possible to add cameras to classical maps (not working for HERE maps). In this case the cameras are added with status "invisible" on the map. After the import, further manual configuration steps are required such as setting to "visible" and correct positioning on the map.   Working with Excel, csv file delimiter: comma The list separator (comma or semicolon) used by Excel when saving a csv file depends on your Windows OS regional settings.  For example, when selecting English US in the regional settings, the list separator comma is used by default.    Note Many European countries, including Germany, the default list separator is a semicolon (";"). Importing a csv file with delimiter semicolon does not work!      Once the .csv file is prepared, you can start importing cameras from it:     Save    Go to Maps and Structure > here you will see all cameras imported under the Logical Tree   If you have more Operators, do not forget to grant them permissions from the User groups menu to the cameras they are allowed to use   ⚠️ Import failure report:   Import report example for some Failure entries of the csv file in order to show what should be avoided when creating a csv file. The cameras marked with "Failure" in the report will be skipped during the import process. Therefore, you have to recheck the csv. file to avoid empty fields for example and adapt it to be imported again correctly.    If the information column is not completely visible or if you want to keep the Failure information for future reference, you have the option to Export log and there you'll see the cause of not importing specific cameras: ... View more

Question   Where to locate the individual CPP14.1 and CPP14.2 packages for Firmware v9.00.0210?   Answer   Starting from Firmware v8.80.0090, the file for all CPP14 sub-platforms are now unified into a single file. Which means that you can use the CPP14 v9.00.0210 unified file for the upgrade of the CPP14.1 products. Changing the infrastructure of the Firmware in a single file was done to avoid confusion among customers while deciding which Firmware to upload. The CPP14 v9.00.0210 and the latest firmware can be found on the DownloadStore or in the product catalog of the cameras/ devices, e.g. CPP14 FW v9.00.0210 can be found on DINION 5100i IR product page   Please refer to the release notes for more details: Bosch_Releaseletter_CPP14_FW_9.00.0210.pdf   Stated in Bosch Release letter CPP14 FW 9.00.0210:   Downgrading from 9.00.0210 to a prior CPP14-compatible firmware requires secure boot alignment. With various previous versions featuring different bootloaders, identifying secure boot compatibility can be challenging. Importantly, attempting to upload an incompatible file poses no harm, as the downgrade process mandates proper secure boot verification. To address potential issues, proceed with the downgrade attempt, and if compatibility problems arise, contact Central Technical Support for guidance on obtaining the correct firmware files.   Details: FW 9.00 has a major architectural changes. FW 9.00 will now be consolidated into 1 file, CPP14. CPP14.1 and CPP14.2 will no longer be available, both will be combined in the CPP14 file.   Upgrading to 9.00 or higher: All CPP14 cameras must pass through FW 9.00 before being upgraded to any FW higher than 9.00. CPP14 will not allow any camera to upgrade until 9.00 has been loaded first.   Downgrading passed FW 9.00 to FW lower requires a special version of FW: CPP14.1_FW_8.80.0090_bld.fw Multi 7000i (IR) CPP14.2_FW_8.80.0090_bld.fw All other cameras CPP14.2_FW_8.81.0037_bld.fw FLEXIDOME corner 7100i IR DINION 5100i IR DINION 7100i IR AVIOTEC 8000i IR   Nice to know: Bosch Video support - Firmware and Software requests ... View more

This article applies to cases such as: The target appears as not connected in the Server Manager, even if the Microsoft iSCSI Software Target service is running.  The target becomes connected only after a service restart.  When you restart the DIVAR IP, the problem returns until you manually restart the Microsoft iSCSI Software Target service again.     Step-by-step guide   You could try the below steps to create a Task using Task Scheduler from MS Windows: 1. Create a CMD File „StartISCSI.CMD” using notepad and add the below 2 lines timeout 60 net start WinTarget   2. Search for the Task Scheduler App in the Start menu and open it   3. Click on "Create Task..."   4. Create a task to run StartISCSI.CMD on startup by configuring the Task as in the following Print Screens (follow the check boxes).  Make sure that you choose the right compatible Windows Server OS version running on your unit from the drop-down list and configure the task to start even if nobody is logged on yet:   5. Setting the Microsoft iSCSI Software Target Service to Manual    6. Restart the Server 7. Now the ISCSI Target starts up on its own without any user intervention Test results had positive results and worked on our laboratory environment on DIP-73xx and DIP-72xx. ... View more