About Central_Support

Question   If you have CPP4 cameras with 6.11 firmware (FW) version and you need to upgrade them to the latest version, normally you have to upgrade to an intermediate firmware version first. But where you can find this firmware ?   Answer   You need to use the CPP file (global file not encrypted) and update the camera as many time as possible to go up to 6.50 (where the FW are encrypted). The CPP file contains all the intermediate FW needed to update an old FW. CPP file → E.g.: CPP4 HD cameras o upgrade from FW < 6.10 to intermediate FW 6.11 o upgrade from FW < 6.50 to intermediate FW 6.50 o upgrade from FW 6.50 (<6.51) to latest FW 7.10 Or you can switch to the CPPS global file and update until the 7.10 version for CPP4. CPPS file → E.g.: CPP4 HD and MP cameras o upgrade from FW 6.51 or newer to latest FW 7.10   These files can be found here, on the Download Area.   More information about firmware release and provisioning status can be found here. Also, find out from here: what is a CPP and where you can find it for your Bosch IP camera? ... View more

Question   Are you looking for the MIC IP fusion 9000i Wiper/Washer RCP command syntax to incorporate it in the third party software?   Answer   Use the following command which triggers the camera to wipe five times then stop: http://<IP_address>/rcp.xml?command=0x09A5&type=P_OCTET&direction=WRITE&num=1&payload=0x80000201B080070168 Replace<IP_address> with the IP address of the camera. For example: http://192.168.1.15/rcp.xml?command=0x09A5&type=P_OCTET&direction=WRITE&num=1&payload=0x80000201B080070168   Washer (MIC should have a washer kit):  http://<IP_Address>/rcp.xml?command=0x09A5&type=P_OCTET&direction=WRITE&num=1&payload=0x80000201B080070169 ⚠️ The "predefined position" for the wash/wipe function is preset 62. The installer must define preset 62 (preferably where the washer nozzle is located and can direct washer fluid towards the camera window) before using the wiper/washer function. "Status 14" code OSD → Washer operation was attempted without washer pre-position being stored. → Configure the washer pre-position. If necessary, refer to the subchapter “Using the Wiper/Washer (Bosch AUX/Pre-position Commands)” in the User Manual for details on configuring washer functions.   AUX commands: Please note that the camera usually does this through auxiliaries commands: AUX 105 and 104. With the help of AUX commands you can enter pre-programmed keyboard control commands. These commands are composed of a command number plus the appropriate function key. A valid combination either issues a command to the device or displays an on-screen menu.   Below is the AUX command for the Wiper/Washer using Bosch Protocol   To activate the washer/wiper function, press ON-105-ENTER and confirm this sequence: 1.The wiper moves to a predefined position. 2.The washer turns on for five seconds. Simultaneously, the wiper turns on and wipes five times. 3.The washer turns off. The wiper turns off. 4.The camera returns to its previous PTZ position (and to inactive mode if applicable) Other AUX commands:   Good to know: Below you can find more extra examples of various RCP commands for MIC IP fusion 9000i : Visible Light ON http://<ip>/rcp.xml?command=0x09A5&type=P_OCTET&direction=WRITE&num=1&payload=0x8500040415030001 Visible Light OFF http://<ip>/rcp.xml?command=0x09A5&type=P_OCTET&direction=WRITE&num=1&payload=0x8500040415030000 IR ON http://<ip>/rcp.xml?command=0x09A5&type=P_OCTET&direction=WRITE&num=1&payload=0x8500040410030001 IR OFF http://<ip>/rcp.xml?command=0x09A5&type=P_OCTET&direction=WRITE&num=1&payload=0x8500040410030000  How to activate the wiper and the white lights of MIC IP starlight 7000 HD in BVMS? ... View more

