Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    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 (3/3)
    ‎03-29-2021 09:40 AM
    Which Bosch encoders and decoders are compatible with BVMS? Up until some years ago, new released cameras, encoders, domes and decoders that are introduced into market after a BVMS release could not be connected to an existing BVMS version because these cameras where not known to the BVMS. In the BVMS 4.5.1, a new concept was introduced. This concept treats Bosch video encoders and decoders as generic devices, and automatically recognizes specific device functionality (for example the number of streams, relays and inputs). Based on this information the, at that time, unknown device is added to the system and can be used by the operator. The attached document provides a detailed description of this functionality.
    View full article
    100% helpful (3/3)
    ‎03-25-2021 07:30 AM
    CPP: Combined firmware package – applicable to all platforms The Release Letter for CPP 7.72.1118 provides information about the dependencies between firmware versions for a better understanding of the upgrade process of devices with older firmware. To find a combined firmware file in the downloadstore you can use the following URL syntax: https://downloadstore.boschsecurity.com/index.php?type=fw&filter=CPP CCP4 and CPP6 devices: Due to an internal file system being introduced to CPP4 and CPP6 since firmware 6.10 and architectural changes thereof, a direct upgrade from firmware below version 6.10 to latest firmware is only possible via intermediate firmware 6.1x. CPP4 cameras upgrade from FW < 6.10 to intermediate FW 6.11 upgrade from FW < 6.50 to intermediate FW 6.50 upgrade EXTEGRA from FW 6.10 or newer to latest FW 6.32 upgrade from FW 6.50 (<6.51) to latest FW 7.10   CPP6 cameras  upgrade from FW < 6.50 to intermediate FW 6.50 upgrade from FW 6.50 (<6.51) to latest FW 7.70  CPP5 devices: This combined firmware cannot be applied to CPP5 products with firmware version older than 5.91. It is required to upgrade to intermediate firmware 5.91 first This means that intermediate firmware version 5.91 for CPP5 needs to be requested from your technical support. Only after receiving and uploading firmware 5.91, you can upload the latest version CPP5 specific firmware  available on the Download Store (currently 6.31.0010). To find a combined firmware file in the downloadstore you can use the following URL syntax: https://downloadstore.boschsecurity.com/index.php?type=fw&filter=CPP if needed for some reason, the older CPP 6.50 combined file is available here: https://downloadstore.boschsecurity.com/FILES/KnowledgeBase/CPP_FW_6.50.0620.fw and Releaseletter of that combined firmware package: https://downloadstore.boschsecurity.com/FILES/KnowledgeBase/Bosch_Releaseletter_CPP_FW_6.50.0620.pdf Note: Upgrading from versions lower than 5.5x To upgrade to a newer firmware version using this combined firmware package, firmware versions before 5.5x require an intermediate update cycle using the respective platform firmware version mentioned above. Restrictions: This firmware and its included platform firmware builds are not applicable to MPEG-4 products. The final firmware version for VIP-X1600-XFM4 modules is FW 5.53. No newer firmware will be provided for these modules. Configuration Manager cannot upload this Combined Firmware file to VIP-X1600-XFM4 modules. Use the module’s web page instead for uploading; or use the separate firmware file. The final firmware version for CPP3 devices is FW 5.75. No newer firmware will be provided for these products. The Combined Firmware file does not load onto VG4 AUTODOME or AUTODOME Easy II via the browser when running a firmware version before 5.52.0017. The specific platform file should be used instead. (Note: In case any link might not work to the current DownloadStore, see attached a copy PDF of the Release Letter.) How to get and request a BOSCH Legacy Firmware: The procedure to request and get an legacy firmware that is no longer online in the web is as follows: Customers are kindly requested to reach out to the local BOSCH Support (Central Solutions and Support Group teams). Bosch Support Group will ask for the exact BOSCH Commercial Type Number (CTN). The local BOSCH team can check the Global End of service date. The project background (How many of these devices/cameras) need to be collected.  The relevant BOSCH Technical Support can explain and check if there is the chance to update the project and included management software in order to be able to use the latest BOSCH device firmware as the goal is to have a non-vulnerable product in productive environments. In case there is no newer firmware available (hardware was discontinued), a commercial hardware upsell can be recommended. In general all firmware that is not available on the product catalog, and for all firmware files that are ranked to have vulnerabilities, this need to be documented in a Technical Support case. In case legacy firmware is anyhow needed and requested by our customers, the Bosch Technical support will start an approval flow. The BOSCH Level 3 Technical Support will provide a form/document that must be signed by the installer/customer. See an example PDF (empty) "Example_Aged_Software_Release_form.pdf" attached to this article. Such a form will be prepared by the BOSCH Level 3 Technical support team and provided to our customer/installer in order to confirm that legacy firmware is then used on the risk of the installer and customer (See text and legal note in the PDF). In the future BOSCH plan to introduce and setup a self-service portal for all customers to simplify this process. ___________________________________________________________________________ The above mentioned combined firmware 6.50 supports: CPP7.3 HD and UHD cameras update from FW 6.40 or newer to latest FW 6.50 CPP7 UHD cameras update from FW 6.30 or newer to latest FW 6.50 CPP6 UHD cameras update from FW 6.10 or newer to latest FW 6.50 CPP5 encoders update from FW 5.91 or newer to latest FW 6.30 CPP4 HD cameras update from FW < 6.10 to intermediate FW 6.11 update from FW 6.10 or newer to latest FW 6.50 CPP3 cameras and encoders update from FW 4.54.0026 or newer to latest FW 5.74 CPP-ENC VIP-X1600-XFM4 encoders: update from FW 4.2x or newer to latest FW 5.53 VJT XF and VJD-3000 update to latest FW 5.97 The combined firmware package includes the following build versions: CPP7.3 FW 6.50.0128 CPP7 H.264 6.50.0128 CPP6 H.264 6.50.0128 CPP5 H.264 6.30.0059 CPP4 H.264 6.50.0128 CPP4 H.264 6.11.0021 CPP3 H.264 5.74.0010 CPP-ENC H.264 5.97.0005 for VJT XF family, VJD-3000 and VJC-7000 CPP-ENC H.264 5.53.0004 for VIP X1600 XFM4 For detailed description please refer to the separate release letters. Customers can upload such combined firmware packages by using multi-select in the Configuration tool "BOSCH Configuration Manager" (currently available in version 06.01.0157 at the BOSCH DownloadStore or Product catalog > Video Software > Video Management Systems > Configuration Manager) When using the multi-select option in Configuration Manager, please make sure this combined firmware package for all platforms can be uploaded to all the devices selected and there are no additional requirements or intermediate steps needed for any of the devices in question. This article has status of 24th of March 2021 and changes in this procedure might be introduced. When changes are done, then this article will be updated. Therefore check this article from time to time.
    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
    ‎02-01-2021 09:01 PM
    Symptoms In rare cases userc might have seen random reboots of the NetApp E2800 contorllers in a simplex controller E2800 iSCSI storage syste   (updated: According BOSCH Product Managemetn and alignment with NetApp Simplex controller systems E2800  can be operated on NetApp Firmware 11.50.2 Updates will be published till 8th of February 2021 dual controller E2800 iSCSI storage systems usng below mentioned older  NetApp Firmware versions   Diagnosis This article is valid for Dualcontroller NetApp E2800 systems. Only for those useres recognizing such a E2800 iSCSI dual controller sysstem show an unplanned reboot, can consult the NetApp Major Event Log (MEL). Customers reported this to BOSCH using a NetApp  dual controller firmware 11.40, dual controller firmware11.50.2 dual controller firmware11.50.R2.  We request customers facing a reboot / unexpected iSCSI connection reset to get in contact with BOSCH Technical Support. For Dual Controller systems a new version is approved and offered by BOSCH. Simplex / Singel Controller systems E2800 can be and should be used with Frimware 11.50.2  which can and must be requested via BOSCH Technical support. See also the BOSCH product catalogue for latest information status update  2021-02-01: https://resources-boschsecurity-cdn.azureedge.net/public/documents/DSA_E2800_Release_Note_enUS_79775057035.pdf   These data are currently updated and therefore this KB-article will be enhanced and updated between  2021-01-10 and 2021-02-08.    Solution A basic step when dealing with technical questions for NetApp E2800 iSCSI storage systems is, to register the system with Serial No. by using the following registration form: https://resources-boschsecurity-cdn.azureedge.net/public/documents/Registration_DIP_600_Special_enUS_9007222920871435.docx  NetApp and BOSCH want to inform, that we expect  a new SANtricity firmware, provided by NetApp, which will contains a fix for the controller random reboot issue which were reported back to Bosch by some customers. The firmware version /  SANtricitiy firmware for E2800 iSCSI models  is delayed and planned for May 2020. As this NetApp SANtricity firmware is desigend by NetApp for BOSCH use cases with 24/7 video recording + replay and even worst case situations during a running reconstruct, this Firmware is not yet available via NetApp NOW. NetApp agreed with BOSCH to cover all improvements and fixes in a global and public release around June/July 2020. BOSCH will inform here in this article about the comming release when available.
    View full article
    100% helpful (2/2)
    ‎04-09-2020 09:22 PM
    What are the best practices for surge and lightning suppression?
    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
    ‎09-19-2019 08:32 AM
    The attached document aims to provide concerned parties, such as customers, users, operators or consultants, with an overview of data privacy and protection related features of BVMS Person Identification. Moreover, this document describes how data, as processed during the Person Identification steps, can be classified. Finally, this document lists technical measures for data protection in the context of BVMS Person Identification.
    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
    100% helpful (1/1)
    ‎08-26-2019 01:03 PM
    Question How can I combine a ISS SecureOS Auto system (providing ANPR functionality) with a BVMS system? Answer The attached document describes the steps how to configure BVMS and the ISS SecureOS Auto system for achieving watchlist ANPR alarms and recorded ANPR detections into the BVMS logbook.  
    View full article
    ‎08-02-2019 03:47 PM
    Question Does BVMS meet the requirements specified in IEC62676-1? Answer The attached document describes how a BVMS system meets the requirements specified by IEC62676-1.
    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
    ‎08-27-2018 12:05 PM
    RTSP and multicast streaming
    View full article
    100% helpful (2/2)
    ‎07-13-2018 10:55 AM
    Collection of FAQs for the Video IT Products DIP 6000 & 7000, DSA E2700 & E2800, HP Workstations and HPE Servers
    View full article
    ‎06-18-2018 09:56 AM
     This article describes how to collect log files and configuration of IP cameras, encoders and decoders. 
    View full article
    ‎05-16-2018 09:31 AM
    Product Security Advisory: Meltdown and Spectre vulnerability in Common Product Platforms (CPP)
    View full article
    ‎05-16-2018 09:30 AM
    Absolute Positioning protocol document for Bosch IP moving cameras
    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