About Central_Support

Overview of the Integration 1.1 Introduction In many camera systems installed for observation and or security purposes, the camera is used as an information gathering source, providing video streams and I/O alarm facilities as part of the total system. Information, such as scene details in the provided camera’s stream, can be sent to monitoring centers where operators can interpret the relevance of the information. According to his or her human involvement in this case, the follow-up actions for this information for the end-user are manually invoked. In systems where no operators are available, the same camera information can be diagnosed internally; programmed and processed via smart algorithms in the camera and, as a result, IP connections are invoked to follow-up automation by other smart devices on the network.   In this article, you will find such an automation process between Bosch Cameras and Advantech Adam I/O devices. In various Verticals, this Bosch - Advantech combined solution can fully automate adequate follow-up actions for the end-user without the cost of a video management system and human intervention.   1.2 Principle and benefit of the integration In principle, a Bosch Camera embeds Intelligent Video Analytic algorithms that can be utilized internally as source for its own Alarm Task engine. This Alarm Task Engine has a dedicated Script editor (a sort of Macro editor and compiler) that allows an installer to combine internal events, I/O triggers as well as the output of IVA rules for smart follow up automation. These powerful macros are called ATSL Scripts. These installer programmed ATSL scripts are the smart engine for controlling the Advantech Adam devices and to propagate the processed camera intelligence to end-user devices as automation. The concept can be expanded as required and is not limited to a single camera, single Adam device. On the contrary, one camera as “smart detector” can control multiple I/O devices in your network.   Some examples: A camera observing an overnight storage room controls lights by controlling various I/O devices in the network. A camera IVA rule violation automatically locks doors, closes a barrier and sends an e-mail to security guards. A camera event activates contacts in AMAX control panels on a cruise ship A camera sends emergency related relay closures to multiple Adam units over various networks. A carpark camera detects loitering incidents and triggers an automatic deterrent audio message The script integration, once programmed, is autonomous and works independently.   1.3. Advantech products for this integration All latest Advantech Adam I/O D-Series units with REST-API interfacing will work. (min.Firmware Version v6.11 B20) These units are : ADAM 6050 – D   ADAM 6051 – D ADAM 6052 – D ADAM 6060 – D ADAM 6066 – D ADAM 6224 – AE ADAM 6250 – B ADAM 6256 – B ADAM 6260 – B ADAM 6266 – B   Remember only outputs are controlled via the Camera Script. Not Inputs. Please find here references to the ADAM-6000 series and the ADAM-6200 series. 1.4 Bosch products for this integration For this integration, basically all Bosch Camera types will work provided that: 1. The camera Firmware Version is min. 7.51 or newer 2. The camera supports Adam’s Basic Authentication protocol (which all Bosch cameras do) 3. The camera supports ATSL scripting (which all Bosch cameras do).   Step-by-step guide   Technical details and setup of the integration   1.Advantech ADAM I/O device preparation There is not much preparation for the ADAM units as long as the unit complies with the chapter 1.3 requirements. Best practice is to start the ADAM unit in a factory default setup and set the device IP address. You can use the Advantech AdamApax .Net Utility tool for this. This tool was also used in the test screenshots of this document to show the ADAM relay status while testing.   ADAM 6060 Relay outputs as shown in Advantech AdamApax .Net Utility: ⬇️ Please download AdamApax .Net Utility here or download directly the installer pack from here.   2. Bosch Camera device preparation To autonomously control the Adam units by the camera’s Intelligent Video Analysis (IVA) or Essential Video Analysis (EVA), the camera must be set up to detect incidents or local site events that need adequate automatic follow up i.e. line crossing, idle object, entering/leaving field, loitering etc. ⬇️ The tool to set up these functions is provided by the Bosch Configuration Manager and can be downloaded here. There are also various instruction videos published on YouTube, for example: IVA configuration IVA calibration   3. Alarm Task Script preparation The Bosch Camera Alarm Task engine is the camera’s on-board smart interface between the cameras IVA detection events as input and the resulting controlled Adam device as output. The autonomous operation of this solution is based on the smartness of the Alarm Task Script that manages the above process flow as a pre-programmed follow-up of site activities.   Example: A door will be locked for a person crossing a line allowing only traffic in the other direction. The Script can be added, edited and compiled all via the Bosch Configuration Manager tool.   By mapping IVA inputs to Adam outputs for various preprogrammed scenarios and using smart Alarm Task Script filters, timers, logical booleans combined with internal camera logical and virtual inputs, the automation can be smart, tailor-made and endless. This is what an example Alarm Task Script looks like in the Configuration Manager:   Test and see the integration at work!   1. Test Set up: The Test described below shows the basic concept of forwarding an IVA Rule trigger in the camera to an IP connected ADAM I/O device. Once you have set up the ADAM IP address and line trigger for your application in the camera (using the Configuration Manager or WebBrowser), the smart interfacing via the Alarm Task script can be programmed. In this test, we will use an IVA rule alarm (Rule 1) to control the ADAM Data output 0(=DO0) transparently. Please adapt the Adam device properties such as IP and password if needed. The Username must be “root” The script to do this automation looks like this: //VCA Profile 1 Rule 1 to Adam Relay DO0 HttpCommand dataOutput0on:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO0=1")}; HttpCommand dataOutput0off:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO0=0")}; if (VCARule(1,1)) then dataOutput0on; if (!VCARule(1,1)) then dataOutput0off;   After compiling with 0 Errors, you can check the result in the GUI in the Advantech AdamApax .Net Utility as shown below. First check if the Adam relay is idle when there is no IVA Rule Alarm (green) Then create a IVA rule Alarm (red) and check that the Relay status turns to ON.   2. Expanding IVA Rule transparency to other systems via multiple I/O Adam outputs: As indicated, the Alarm Task Scripting editor can be used to implement tailor-made IVA controlled routing to multiple Adam Outputs. This flexible routing principle makes it possible to signal IVA events generated from one location to remote locations as desired. Another advantage is that in this autonomous camera controlled system, the IVA Alarms can be interfaced to any other low or high level system.   Example: Alarm Task Script of 6 IVA Rule Alarms routed to 6 individual outputs: //VCA Profile 1 Rule 1 Adam Relay DO0 HttpCommand do0On:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO0=1")}; HttpCommand do0Off:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO0=0")}; if (VCARule(1,1)) then do0On; if (!VCARule(1,1)) then do0Off; //VCA Profile 1 Rule 2 Adam Relay DO1 HttpCommand do1On:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO1=1")}; HttpCommand do1Off:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO1=0")}; if (VCARule(1,2)) then do1On; if (!VCARule(1,2)) then do1Off; //VCA Profile 1 Rule 3 Adam Relay DO2 HttpCommand do2On:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO2=1")}; HttpCommand do2Off:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO2=0")}; if (VCARule(1,3)) then do2On; if (!VCARule(1,3)) then do2Off; //VCA Profile 1 Rule 4 Adam Relay DO3 HttpCommand do3On:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO3=1")}; HttpCommand do3Off:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)vUserName("root")Method(POST)ContentType("text/plain")Payload("DO3=0")}; if (VCARule(1,4)) then do3On; if (!VCARule(1,4)) then do3Off; //VCA Profile 1 Rule 5 Adam Relay DO4 HttpCommand do4On:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO4=1")}; HttpCommand do4Off:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO4=0")}; if (VCARule(1,5)) then do4On; if (!VCARule(1,5)) then do4Off; //VCA Profile 1 Rule 6 Adam Relay DO5 HttpCommand do5On:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO5=1")}; HttpCommand do5Off:= { Command("digitaloutput/all/value") IP("10.10.5.55")Password("00000000")SSL(false)Port(HTTP) ForceBasicAuth(true)UserName("root")Method(POST)ContentType("text/plain")Payload("DO5=0")}; if (VCARule(1,6)) then do5On; if (!VCARule(1,6)) then do5Off;   ⚠️ Disclaimer: Bosch cannot not accept any liability on implementing or using scripts mentioned in this document. Your activity in developing products that interface with Bosch products is at your own risk and responsibility regarding fitness for use, completeness, faultlessness, or any claims of third parties which may arise based on such further development.   ⚠️ ATSL Documentation ... View more