Question   Did you try to upgrade the firmware of your camera and the message below was displayed? Find out from this article what might be the cause that could lead to this message being displayed: “error 18: wrong or no signature”   Answer   Maybe you have tried to upgrade the camera with the wrong firmware (FW) or the upgrade was not done properly. You have downloaded the firmware package from an unknown site, other than the official Bosch website and the file could have been corrupted. Depending on the firmware you have on your camera, the firmware upgrade must be done according to the release letter of the firmware you want to update.   Example: If you have a DINION IP starlight 7000 HD (CPP7) camera with the firmware 7.10 and you want to upgrade to the  FW version (7.70), this package must be used. According to the release letter of the Firmware 7.70, this supports CPP7 HD cameras and the upgrade must be done as the following: upgrade from FW < 6.50 to intermediate FW 6.50 upgrade from FW 6.50 (<6.51) to FW 7.70   ⚠️ To upgrade to a newer firmware version using this combined firmware package, products may require to have this firmware file uploaded multiple times until the intended firmware version is installed.   Note: Please note that the combined firmware package is applicable to H.264 and H.265 products based on one of the following platforms: CPP7.3 HD and UHD cameras o upgrade from FW < 6.50 to intermediate FW 6.50 o upgrade from FW 6.50 (<6.51) to FW 7.70 CPP7 HD cameras o upgrade from FW < 6.50 to intermediate FW 6.50 o upgrade from FW 6.50 (<6.51) to FW 7.70 CPP6 UHD cameras o upgrade from FW < 6.50 to intermediate FW 6.50 o upgrade from FW 6.50 (<6.51) to FW 7.70 CPP5 encoders o upgrade from FW 5.91 or newer to latest FW 6.31 CPP4 HD cameras o upgrade from FW < 6.10 to intermediate FW 6.11 o upgrade from FW < 6.50 to intermediate FW 6.50 o upgrade EXTEGRA from FW 6.10 or newer to FW 6.32 o upgrade from FW 6.50 (<6.51) to FW 7.10 CPP3 cameras and encoders o upgrade from FW 4.54.0026 or newer to FW 5.75 CPP-ENC encoders and decoders o VIP-X1600-XFM4 encoders: upgrade from FW 4.2x or newer to FW 5.54 o VJT XF, VJD-3000 and VJC-7000 upgrade to FW 5.97   The combined firmware file is not applicable to devices running firmware higher than FW 6.50 due to the two-factor authenticated release signature. Release letter version 7.70.0817: https://downloadstore.boschsecurity.com/FILES/Bosch_Releaseletter_CPP_FW_7.70.0817.pdf ✔️ Note: Please always check the latest available CPP and CPPS on downloadstore.boschsecurity.com ... View more

