Important Cookie Information

This website uses absolutely necessary cookies. If you consent to the use of convenience cookies, please click “Yes, I agree.” By clicking on “Privacy Settings.” you can change this setting at any time and withdraw your given consent. Icon down see more You can find detailled information in our Privacy Policy Icon forward-right
Icon up see less

Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    ‎05-16-2018 09:24 PM
    Related Products Bosch Recording Station Video Jet X Series BRS   Question Is it possible to control an AutoDome connected to VideoJet X Series via Bilinx?   Answer In BRS 8.8.1 Bilinx over Encoder only works for devices connected via VSDKPluginModule. Current supported devices are VIP-X1600-XFM4B and VIP-X1XF. VideoJet X series are connected per default via VCSModule, which does not support Bilinx communication. To be able to control Bilinx devices on VideoJet X series please configure the following work around: 1. In BRS Configuration > IP Cameras and encoders > Scan network (VideoJetX is found) and add VideoJetX device to BRS 2. Click VideoJetX and click Edit 3. In tab General settings select Device Type BVIP H.264 4. In tab Dome settings mark Activate and select Connection Bilinx/IP Dome Now the AutoDome can be controlled via Bilinx. Note: Due to performance reasons do not change the encoder stream from MPEG-4 SH++ to H.264 streaming! Only change the device type in BRS.
    View full article
    ‎07-22-2019 01:46 PM
    This article shows how to configure Input Alarm and later search for them in the Event search using Web Interface. There are only 3 different search parameters for Event type search, which are "All", "Motion" and "Alarm". Once can search for any alarms during the set time period and channel and in this way indirectly to filter for Input Alarm (if only Input Alarm triggers Recording for a particular channel). It is not possible to directly narrow the search for particular Alarm type (ex. Input alarm). 1.Configure the Input Alarm. Go to: Settings - Alarm - Input Alarm. Click Enable and Chose the respective Input (from 1 to 16), then click Record Channel and Save.  Note: The other Settings like Buzzer, Display Mon. A can also be configured but is not a must for performing Even Search. Schedule the recording. Settings - Schedule: Chose the days of the week, the time and enable "Alarm" Set the recoding stream. Settings - Storage - Recording: Chose the stream to be recorded. 2. Event Search - Chose the respective Camera (that recorded on Alarm Input) and search for "Alarm"
    View full article
    ‎07-10-2019 11:51 AM
    When using Configuration Manager, each device has a status icon. The method below shows you how to generate an updated certificate for Bosch IP Camera's and VRM Servers Here we are talking about Certificates, the Icon is colored Yellow with an exclamation mark. Using the mouse over Tooltip, the device is saying exactly what is wrong with the certificate connection. VRM on a DIVAR IP 5000: IP Camera: Right click on the device to Show Certificates, if you wish to view them. We can see that there are multiple things wrong. The Cert is not Trusted Inconsistent Date Cert Name mismatch. First is inconsistent date: All IP devices and PC’s must be synchronized on Date time page (group General)   Second is invalid certificate First quick look on certificate requirement level, navigate to Preferences -> Configuration Manager -> Access -> Security:   The certificate must just be valid - self signed certificate matching host name/IP address will be sufficient. We need to generate a new certificate on Certificate page. Clicking "Generate certificate" button: should open a certificate creation dialog - most important options are matching common name and matching validity time.   After the certificate is created correct usage must be set as shown below:   IP Camera Certificate   To apply changes VRM must be restarted. If certificate requirement is higher,  then a validatable chain of certification must be used (This would be setup by a System Integrator or IT Administrator): Trusted - the signing entity CA (e.g. VeriSign) must be trusted on target PC Issued by this CA - There is a  Micro CA setup on this PC.
    View full article
    ‎05-21-2018 08:33 PM
    Connections and programming for VIP X1XF and VG5 600 Dome.
    View full article
    ‎05-21-2018 08:40 PM
    This will let you call up cameras on an Allegiant monitor output across the network to a remote site.
    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
    ‎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
    ‎05-01-2019 08:50 PM
    Keeping an eye on system messages and to collect logging data at a central site just got a whole lot easier:  Syslog feature is implemented in all IP BOSCH Products for many years. Since latest firmware versions a GUI on the WEB-page of the IP cameras was added. The BOSCH IP cameras as network devices can continuously send system messages via Syslog. This funciton must be activated and configured before as a devinded Syslog IP as destination for those messages must be activated and network administrators need to monitor those data. There are many different monitoring tool on the market. Configuration and technical analysis functions of those are in responsibility of those software vendors. Known tools are PRTG NETWORK MONITOR from PAESSLER Kiwi Syslog Server EventLog Analyzer from ManageEngine and many more. Especially for incidents that happen unpredictable and do not necessarily trigger an alert message can be analyzed with syslog even throughout reboots of equipment (switch reboot / IP camer reboot etc.) as the syslog reconnects to the destination server. As well in cases were many system items are involved this can be very helpful (several switches / many IP cameras involved). By using the BOSCH Configuration Manager or Bosch Configuration Client software can help to quickly setup the syslog function for many cameras in just a few mouseclicks. In current firmware generation 6.xx for BOSCH IP video products a enhanced user webpage to configure loggings that are also sent out via syslog  Event Logging Software Sealing Debug Logging  In case this syslog function need to be was introduced and added. At the Configuration webpages those extra logging can be collected and downloaded. With Syslog logging data can be sent to a syslog server.     
    View full article
    100% helpful (1/1)
    a week ago
    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 (1/1)
    ‎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
    100% helpful (2/2)
    ‎05-17-2019 04:46 PM
    Combined firmware package 6.60 – applicable to all platforms The Release Letter of the combined firmware package for all platforms 6.60.1321 provides information about the dependencies between firmware versions for a better understanding of the upgrade process of devices with older firmware. 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 with firmware versions below 6.10 need to upload this package twice. For example, when having firmware 5.92 on a CPP4 device, you need to load the CPP all common firmware file two times: >  First time this is loaded the device will be updated to the 6.11.0021 which is part of the common file. >  Second time you load the common firmware file, the update to 06.50.0128 will be performed. CPP6 cameras with firmware versions below 6.10 need to upload the separate firmware version 6.1x first to receive the latest firmware version. This means that intermediate firmware version 6.1x for CPP6 needs to be requested from your technical support. A support ticket to Level 3 team at MKP PRM group via the support ticket system is needed. In case we see a high demand for that a new combined firmware file might be created by PRM. Only after receiving and uploading firmware 6.1x, you can upload combined firmware package for all platforms 6.50.0620 or CPP6 specific firmware  6.50.0128.  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 combined firmware package for all platforms e.g. 6.50.0620 or CPP5 specific firmware  6.30.0059. To find a combined firmware file in the downloadstore you can use the folowing URL syntax: https://downloadstore.boschsecurity.com/index.php?type=fw&filter=CPP or you use the CPP 6.50 combined file 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.74. 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 (L1 and L2 team). Bosch Level 2 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 (e.g. Level 2) 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/endcustomer. 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 31st of October 2018 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
    100% helpful (4/4)
    ‎09-06-2019 03:06 PM
    Introduced Firmware signature and firmware file encryption to protect IP cameras
    View full article
    ‎05-18-2018 01:23 PM
    How many streams can use the BP+ profile?
    View full article
    ‎05-18-2018 01:39 PM
    Related Products Bosch encoders Answer Place this in the alarm task editor and save it.  Please read the comments for more details.  They are noted below by //. //Define weekly timer from Monday to Sunday from 7am to 9pm Timer weekly := {TimeBegin(07:00) TimeEnd(21:00) DayBegin(Mo) DayEnd(Su) }; //define what is to be recorded Recording recording:= { Camera(All) }; // Define Operation Mode to periodic, 1 sec low 30 min high OperationMode periodic := { Low(10) High(18000) }; TempState(1):=periodic; //define recording timer OperationMode monostable := {High(50)}; TempState(2):=monostable; //Turn on recording timer if (IsActivated(weekly)) then TempState(1) := true; if (TempState(1)) then TempState(2) := true; if (TempState(2)) then recording else Stop(recording);
    View full article
    ‎05-18-2018 01:41 PM
    Related Products All IP encoders   Answer Copy/Paste this example into the alarm task editor and save.  See comments below for more details, annotated by //. // Settings for JPEG posting JpegPosting PicPosting := { IP( "put ftp FQDN servername or IP here" ) Login( "anonymous" ) Password( "anonymous" ) Format( Large ) FileName( "Snap" ) Suffix( Date ) Camera( All ) }; // Define Operation Mode to periodic, 15min low and 0.1 second high OperationMode periodic := { Low(18000) High(1) }; //define logic TempState(1):=periodic; if(true) then TempState(1); if (TempState(1)) then PicPosting;
    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