Supermicro SuperDoctor® 5 (SD5) monitors the hardware health or availability of the target node systems in data centers real-time and provide alerts to administrators. The software cand be downloaded from the link below: https://www.supermicro.com/SwDownload/SwSelect_Free.aspx?cat=SD5   System Requirements Hardware: Supermicro servers 200 MB free disk space 64 MB available RAM An Ethernet network interface card Operating Systems: Red Hat Enterprise Linux Server 5.x (64-bit), 6.x (64-bit), 7.x (64-bit) SUSE Linux Enterprise 11.x (64-bit), 12.x (64-bit) Windows Server 2008 R2 64-bit Windows Server 2012 R2 64-bit Windows Server 2016 64-bit Windows Server 2019 64-bit   Please follow the steps below and learn how you can collect the Support Data of DIP 6000 R2/ 7000 R2 with SuperDoctor 5 (SD5) software.   Step-by-step guide   1.Login to Super Doctor Start SuperDoctor from Desktop If it does not open the Login window, please click on this button and wait Login into the Webpage with (default) User ADMIN and password ADMIN Which is the SuperDoctor 5 password for Divar IP 7000 AIO? 2. Check the status of (defect) Hardware In SuperDoctor Check the Status from the Hardware you want/need to check, for example PSU and make a screenshot for Bosch Technical Support 3. Please note that the SSD Raid is NOT recognized from SuperDoctor and therefore is always faulty. For SSD check, there is the Intel Rapid Storage Tool 4. Generate the following logs from the “Report” tab: a. System Information b. Event Log ... View more

