About Central_Support

TDR (Time-out Detection Recovery) activated on Z4G4 workstations with T1000, RTX A2000 or RTX A3000 graphical cards   Possible causes and solution   Cause   Use workstation MHW-WZ4G4-HEN4 with RTX A2000 or MHW-WZ4G4-HEN2 with T1000 GPU to run BVMS on it. TDR (Time-out Detection Recovery) feature is activated in case that opening many cameos would overload the system. Below blue screen is showing with Stop code VIDEO TDR FAILURE. Restart PC.   Solution   Enable the hardware-accelerated GPU scheduling feature in Windows 10. This will enable the system to avoid the time-out detection recovery feature which can be activated when opening higher numbers of cameo. To turn on the hardware-accelerated GPU scheduling: On the Windows Start menu, select Settings, and then select System > Display. Under Multiple Displays, click Graphics settings. Set the Hardware-accelerated GPU scheduling to On. Restart your computer. ... View more

General Advise to first update to the latest available fw Some cameras received an enhancement on the behavior of the day-night switch slider in later firmware to prevent it might get stuck in night mode. - 7.86.0019  and higher >  AUTODOME IP starlight 5100i (IR)  - 7.89.30 and higher > Flexidome 8000i   Below article is applicable to all Bosch cameras Why does this happen The camera has a mechanical IR-Cut filter, which typically switch 2x a day, 1x at sun-rise and 1x sun-set. This can off course be more as long as it is within a reasonable amount, and interval. When the camera operates in automatic Night-Mode and the switching interval is too fast the camera built in protection mechanism will intervene to prevent premature wear of the mechanical IR-Cut filter. you recognize the intervention of this security measure when the Night-to-Day slider has increased. It will automatically increase each time with +1 till a max of +15 ones it has reached +15 the camera will permanently stay in Night-mode This protection mechanism will intervene each time when N>D happens approx 4x within 2 minutes, or 2x short after each other. Some used cases where the intervention of this security measure can happen: Camera is used in an environment where visible-lights sources are switching On/Off e.g. with an external motion sensor (PIR), and the light-source time-out is to short causing multiple switches in a short time Cameras are outdoor, for example next to a highway or road and headlights causing the camera to switch to Day-Mode A non-IR camera is used in combination with IR-Illuminators A non-IR camera receives streaking IR light from neighbor IR-Cameras   Solutions: Switch permanent to Night-mode (monochrome) makes most sense for camera with built in IR because otherwise IR will never turn on Switch Permanent to Color-mode, especially for well lit environments during the evening this can be a good option due to the good light sensitivity of the Bosch Cameras For moving cameras, avoid passages between pre-sets that might contain enough light to trigger a N>D switch over Ensure and extend in case needed the time-out time for automatic switching visible-light sources to at minimum 40sec if these are close to the camera as well in the FoV Wire the External-Motion-Sensor (PIR), External-Day/Night-Sensor or External IR-Light source to the camera input, and use this input as Night-mode trigger. Warning: This method bypasses the built in protection mechanism and therefore stops the increase of the Night-to-Day slider. Extra caution is required to ensure that not more than 10 switches per day take place to prevent premature wear When a NON-IR camera is used in combination with an External IR-Light source, or nearby IR-Cameras, connect the IR-source trigger to the NON-IR camera input, and use this input as Night-mode trigger. Reason why this happens: A Camera with built-in IR makes use of an additional built-in ambient-light-sensor (ALS) with IR-block-filter to detect only visible light so it knows when to toggle night-mode. NON-IR cameras don’t have this sensor and toggle night-mode based on the light on the Image-Sensor. So if a neighbor IR-Light source streaks into a NON-IR cameras the IR acts as visible-light as in night mode the IR-Cut filter is no longer in front of the Image-Sensor. Warning:This method bypasses the built in protection mechanism and therefore stops the increase of the Night-to-Day slider. Extra caution is required to ensure that not more than 10 switches per day take place to prevent premature wear Manuals says, when a NON-IR camera is used in combination with an External IR-Light source:   There is also a possibility to use a script as solution, in order to allow this you must first evaluate the camera log from a full day cycle and count the amount of “Night mode” changes this should not be more than 10 per day See attached script to be copy/paste in the camera "Alarm Task Editor":  Prevent Night-to-Day slider to run-up by keeping the camera at minimum 40sec in Night-mode before back to auto-dn.txt Warning:This method bypasses the built in protection mechanism and therefore stops the increase of the Night-to-Day slider. Extra caution is required to ensure that not more than 10 switches per day take place to prevent premature wear Side-note Each IR-Cut filter switch cycle is logged in long term log. Early failure due to abnormal amount of switching during the camera total operation time, can have warranty consequences. Therefore, better please prevent excessive night-mode switching by selecting one of the above solutions ... View more

Possible causes and solution(s)   Causes   Certain services in Remote Portal are activated (e.g. Alarm Management, AI Alarm Verification, Cloud Storage). However, the cameras in Alarm Management cannot use those services. How to solve this?   Solution   Activated licenses are recognized during commissioning a camera from Remote Portal to Alarm Management. It might occur that recently activated licenses are not recognized by Alarm Management yet, and the cameras cannot be used in the related services in Alarm Management (e.g. Live Intervention, AI Alarm Verification, Cloud Storage, etc.).   To solve the issue, please perform the following steps: In Alarm Management Configuration > Devices tab, open the dialog to add a Remote Portal camera. Enter your credentials and click button “Login to Remote Portal” > the connection to Remote Portal gets activated and new licenses are recognized in Alarm Management. Click button “Cancel”. Now the recently activated services should work in Alarm Management.     The issue will be fixed in a later Alarm Management version. ... View more

Possible causes and solution(s)   Causes   After upgrading the camera firmware to version 7.81.0060 and higher, the camera display name become smaller in the font size. This is observed in CPP 6 and CPP 7 Bosch IP cameras. It is not possible to increase the font size of the camera display name for CPP 6 and CPP 7 Bosch IP cameras as this is capability is only implemented for CPP 7.3 Bosch IP cameras.   DinionIPultra8000MP_CPP6_12MP&4K (FW 7.82.0025):     DinionIPultra8000MP_CPP6_1080p (FW 7.82.0025):     Solution   This behavior where the OSD font size is too small (half height) when resolution is set to 1080p or higher is now fixed in FW version 7.85.0016. If you still encounter this OSD resolution issue, please upgrade your camera to the FW 7.85 or the latest one available on the Download Area webpage.   ... View more

Important to know: Before VSG 8.0, there was 1 Connector (Proxy) instance/service and multiple Worker instances/services (1 - 7) Since VSG 8.0 there is now a Connector (Proxy) instance/service (1 - 7) per worker instance/service (1 - 7) The normal process is to enable Complete memory dump, this will capture in the event there is an Unhandled Exception.   Step-by-step guide   Via BVMS CC: Would be needed to enable for each instance   Via CM: Would be needed to enable for each instance   If in the event that the crash is due to a "Memory Leak" this would cause also all other applications also to crash due to all the memory on the sever to be consumed by 1 application. So the normal way of collecting the dump files would not work as there is no more  memory available for the application to generate such a dump. In this case you should contact technical support for additional instructions how to create a dump file.   ... View more