About Central_Support

IPMI allows you to remotely monitor and manage certain aspects of the DIVAR IP all-in-one 7000 2U (gen 3), such as power status, temperature, fan speed, and other hardware-related information. This can be particularly useful in data center environments where remote management of servers and other devices is essential. Please note that the IPMI works on DIVAR IP all-in-one 7000 2U (gen 3) as designed.   Step-by-step guide 1. Prerequisites: set BIOS primary adapter to Auto instead of iGFX  you require a monitor connected (monitor must be connected to DVI) Disable windows lock screen and set "shutdown monitor to never"   2. Limitations: On the IPMI screen, the POST/ Boot sequence is shown until KIOSK mode pops up on the main Monitor, then the IPMI screen goes black. to get image on the IPMI screen, you need to login into Windows with BVRAdmin After login, Windows will "generate" a secondary screen for the IPMI which is an extended screen (you can’t change the setting to duplicate) Mouse control is basically inexistent, you need to drag/ drop any program to the secondary screen when you are in front of the main screen (you need to work from the DIVAR) You can’t open anything from the IPMI screen, you are basically clicking on the main screen which you can’t see, the mouse will not migrate to the IPMI screen. for Example, drag & drop the Super Doctor to the IPMI screen, and you can then basically migrate with Alt+Tab using the Virtual keyboard. if a screen timeout is set and the DIP goes in Kiosk Mode, IPMI screen will go black and a new logon to windows is required Power control works (restart/power on/shutdown)  Note To see the second monitor you can use iKVM viewer (in the IPMI)    Nice to know: How to remotely view and collect the DIVAR IP 6000 or 7000 (R2&AIO) system's event log through IPMI? ... View more

Question   Is it possible to configure a 2 X 3 layout for VIDEOJET decoder 8000 (layout of 2 images on the first row and 3 other images in the second row)?   Answer   It is not possible to have a custom layout, such as 2 X 3. Supported layouts depend on physical characteristics of monitor and on the set aspect ratio. For example, for a monitor with optimal resolution 1920x1080 the following layouts are supported. Other resolutions may have different values. Any resolutions are supported:    Nice to know: How can you change the Decoder Layout with BVMS SDK script? ... View more

Question   In the controller history, you can see entry as detailed below, showing Detector -On- 14 , what does this indicate?   Answer   This entry indicates that during alarm verification, manual alarm was activated on the controller. ... View more

Efficient way to update the panel firmware in an AVENAR panel 4.x network via SD card, thus keeping downtime of the panels to a minimum. The following steps describe an efficient way to update the panel firmware in an AVENAR panel 4.x network via SD card, thus keeping downtime of the panels to a minimum. To further reduce downtime, it is recommended to network the panel nodes via ETH. Step-by-step guide   In the example below we will update four nodes from firmware 3.2.2 to firmware 4.0.2, one of which is redundant (1.1). It is irrelevant which panel node you start with. Note: A firmware update might require an update of the OPC server if the panel network is connected to a BMS.   Let’s get started. 1. Copy the 4.0.2 AVENAR panel firmware (*.swu) to one or several SD cards (FAT32)   2. Starting with node 1.1, insert the SD card into the redundant panel’s memory card slot. 3. Power down the main node via its power switch. 4. As soon as the redundant node reboots, place your finger immediately on the screen and wait until the boot menu appears   5. Select “Load new firmware from memory card”   6. The panel screen will display the progress. Once the screen displays “Please touch screen to exit!” eject the SD card. Follow the instructions and touch screen to continue.   7. Back in the boot menu select “Toggle firmware & restart panel”   8. The redundant node will reboot, running on firmware 4.0.2 with default configuration. 9. Now insert the SD card into the main panel nodes memory card slot. 10. Power up the main panel node and immediately place your finger on the screen. Wait until the boot menu appears and select “Load new firmware from memory card”.   11. The panel screen will display the progress. Once the screen displays “Please touch screen to exit!” eject the SD card. Follow the instructions and touch screen to continue.   12. Back in the boot menu select “Exit menu & start panel”   13. The main panel node will reboot running on its current 3.2.2 firmware and corresponding configuration. The panel is fully operable communicating with all neighboring panel nodes. 14. After all faults have been reset, the panel will display the fault message “SW incompatible ...” as the redundant panel node is running on 4.0.2. 15. For the single panels and keypad (1.2, 1.3 and 1.4) power down the node and repeat steps 9 – 13. - Expected downtime for panels with redundancy, approx. 10 minutes. - Expected downtime for single panels and keypad, approx. 5 minutes. 16. When finished all panel nodes will be fully operable running on firmware 3.2.2. 17. Now to switch the panel firmware to 4.0.2 and upgrade the configuration to 4.0 18. Via RPS connect to all panels with the current 3.2 configuration. In our example RPS is connected to panel node 1.1. All nodes must display a yellow or green flag confirming connectivity! 19. Before you right-click on each individual node and “switch firmware”, ensure that your sequence does not isolate a node. Otherwise you need to go to that isolated node locally to switch the firmware. Send the “switch firmware” command to the panel you are physically connected to last. In this example the firmware is switched first on node 1.3 and last on node 1.1     20. After the “switch firmware” command has been sent to each panel the panels will reboot, running on firmware 4.0.2 and default configuration. 21. Upgrade the 3.2 configuration to 4.0.   22. Afterwards open the 4.0 configuration and connect to all panels via RPS ensuring that all nodes must display a yellow or green flag confirming connectivity! 23. With “Configuration Overview” load the 4.0 configuration into all panels of the panel network. 24. After the panels reboot, reset all (network-related) faults. The panel network will be fully operational. Expected downtime for panels depends on the number of nodes and configuration size. As a reference, the downtime for a panel network with 20 nodes (4 of which redundant) is approx. 20 minutes. Note: - Panels with redundancy will temporarily display “configuration mismatch …” until the main node has synced its configuration with the redundant node. - All user passwords will be set to default and must be re-entered. ... View more

Goal: Detecting a paper jam on the paper shredder with the Camera Trainer Solution: Bosch IP camera with Camera Trainer, e.g. NDE-8513-RX (FLEXIDOME IP starlight 8000i)              Note All configuration screen shots reflect Configuration Manager version <7.71 and FW <9.x. Everything higher, the UI has changed and is completely different.    − A clearly recognizable symbol is applied to the shredder chute, which stands out well from the background and the material being transported. − The marking should not be in the main material stream, otherwise there is the possibility of false alarms due to permanent coverage. Better in the side area, where material flow or standstill only occurs when there is a traffic jam. − The marking is taught into the camera trainer in order to permanently detect it statically, in the example below an X marking. − If this can no longer be detected by the camera for the defined period of time, the alarm is triggered via the occupancy count. In the example below, if the X marking cannot be detected again for more than 5 seconds.     Step-by-step guide   Camera settings   Calibration   No height information so that the camera does not generate an artificial horizon and runs purely in 2D.   VCA basic setting     CameraTrainer   Train the Camera Trainer detector to distinguish between object to detect.   Create task 1/3:   Create task 2/3:   Create task 3/3:   Outcome   Short term cover   If the occupancy is “0” for less than 5 seconds, no alarm is generated:     Alarm case   If the occupancy is “0” for more than 5 seconds, an alarm is generated:   Video Example Counter   Concept example video alarm on missing object: ... View more