Network Docent scans and visualizes the network environment and is giving simple insight into all devices and cable connections of a network based system. This Software can help you to identify network errors and find quick solutions to fix them. You even can extract an Network snapshot which is an important log file for the Technical Support. But there are also limitation of docent for example it can only scan devices in the same sub net and it can not catch up with fast intermittent contact. If you need more information how to operate this software please have a look at Network Docent manual: https://licensing.boschsecurity.com/OMNEO/OMNEO/Docent_manual.pdf In the next view step it will be explained how to create and extract these snapshots. 1) Open or install the Network Docent Open Network Docent Install Network Docent 2) Run the Network Docent 3) Export the Network snapshot   Step-by-step guide   1) Open or install Network Docent   The DICENTIS will install this Network Docent automatically if not unselected. If you want to update an existing version you first have to uninstall the current version and reboot your PC between. With the link below you will find the current Software to perform the testing. https://licensing.boschsecurity.com/software   Open Network Docent Open the search (Windows key + S key) type Network Docent.   Multiple paths to open the program are possible. C:\Program Files\Bosch\OMNEO\Network Docent   If you want to check which version you are using click on the following. The newest version should be used to get the best test results. (It is also possible to see this shortly during the startup of the program.)   Install the Network Docent Go to this page and download the Software: https://licensing.boschsecurity.com/software   Start the program and follow the instructions.   2) Run the Network Docent   Please note you can only scan in one sub net. If you have different VLANs with multiple sub nets you can only scan within one VLAN where the Docent is placed. Also you are limited to 50 network infrastructure devices (for example switch) and another 450 end points. (max 500 devices) In the following example 4 separate scans must be done to check each branch of the DICENTIS system and they cannot displayed as whole in one. Future software improvements to solve that is in planing. Click on "Scanning Offline" and the program will scan the network. This will take some minutes depending on the size.   3) Export the Network snapshot   Click on the left upper corner to get in the menu and next on "Export file". (or you press Ctrl + E) Now select one file were you want to export the Snapshot in. Than rename the file or keep the old naming and press on "Export". You can copy it from the file and send it via mail to the technical support. ... View more

This article helps you to solve the situation where the "No Config" error message appears when you try to authenticate in Operator Client.   This error can be persistent, no matter what central server you attempt to login to and no matter what user account or credentials you are trying to use. This means that you have a corrupt cache .dat file on your system. Follow the steps below if you attempt to login into BVMS Operator Client and encounter the message: "Please enter your credentials... No config..."   Step-by-step guide   First, check on the workstation if windows firewall is enabled for the Domain profile. If so, please add the Operator Client to the exception list. This issue may be caused by a network anomaly or interruption during the Log In process: It can be easily fixed by deleting the corrupt file.   Navigate to: Computer > Windows (C:) > ProgramData -> Bosch -> VMS -> CommonOpClientSettings and delete the "proxycache.dat" file Note: It must be noted that the program folder may be a hidden folder. To see this folder: 1. Click on the Organize > Change folder and search options 2. From the "Folder Options" pop-up menu >  select the View tab > select "Show hidden files, folders, and drives" Once the corrupted file has been deleted, the "No config..." message should disappear and the Operator Client will run without issues. ... View more

   NEW! Find attached the French version of this article!   Question   What information is required for password reset of Bosch IP camera, SW and HW decoders?   Answer   If you forgot the password of your Bosch IP camera/ SW/ HW decoder and you want to reset its password, the Central Technical Support Team can help you. Before requesting a password reset, please note that you need to provide some important information to the Central Technical Support Team to get help from them.   ⚠️ The Authorization Letter is mandatory in order to proceed with the password reset. The Authorization Letter is available for download via the following article: Where to find the Authorization Letter for Password reset of Bosch Video Products and Software?   Please follow the steps below and find out how you can reset the password and what information is needed: 1. First, you need to open a web browser page and type the following: http://<IPADDRESS>/masterpwd.htm Where <IPADDRESS> is the address of your device. Example: http://192.168.1.10/masterpwd.htm 2. This will generate a password challenge code of 32 characters ⚠️ Please note that this challenge code is valid only for 1 hour!   Info: Another way to find the challenge code is by accessing the following URL:  http://<IP_address>/rcp.xml?command=0x013f&type=P_STRING&num=1&direction=READ    3. Please send the password challenge code in plain text via e-mail to the Central Support Team. 4. Additionally, you need to provide them with the following information of your device: model number MAC Address Firmware version Serial Number You can also provide them with a picture of the label of the unit. ⚠️ Be aware that in exceptional cases, you may be required to send them an invoice of your unit or other proof of ownership   Nice to know: How should the PUK code be used for password reset of Bosch IP camera, SW and HW decoders? ... View more