Question   Let’s suppose that you have one setup which consists in an Adam 6060 I/O module, BVMS and a DINION IP thermal 8000 camera. Can the state of an ADAM relay module be changed when the IVA from the camera generates an alarm?   Answer   If you have the ADAM relay module attached to the system, you can use it to enable sirens and spotlights for example, only if conditions that are set up in an IVA-task are met. Therefore, please make sure first that you enabled the IVA on the camera, and you have created specific tasks for it. Then, in BVMS (Bosch Video Management System), create first an event, then an alarm and you can configure from there what happens on that alarm. This is explained in the BVMS Configuration manual. Also, you can consult how to setup IVA on our YouTube channel.   Afterwards, you can trigger a relay from BVMS via SDK scriptlet. To achieve this, open the script area in the Configuration Client (Tools-Command Script Editor menu) You can use the script below, but you need to do some adjustments in the Script, as the name of the relay used, how long the relay to be active etc.   Scriptlet: Open and close a relay This scriptlet opens and closes a specific relay. This scriptlet is meant to be used in a server script.   [Scriptlet("system generated script ID")] public void OpenAndCloseRelays() { //line #1: Relay r = Api.RelayManager.GetRelayByName("Relay 1"); //line #2: Api.RelayManager.Open(r); //line #3: System.Threading.Thread.Sleep(1000); //line #4: Api.RelayManager.Close(r); }   Comments (line-wise): 1: Get the relay as specified in Bosch VMS (by name) 2: Open the relay 3: Wait for 1000 ms = 1 second 4: Close the relay   You can refer to this document where there is a step-by-step procedure with configuring relay contacts from an ADAM6050 to activate when there is an IVA alarm condition within BVMS from an associated camera. ... View more

 Find attached the French version of this article!   Intelligent Platform Management Interface (IPMI) is a security guard for your server. Some primary functions of IPMI are to monitor hardware status (including temperatures, power consumption, voltage, etc.), log server data, and allow access to the server even when an operating system is not installed or is malfunctioning. IPMI gives you the ability to manage servers in remote physical locations regardless of the installed operating system. This procedure is applicable for DIVAR IP 6000/7000 (R2 & AIO).   Follow the steps below and find out how you can remotely view and collect the system's event log through IPMI..   First, please make sure that a LAN cable is connected to the IPMI port on the back of the DIP: Note: IPMI port is set by default to obtain automatically the IP address. Therefore, a DHCP server is needed. If there is no option to have physically a router with DHCP server on it, then please refer to the following article and find out how to assign IP address to a DIVAR IP 7000/ 6000 through haneWIN DHCP server software. Step-by-step guide   The IPMIView software can be downloaded from here: https://www.supermicro.com/SwDownload/SwSelect_Free.aspx?cat=IPMI To be able to download IPMIView, you will be asked to either login with your account in case you have one or to continue as guest and fill in your details (work e-mail, name and company).   1. Install the software and open it by selecting “Run as administrator” 2. Discover IPMI Device IPMI View software offers a feature that will detect all devices or systems currently connected to the network. Click the ‘File’ button and select ’Discover IPMI Device’ You may specify a Network IP address range and network Mask, then click Detect or Start to search for any IPMI devices or systems that are connected to the IPMI tool connections.   3. Select the IP address of the device for which you want to collect logs and click "Start" and "Save" The selected IP will be found in IPMI Domain section 4. Once you are connected to the remote server via IPMI Console Redirection, the following IPMI Login screen will be displayed: Enter the username & password and click Login. Default credentials: Username: ADMIN Password: ADMIN ❗ Notice: Units that have been produced after 2020: access to the IPMI are no longer made with ADMIN / ADMIN credentials. The user remains ADMIN, but the password is unique for each unit. The password can be found on the label on the back of the unit. Applicable for: - any unit that has IPMI and was produced after 2020 - any motherboard replaced in any system, even older, if the new component was produced after 2020 You have 2 options to collect the Event Log: via web browser or directly from IPMIView tool:   A) IPMIView Tool:   1.Select Event Log tab > choose the Event Type you want to collect (Health event/ Maintenance) and click the “Get SEL Records” button 2. Once the events are displayed, you can export them in one .txt file by clicking the Save button Note: Current SEL Device Timestamp: This item displays the timestamp of the current device.To learn about the rules, click the information icon  B) WEB browser: If you would like to sort the system’s events log, you can choose a category from the drop-down list in the WEB view. The event log you can choose may be as follows: All events System Management Software Events BIOS Generated Events Sensor Specific Events 1. Open the web browser and type the IP address of the unit found through IPMI   2. Enter the username & password and click Login. ⚠️ You need to have Java installed in your system to launch the console. So, be sure that you have the latest version of JAVA.   3. Go to 'Server Health' tab > Select 'Event Log' 4. Once the events are displayed, you can copy them into a .txt file and send it to the Central Support Team if they have requested you the logs.   Good to know:   Also, in IPMI you can check the Power Source if SuperDoctor is not working and other information such as Sensor Recordings, Power Consumption. You can find this information by clicking the 'Server Health' tab:   Power Source: Sensor Readings: Power consumption:     Tip If you were asked by Technical support to provide them with the Post Snooping code, please follow the steps below: right click on the IP address from the IPMI DOMAIN →  then, you will connect to the webpage of the IPMI tool   Go to Miscellaneous tab → The Post Snooping code will be displayed ... View more