About VS-Support-AP

Related Products DIVAR AN 3000 DIVAR AN 5000   This article explains how to configure Monitor B output for Divar AN 3000-5000.   Step-by-step guide   The only way to change what is displayed on monitor B is via the monitor B sequence setup Select Main Menu –> Advanced –> Sequence Mon. B Everything that is selected in all of the “Split” views is what is going to be displayed. If video from only one camera is wanted, make sure all cameras/views are unchecked in all other views. Select the “Enable sequence” box Interval: This value ranges from 5 (default) to 120 seconds and is used if more than one camera/view is selected in the “Split” selection Split: Choose here which tour combination is displayed (1, 4, 8, 9 and 16 windows). If required, use the Add, Delete, Move up or Move down buttons to adjust the view settings.   ... View more

Question   What Ports need to be open for LAN and WAN Access for Divar AN 3000/5000?   Answer   To access the DIVAR AN 3000/5000 via web browsers or the mobile DIVAR Viewer App the TCP and the HTTP port shown in the DVR setup needs to be open. If both ports are not open or forwarded, logon authentication and viewing live video will fail.   The HTTP port is 80, and the TCP port is 37777, by default (configurable) The allowed port ranges are shown beside each connection type.   🛈 Port Forwarding Allows remote computers (for example, computers on the Internet) to connect to a specific computer or service within a private local-area network (LAN). In a typical residential network, nodes obtain Internet access through a DSL or cable modem connected to a router or network address translator (NAT/NAPT). Hosts on the private network are connected to an Ethernet switch or communicate via a wireless LAN. The NAT device's external interface is configured with a public IP address. The computers behind the router, on the other hand, are invisible to hosts on the Internet as they each communicate only with a private IP address. When configuring port forwarding, the network administrator sets aside one port number on the gateway for the exclusive use of communicating with a service in the private network, located on a specific host. External hosts must know this port number and the address of the gateway to communicate with the network-internal service. Often, the port numbers of well-known Internet services, such as port number 80 for web services (HTTP), are used in port forwarding, so that common Internet services may be implemented on hosts within private networks.   Portlist   Port Protocol Usage 80 TCP HTTP 3800 TCP Reserved. This is currently a private debug port used for development purposes. This port will be available in future releases 5000 TCP Reserved Used in firmware versions 1.x as private protocol port for internal communications. In firmware versions 2.x this port is configurable (default is 7892) 7892 TCP Reserved Used in firmware versions 2.x as private protocol port for internal communications 37777 TCP Private default port for remote connections; 37777 can be changed by configuration 37778 UDP Private default port for remote connections, 37778 can be changed by configuration 42323 TCP Development Monitoring 42324 TCP Development Monitoring 5050 UDP IP Search 37810 UDP IP Search 49152 TCP UPNP communication 1900 UDP UPNP Multicast 9999 UDP Reserved for factory production process 39999 UDP Reserved for factory production process 20000 - 24000 UDP RTPdata transfer; used when rtsp connections are created. Each new connection creates 2 port assignments (1 sending, 1 receiving). The HTTP port is 80, and the TCP port is 37777, by default (configurable) The allowed port ranges are shown beside each connection type. ... View more

