Bosch Building Technologies

    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    100% helpful (3/3)
    ‎06-24-2021 04:11 PM
    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 (4/4)
    ‎09-06-2019 03:06 PM
    Introduced Firmware signature and firmware file encryption to protect IP cameras
    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
    ‎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
    ‎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-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
    ‎05-21-2018 08:33 PM
    Connections and programming for VIP X1XF and VG5 600 Dome.
    View full article
    100% helpful (1/1)
    ‎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
    ‎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:23 PM
    How many streams can use the BP+ profile?
    View full article
    ‎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
    Top Contributors