This article explains how to use the settings as per the devices current configured capabilities if you just added a device to BVMS, you get the possible stream options as per a “Config table” known to BVMS.
If the Host Type was set to other value than “Factory Default” for DSA E2800 and you want to integrate it with BVMS, the targets will most likely not be scannable and there will be no recordings at all.
In order to quickly offer a technical solution or to provide a professional advice for the next analysis steps, the technical support specialists need to get some general and basic information.
Ticket content should always be in English and provided in a well summarized and structured way in order to be able to provide a quick and appropriate feedback.
Not following the guideline will impact the processing time of the ticket.
Related Products: BVMS Operator Client
This article describes the initial steps one can take for troubleshooting BVMS display issues (during live view or playback). It also summarizes what initial information and logs are needed for support in order to start the issue investigation.
How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status?
BVMS stand alone or appliance
Detailed problem description
Check and eventually update the version of your Graphic Card driver.
During BVMS system tests there were documented cases of display issues related with out of date Graphic card divers. ❗ It is important that the Graphic Card driver of the client is up to date. Find the supported version of the Graphic Card driver in the corresponding to your BVMS version Release Notes (https://downloadstore.boschsecurity.com), in the section Hardware drivers.
Symptom specific Information
Is the issue camera type / FW dependent?
Are all the devices in the system affected?
Is the issue existent for all BVMS Operator Clients in the system?
Is the issue existent for hardware decoders, for camera Web Interface or other display Clients?
Is the recording, the playback or are both affected?
BVMS ConfigCollector logs keeping the following conditions:
From the machine that shows the issue
VSDK logging – please follow the steps from the article:
How to collect Video SDK log files
VRM logs (in case VRM runs on the same machine like the BVMS MS, then BVMS ConfigCollector logs from the server)
for VRM version 3.82 and onwards use VRM Monitor. The following articles will help you out:
How to access VRM monitor from BVMS Configuration Client?
How to collect VRM logs with VRM Monitor (v3.82/ v3.83)?
Screenshot of the Dashboard of the VRM
for VRM version till 3.81 - contact support to receive BVIP Log collector tool and use it to collect VRM logs
Movie showing the display artefacts can be helpful