The Divar AN 3000/5000 features the ability to ping an IP address, thus allowing the technician to verify that the workstation that is to connect to the Divar can be seen on the network. Please note that this only checks the connection from the DIVAR to the Workstation. Ping operates by sending Internet Control Message Protocol (ICMP) echo request packets to the target host and waiting for an ICMP echo reply. The program reports errors, packet loss, and a statistical summary of the results. The Internet Control Message Protocol (ICMP) is a supporting protocol in the Internet protocol suite. It is used by network devices, including routers, to send error messages and operational information indicating, for example, that a requested service is not available or that a host or router could not be reached. ICMP differs from transport protocols such as TCP and UDP in that it is not typically used to exchange data between systems, nor is it regularly employed by end-user network applications (with the exception of some diagnostic tools like ping and traceroute).   Step-by-step guide   Select Main Menu –> Setting –> Info -> Network info   Enter the IP address of the workstation into the “Destination IP” input box and select test The results of the ping and network status will be shown beside “Test result”   ... View more

 Find attached the French version of this article!   For troubleshooting of VSDK based applications (ex. BVMS, BVC) sometimes development requests VSDK logging. Typical scenarios for VSDK logs request are live view or play back issues. Related Products: BVC BVMS  Workstations Servers  Video SDK  This article explains how to collect Video SDK Logs for VSDK based applications.   Step-by-step guide 1. Enable VSDK logging 1.1 Create the directory C:\VSDK\Log. VSDK writes logs only when this directory exists In case it was already existing, there would be old logs. Delete them. 1.2 Enable specific VSDK log level. This is done by creating registry key in the registry directory VideoSDK: 1.2.1 Click Start, type regedit in the Open box, and then click OK. 1.2.2 Locate the registry directory VideoSDK5 (if it doesn’t exist, create it) - For 32 Bit system: HKEY_LOCAL_MACHINE\SOFTWARE\Bosch\VideoSDK5 - For 64 Bit system (meaning starting with BVMS 8.0): HKEY_LOCAL_MACHINE\SOFTWARE\\Bosch\VideoSDK Note: VideoSDK5 location was used for older versions that were using VSDK version 5: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bosch\VideoSDK5  Tip If you cannot find the Bosch directory at all in the Registry Editor (HKEY_LOCAL_MACHINE\SOFTWARE\Bosch), you can create it: Expand: HKEY_LOCAL_MACHINE > right click on the SOFTWARE > select New > select Key > Type in "Bosch" to name the key Repeat the steps above to create VideoSDK   Type in "VideoSDK" to name the key The registry directory is now created: HKEY_LOCAL_MACHINE\SOFTWARE\\Bosch\VideoSDK 1.2.3. If no specific instructions are provided, create: "BVIPDebug" [DWORD] /[DWORD -32 bit] in 64 bit system. The possible values are: - 0 - No changes - 1 - Debug mode - set the value to 1   1.2.3.a.  Go to the Registry Editor – Start> type Run > type regedit   1.2.3.b. Find the VideoSDK folder (please see information about the location in the beginning of this document) 1.2.3.c.  Right-click and create a new [DWORD] /[DWORD -32 bit] value.   1.2.3.d. Right on the new value created and rename it BVIPDebug.   1.2.3.e. Right-click on the file and select “Modify”.   1.2.3.f. Set the value to 1   1.2.3.g. Create the following directory - C:\VSDK\Log this is the default VSDK logging directory (it can be changed using a specific registry key) the VSDK logs will be automatically filled in this directory VSDK logging is very extensive and fills the hard drive fast. After collecting the logs, stop the BVMS application, delete the C:\VSDK\Log directory or revert the BVIPDebug value to 0, or delete BVIPDebug dword.   2. Reproduce the issue. 2.1. VSDK logs are overwritten fast, so once the issue is reproduced, close the application (BVMS, BVC, etc) 2.2. In case there is no application concerned, but the logs are written for a service (like MVS), you should stop the service in order the files to be written in the directory log and only then copy them (otherwise they will be empty). reproduce the issue stop the service (in case of MVS it is Bosch MVS BVMS Provider), otherwise you will have only empty files in the directory VSDL/logs. Once the service is stopped, the entries are filled in the log files VSDK/Log is ready to be collected   2.3. Write down short description of the issue (including IP address of the affected devices) and the timestamp of the issue.   3. Collect the logs 3.1. For BVMS always use BVMS Configuration Collector tool, it will collect also VSDK logs 3.2. For other VSDK applications copy the content of the directory C:\VSDK\Log. 3.3. For MVS always use BVMS BVMS Configuration Collector tool, it will collect also VSDK logs   4. Disable the VSDK logging. 4.1. Delete the registry key or set its value to 0 4.2. Delete the directory C:\VSDK\Log ... View more

If BVMS and VRM are installed on the same machine, it is needed to change the TCP Port of the VRM Monitor.   It can be changed by editing the "http-port" key under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BoschVideoRecordingManager\Parameters in the Windows registry.   Run regedit.exe on the VRM server Open HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Bosch Video Recording in the registry tree Change to value of the "http-port" key to the port you want the VRM Monitor to listen to ... View more