Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    3 weeks ago
    ⚠️   WARNING:   Do not upgrade the camera firmware directly to 7.10. If you do this,  “error 13: device check failed”  message will be displayed, and the firmware will not be upgraded successfully.
    View full article
    100% helpful (1/1)
    ‎04-23-2021 08:46 PM
    Related Products MIC IP starlight 7000i (MIC-7502-Z30x), MIC IP fusion 9000i (MIC-9502-Z30xxx) MIC IP starlight 7100i (MIC-7522-Z30xx), MIC IP Ultra 7100i (MIC-7504-Z12xx) AUTODOME IP starlight 7000i (NDP-7512-Z30xx) Symptoms Complaints received about video performance in terms of sharpness, focus, and color. AUTODOME IP starlight 7000i, MIC IP starlight 7100i. Complaints received about focus failure, MIC IP starlight 7000i, MIC IP fusion 9000i . Complaints received about NTCIP control of Autofocus, Autoiris, and MIC wiper. All Models. Diagnosis Video Performance MIC IP 7000i, MIC-9000i: Focus failures caused by an unexpected range of tolerances in a small percentage of lenses. AUTODOME IP starlight 7000i: Incorrect default settings, camera block performance, and compatibility issue between the optical characteristics of the bubble and the camera block. MIC IP starlight 7100i : Sharpness and color performance were not aligned with the previous model. NTCIP Controls Autofocus and Autoiris functions were released in 2007, but the NTCIP standard was changed in 2014. These functions were not used in the ITS market until recently. NTCIP Wiper Operation This operation was never implemented and no complaints were received until June, 2020. Solution FW release 7.72.0008 Contained camera block FW for video improvements for the MIC IP starlight 7100i and the AUTODOME IP starlight 7000i . Contained the NTCIP Autofocus, Autoiris, and MIC wiper control implementation for all of the models. FW release 7.80.0128. Contains new camera block FW with additional video improvements for the AUTODOME IP starlight 7000i and still contains the camera block FW for the MIC IP starlight 7100i. Contains new camera block FW with focus improvements for the MIC IP starlight 7000i and MIC IP fusion 9000i. NOTES: All of camera block FW updates require an additional step for the FW upgrade process, which is described in the documents attached. The MIC IP starlight 7000i and MIC IP fusion 9000i focus improvements are only applicable to a specific S/N range, so there is a separate FW upgrade for these models.
    View full article
    100% helpful (1/1)
    ‎04-12-2021 12:43 PM
    ?   Hint: A) If you would like to search for the   BVMS version   that can be used according to the   firmware version of your DSA E2800, please check the following link: TB-VS: Plan for a new Firmware for NetApp E2800 iSCSI storage (dual controller) systems B) The Serial Number (SN) of your DSA E2800 is displayed under   Support   >   Support Center   in the upper right corner.
    View full article
    ‎03-24-2021 10:22 PM
    Related Products AUTODOME 7000 HD, MIC 7000i, and MIC 9000i Question  Why is the minimum FW version 6.52.0003 for these models? Answer In November 2018 an internal hardware (HW) change was made to these models that requires this new minimum FW version. The new HW version isn't backwards compatible with older FW versions. Question If the unit has been upgraded to a higher version, how do I get the 6.52.0003 FW? Answer This FW version was only released for these three models, so it isn't available on the Bosch Download Store. At this time, please contact Technical Support to obtain this FW. It will be available on the individual Product catalog pages by March 11, 2019 (or sooner).
    View full article
    100% helpful (1/1)
    ‎03-02-2020 02:58 PM
    Hardware change in FLEXIDOME IP 4000i 5000i causes update in minimum FW version 7.60
    View full article
    100% helpful (4/4)
    ‎09-06-2019 03:06 PM
    Introduced Firmware signature and firmware file encryption to protect IP cameras
    View full article
    ‎07-30-2019 08:54 PM
    Problem: Configuration Manager does not display all camera configuration menus for cameras with fimware v7.10+     Resolution: Upgrade Configuration Manager to v6.20 or higher.  It is available on the  Download Store        
    View full article
    ‎04-04-2019 09:19 AM
    Symptoms transparant data transmission at a Encoder VideoJet Multi 4000 or VIP-X16-XF-E stops / does not work any longer in case of a power outage and restart of the device. Diagnosis when e.g. controlling a Bosch Autodome 7000 and PTZ via Transparent Data not working after reboot of the encoder, this is caused by an issue in the released firmware. It doesn't matter if it is Firmware 6.30.0047 or 6.30.0059. As a power outage should happen not too often the solution below is offered to fix this. Solution The solution is via a workaround using an ATSL script in the encoder to re-set the COM port baud-rate upon a reboot/restart of the encoder (which should in normal practice not happen to often). Please add th following scritp to the Alarm Task Editor tab either via CM or Web interface. //The 1st line set the board rate, 2nd line sets the port type RS232 = 1 or RS485/422 = 2 RcpCommand setCOMBaudrate := { Command( "rcp.xml?command=0x027e&type=T_DWORD&direction=WRITE&protocol=TCP&payload=9600&num=1" ) }; RcpCommand setCOMMode := {Command("rcp.xml?command=0x0208&type=T_OCTET&direction=WRITE&protocol=TCP&num=1&payload=2")}; if (true) then setCOMBaudrate, setCOMMode; If the device has a password set then 2 additional perimeters need to be added UserName() and Password(""). RcpCommand <name of RCP command> := { Command( "Bla Bal Bla" ) UserName(Service) Password( "enter the service level password here" ) }; There will be no furhter release or fix provided by BOSCH status of 2019-03-19 as the ATSL script resolves this.
    View full article
    100% helpful (2/2)
    ‎11-07-2018 08:31 PM
    MTU and MSS     MTU stands for "Maximum Transmission Unit." MTU is a networking term that defines the largest packet size that can be sent over a network connection. The MTU is typically limited by the type of connection, but may sometimes be adjusted IT network settings. The typical value of the Network MTU is 1514 Byte. If a system sends packets over an Ethernet network that are larger than this size, the data will be fragmented into smaller packets. When referring to Ethernet MTU this includes 4 Byte checksum. The  1514 Byte is the interface MTU without the Ethernet Checksum. In cae there are limitations by the type of connection, the packets will then need to be reassembled on the receiving side (e.g. Bosch video management software or Bosch hardware decoder). However, it can be beneficial to optimize the packet size on the sender side (e.g. IP camera) to the exisitng network infrastructure. As MTU maximum packet size is layer 1 related, the IP MTU that you can be adjusted at the BOSCH device configuration (Configuration Webpages or with the help fo BOSCH configuraiton software like "Configuraiton Manager"). The BOSCH GUI refers to this as “Network MTU”. BOSCH products can manage fragmented data. MSS stands for "Maximum Segment Size" The MSS value is calculated from the MTU. MSS = MTU – (layer 3 TCP header [20 Byte] + Layer 2 IP header [20 Byte]+ Layer Ethernet 1 [6+6+2 = 14 Byte]) For example looking at CPP 6 Platform – like FLEXIDOME IP panoramic 7000 MP in Firmware version 6.50.0128 you can adjust and find the following values: Network MSS (in Byte) - default value = 1460 iSCSI MSS (in Byte) – default = 1460 Network MTU (in Byte) – default = 1514   MTU and MSS can be adjusted at all released firmware versions 4.x and later. CPP-ENC CPP3 CPP4 CPP5 CPP6 CPP7 CPP7.3 yes x x x x x x x No               Here some screenshots as example based on Firmware 06.50.0128  
    View full article
    ‎10-29-2018 09:18 AM
    The attached file explains how BVMS can be configured to connect to an LDAP (or Microsoft Active Directory) and use it as a base for user authentication.
    View full article
    100% helpful (2/2)
    ‎06-07-2018 06:30 PM
    The table below lists the firmware versions which are used in the BVMS 7.5 system test.
    View full article
    ‎05-21-2018 08:30 PM
    Related Products DVR 700 series BVIP device   Question Why does Divar 700 change the settings of 2nd stream, even though only 1st stream is configured in the DVR?   Answer Divar 700 uses the concept where it assumes to be the (master) device to have control over the cameras and their streams. Stream 1 is always set to profile 1 Stream 2 is always set to profile 2 Only one command is sent from DVR to set both stream 1&2 So please configure profile 2 in the wanted way to be used with stream 2.
    View full article
    ‎05-21-2018 08:30 PM
    Related Products VIPXD (Audio Version)   Question Why there is NO sound from a loudspeaker connected to a VIPXD SPK port?   Answer The RTC_AUDIO_LOUDSPEAKER_ON_OFF flag is not activated. This flag can be set manually by using this CGI command: http://160.10.x.x/rcp.xml?command=0x09be&type=F_FLAG&payload=1&direction=WRITE&num=1 Replace 160.10.x.x by your VIPXD IP address.
    View full article
    100% helpful (1/1)
    ‎05-18-2018 02:03 PM
    Related Products All Bosch encoders running firmware 4.0 and above Question How can I set, clear and check virtual alarms via CGI? Answer  You can use virtual alarms within encoders as a trigger to have other events take place. This is an example on how to integrate 3rd party devices/software to trigger an event to take place on the encoder.  This event could be used to change any variable via ATSL (Alarm Task Script Language) - example below Virtual Alarms via CGI Set Virtual Alarm: http://160.10.92.40/rcp.xml?command=0x0a8b&type=F_FLAG&direction=WRITE&payload=01&num=1 Clear virtual Alarm: http://160.10.92.40/rcp.xml?command=0x0a8b&type=F_FLAG&direction=WRITE&payload=00&num=1 Check virtual Alarm: http://160.10.92.40/rcp.xml?command=0x0a8b&type=F_FLAG&direction=READ&num=1 Virtual Alarms in ATSL if (VirtualAlarm(1)) then Relay(1) := true; if (!VirtualAlarm(1)) then Relay(1) := false;
    View full article
    100% helpful (1/1)
    ‎05-18-2018 01:49 PM
    Related Products All IP encoders Answer Copy/Paste the selection below to your alarm task editor and save. This script will make your encoder trip relay 1 only when IVA rule #1 alarm is active. // Set TempState to monostable mode, 5 seconds OperationMode monostable := { High(50) }; TempState(1) := monostable; if (VCARule(1,1)) then TempState(1) :=true; if (TempState(1)) then Relay(1) :=true else Relay(1) :=false;
    View full article
    Top Contributors
    Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist