Which are the components that establish a connection between BVMS& 3rd party management system?
This article describes the different components that Bosch Video Management System offers to to establish a connection between Bosch Video Management System and a 3rd party management system.
This description helps you in writing your own commands for controlling Bosch VMS from inside your management system.
Notice! Please note, that OPC is not the preferred solution for connecting Bosch VMS to 3rd party components. BU-ESS/MKP rather recommends using our existing .NET SDKs.
List of used abbreviations: – AE: Alarms and Events – Bosch VMS: Bosch Video Management System – DA: Data Access – HTML: Hypertext Markup Language – I/O: Input/ Output – OPC: OLE for Process Control (OLE: Object Linking and Embedding) – XML: Extensible Markup Language
For details regarding Bosch VMS OPC Server, see Bosch VMS OPC Server. For details regarding Bosch VMS Proxy, see Bosch VMS Proxy. Installation section from this article describes how to install a connection between Bosch VMS and a 3rd party management system. The files needed by OPC Server and Bosch VMS Proxy, are described in Configuration files. Example for 3rd party client (HTML file), page 18 gives an example for a 3rd party application in form of an HTML file.
The following software components are used to realize a connection: – Bosch VMS OPC Server Forwards events from Bosch VMS to the 3rd party software and forwards commands from 3rd party software to Bosch VMS. It is installed but not automatically registered in Windows where Bosch VMS Management Server software is installed.
– Bosch VMS Proxy Forwards events from Bosch VMS to the 3rd party software and forwards commands from 3rd party software to Bosch VMS. It is installed on each computer where Bosch VMS Operator Client and/or Bosch VMS Management Server software is installed.
– 3rd party application As an example we provide an HTML page with code (JScript) to send commands like Show Live or Show Playback to Bosch VMS Proxy. This HTML page can be integrated in a 3rd party management system. It is installed on a computer where Bosch VMS Operator Client software is installed. You can use Softing OPC Toolbox as a 3rd party application on a Bosch VMS Operator Client computer or on a standalone computer to send commands like open/close a relays to the Bosch VMS OPC Server.
The following image shows the connection between a 3rd party application and Bosch VMS Server via OPC Server and Bosch VMS Proxy:
Figure 1.1: Connection 3rd party application – Bosch VMS Management Server
See Bosch VMS Proxy commands that you can send from an application on 3rd party side to Bosch VMS Operator Client.
The connection between a 3rd party application and Bosch VMS Operator Client does not need OPC Server.
The commands being sent by the 3rd party application can be processed by an HTML file with code. For an example for such an HTML file, see Example for 3rd party client (HTML file).
See section OPC Server events that are sent from 3rd party server to Bosch VMS OPC Server.
See section OPC Server commands that you can send from 3rd party server to Bosch VMS OPC Server.
1. Bosch VMS OPC Server
The Bosch VMS OPC Server software is used for sending state changes of the following items from Bosch VMS to a 3rd party management system like Softing OPC Toolbox.
The following items are available: – Input – Relay – Encoder – Decoder – Virtual Input – Camera
Bosch VMS OPC Server has the following features: – Notification of state changes in cameras, decoders, encoders – Start and stop recording – Control of relays and virtual inputs, status notification of I/O objects in Bosch VMS
On startup, OPC Server reads a Bosch VMS configuration file where all items like cameras, relays, inputs, decoders, encoders, virtual inputs are listed. OPC Server supports DA V.2. DA helps creating the namespace and sending commands to devices like open or close a relay.
Note: It is not supported to directly send commands to devices via DA by changing the item’s value. To send commands use the DA item CMD. Also it is not supported to query the current state of a device using DA. Use AE instead when you want to be notified about a state change of a device.
The 3rd party system DA namespace looks like this:
This picture was made with Softing OPC Toolbox.
1.1. OPC Server events
OPC server notifies state changes on the Bosch VMS side with an AE event to the 3rd party Server. OPC Server events section describes the notified values. The following table lists all error events which Bosch OPC Server can generate.
Table 2.1: Bosch VMS OPC Server Event Details
Table 2.2: Bosch VMS OPC Server / Bosch VMS Proxy Error Events
1.2. OPC Server commands
The following table lists the commands that you can send with OPC Server:
Table 2.3: List of commands (OPC Server)
This chapter describes the steps required to install the connection between a 3rd party system and Bosch VMS
2.1. Bosch VMS Server
Ensure that Bosch VMS Version 1.1.3 or higher is installed and that the Management Server is started on the Bosch VMS server computer.
1. Start Bosch VMS Configuration Client on the Management Server.
2. Create a user group with one or more users and no password (see Bosch VMS online help for details).
3. Export the configuration of Bosch VMS to BVMSConfig.xml via the menu System->Export Device Information for OPC. The export destination folder must be \Bosch\VMS\bin\.
Each time the Bosch VMS configuration is changed, repeat this step and restart BVMSOpcServer.exe. You perform this restart with restarting Softing OPC Toobox.
BVMSOpcServer.exe is automatically installed with Bosch VMS Server installation. The Server installation also automatically installs OPC Core Components 2.00 Redistributable 2.20.msi which is required for running the Bosch VMS OPC Server.
1. Create a Windows user with the name MgtS-Service with a password that complies with the password policy of the server concerned.
Note: Ensure that this password is also configured on the BIS Server.
2. For registering the OPC Server and setting appropriate DCOM settings, run: \Bosch\VMS\bin\RegisterBvmsOpcServer.exe
3. Confirm the password for the MgtS-Service user configured earlier.
4. Edit Bosch.Vms.BISProxy.dll.config for the user credentials of the administrator user (see Bosch VMS Proxy Configuration File, page 17 for details).</installation directory></installation directory>
2.2. Bosch VMS Operator Client and 3rd party client
We recommend using a dual monitor system. Configure the IE security settings:
1. On the Tools menu, click Internet Options. 2. Select the Security tab. 3. Select Trusted Sites. 4. Click Custom Level. 5. Enable the options Download unsigned ActiveX controls and Initialize and script ActiveX controls not marked as safe and click OK. 6. Click Sites: 7. Deactivate the option Require server verification (https:) for all sites in this zone and add the name of the 3rd party server computer. 8. Add your custom web page to the trusted sites.
In one particular case editing the configuration file Bosch.VMS.BISProxy.dll.config is recommended: if the client computer has multiple network adapters installed, enter the IP address of the LAN network adapter manually in the configuration file.
Enter the IP address of the client computer.
<?xml version="1.0" encoding="utf-8" ?>
Start the Operator Client of Bosch VMS, select the Bosch VMS server and log on using the same account as configured with Configuration Client.
3. Bosch VMS Proxy
Bosch VMS VMS Proxy has the following features: – Displaying a selected camera on a Bosch VMS monitor (Bosch VMS supports maximum 4 digital monitors) – Starting instant playback for a pre-configured time period – Starting and stopping Bosch VMS Operator Client from the 3rd party side
The Bosch VMS Proxy is implemented as a COM server, i.e. the delivery is a DLL which is installed and registered as part of the Bosch VMS server and client installation. The COM server implementation allows for accessing the Bosch VMS Proxy functionality from either C++/C# code but also from scripting code like JScript. Currently both ways to access the Bosch VMS Proxy functionality are used for the 3rd party system/Bosch VMS connection: access via JScript from within the 3rd party system client (browser based client using HTML with embedded JScript code) and access via C++ code from within OPC Server. Bosch VMS Proxy forwards 3rd party system-triggered commands to Bosch VMS, see Bosch VMS Proxy commands section.
3.1. Bosch VMS Proxy commands
Some commands like Show Live Image or Playback are forwarded directly to the Bosch VMS Client via Bosch VMS Proxy without OPC Server due to performance reasons. The following table lists the available commands that can be forwarded from the 3rd party client to Bosch VMS via Bosch VMS Proxy.
Table 4.4: List of commands (Bosch VMS Proxy)
Use the GUIDs from BVMSConfig.xml.
Show Live / Show playback image These commands display a camera image in the next free Image pane of Bosch VMS Operator Client or in the selected Image pane if all Image panes already display camera images.
Start/Stop Bosch VMS Operator Client Bosch VMS Operator Client is started/stopped after 3rd party system logon, via JScript. To achieve this, a Proxy method is called which starts/stops the Bosch VMS Operator Client. The method gets an XML string as parameter which describes the command. Additionally the command has another parameter containing the user name of the Bosch VMS user. Note: Do not configure a password for this user.
The command looks like this:
<nsPV:Command xmlns:nsPV=file:///S3K/Proxymanager Name=”LaunchOperatorClient”> <nsPV:Parameters> <nsPV:Parameter Name=”Login” display name=”Login” ... >[Bosch VMS user]</ nsPV:Parameter> </nsPV:Parameters> </nsPV:Command> To stop the Bosch VMS Operator Client: <nsPV:Command xmlns:nsPV=file:///S3K/Proxymanager Name=”TerminateOperatorClient” /> The user is asked to confirm exiting the application.
4. Configuration files
This section describes all configuration files that are required for the connection of the 3rd party system and Bosch VMS. To initialize the OPC Server correctly, its configuration is built during the startup of the server by reading BVMSConfig.xml. and BVMSCommand.xml. To obtain BVMSConfig.xml, you export this file from within Bosch VMS Configuration Client after each configuration change.
Note: Bosch VMS OPC Server discards state changes from unknown addresses and ignores commands on unknown addresses (filtering via GUID).
To create BVMSConfig.xml use Bosch VMS Configuration Client (see Bosch VMS Server section). This file lists all Bosch VMS devices with their name and their unique identifier. This file is used as input for the OPC server.
Structure of a configuration file:
Descriptions: – Camera: Data of a Camera item (name and identifier of the component). – Relay: Data of a Relay item (name and identifier of the component). – Input: Data of a Detector item (name and identifier of the component). – VirtualInput: Data of a Detector item (name and identifier of the component). – Decoder: Data of a Decoder item (name and identifier of the component). – Encoder: Data of an Encoder item (name and identifier of the component).
Description of the attributes: – Name: name of the component – id: unique 128 bit key of the component (identifier realized as GUID)
The Bosch VMS Proxy command file is automatically installed on the Bosch VMS server machine (for example, in \Bosch\VMS\AppData\BVMSCommand.xml).
The definition of an item’s command is stored in BVMSCommand.xml. The OPC server also reads these data on startup and depending on the item type (camera, relay, etc.) these data is stored in the properties of the CMD item. Additionally all command items have an attribute id as GUID, which identifies a relay, virtual input, or camera.
A possible structure of the file can look like this:
Descriptions: – Camera: definition of the commands for the item type Camera – VirtualInput: definition of the commands for the item type Virtual Input – Relay: definition of the commands for the item type Relay
An example for displaying a camera on a monitor can look like this: <nsPV:Commands> <nsPV:Command Name="ShowLive" OPCServerKlasse="OPCBVMSOpcServer" Anzeigename="Show Camera" Description="Display images on a monitor" ID=“id as GUID“> </nsPV:Command> </nsPV:Commands>
The OPC Server reads this file during initialization. If the file is not present, the OPC Server uses default values which are displayed in the example below.
Example of a file:
<BVMSOpcServer debg="0" disconnectionTimeout="0"/>
The file evaluates two values: debug and disconnectionTimeout.
The following values are possible for debug: 1 or 0.
If debug = 1, OPC Server logs all notifications coming from Bosch VMS in %CommonApplicationData%\Bosch\VMS\Log \BVMSOpcServer.xml
On an English Windows OS, %CommonApplicationData% usually is C:\Documents and Settings\All Users\Application Data
disconnectionTimeout specifies the number of seconds to wait for the next update of the Error item (Malfunction), when the connection to Bosch VMS gets lost.
disconnectionTimeout is only required when the connection to Bosch VMS is lost very often for a short time (< 20 s).
BVMSOpcServer_Commands.log contains commands received from BIS Server to send to the Bosch VMS Proxy.
BVMSOpcServer.log contains connect/disconnect messages and processed Bosch VMS events.
BVMSOpcServer_Events.log contains events received from Bosch VMS Proxy.
Bosch VMS Proxy Configuration File
The Bosch VMS Proxy configuration file is automatically installed when installing either a BVMS client or a BVMS server (for example, in \Bosch\VMS\AppData \Bosch.Vms.BISProxy.dll.config).
This file contains information about the Bosch VMS Proxy execution mode, an optional client host IP and the credentials to be used for logging on to the Bosch VMS SDK.</installation directory>
For server installations, the configuration file defaults are:
<add Password=" "/>
These settings cause that the Bosch VMS Proxy is started in server mode (which is a precondition for properly collaborating with OPC Server) and that SDK commands are executed using the given user credentials.
For client installations, the configuration file defaults are:
<add Password=" "/>
These settings cause that the Bosch VMS Proxy is started in client mode (which is a precondition for triggering client commands like ShowLive) and that Bosch VMS SDK commands are executed using the given user credentials.
The Host setting is optional and should only be set to the IP of the LAN network card in case of multiple network cards (e.g. a WLAN or a second LAN network card) being installed in the client system
Bosch VMS Proxy Logging Configuration File
The Bosch VMS Proxy logging configuration file is automatically installed on the Bosch VMS client machine (e.g. in \Bosch\VMS\AppData\BISProxyLogCfg.xml for English Windows). This file configures the Bosch VMS Proxy Log4Net logging settings.
Example for 3rd party client (HTML file)
A sample HTML file with JScript code used for sending commands to Bosch VMS is available in \Bosch\VMS\Samples\BVMSProxySample.htm.
For the list of commands used in this sample, see Bosch VMS Proxy commands, from above. The GUIDs are taken from an example BVMSConfig.xml.
... View more
When working with previous versions of BVMS, remote connectivity was cumbersome due to the amount of port mapping that needed to be configured. BVMS 7.5 provides a new method of remote connectivity utilizing Secure Shell (SSH) Tunnelling.
SSH Tunnelling constructs an encrypted tunnel established by an SSH protocol/socket connection. This encrypted tunnel can provide transport to both encrypted and un-encrypted traffic. The Bosch SSH implementation also utilizes Omni-Path protocol, which is a high performance low latency communications protocol developed by Intel.
The BVMS SSH service generates a private and public key when it is started for the first time. Both keys are saved in an encrypted file. When the BVMS SSH service restarts this file is detected and the private key is read.
There is little to no configuration required for this feature to function.
The SSH Service must be installed and running. If deploying a BVMS Pro system, insure the SSH Service is part of the installation process.
Recording Appliances that ship with BVMS 7.5 should have the service pre-installed. Check your “Services”.
If the service has not been installed, the install package can be run from the BVMS 7.5 downloadable install package. If working with a DIVAR IP Recording Appliance, the appliance “Installer Package” must be used.
B. Port mapping entry
The primary configuration step is to configure one (1) port forwarding for the BVMS Central Server to utilize port 5322 for both internal and external connections. This is the only port mapping entry that needs to be made for the entire system.
The image below shows a sample configuration.
A. Login with the Operator Client
After the basic configuration is done, logging in via Operator Client is very intuitive:
From the log menu, select the “Connection” drop down menu, then Select <New…>
You will be prompted to enter an IP address or DNS host name. You will also notice a cheat guide below the entry menu that will assist with address entry. Addressing must be in the following format: ssh://IP or servername:5322. In the example we used: ssh://220.127.116.11:5322.
After entering a properly formatted address, enter a valid user name and password. SSH users MUST have a password associated with their BVMS account. User accounts without a password cannot log in utilizing an SSH Connection.
After connection is established via an SSH Tunnel, all communications between the BVMS Server (192.168.1.19) and a remote client (18.104.22.168) are encrypted. Below is a Wireshark Capture taken from the BVMS Server after a connection is established.
C. Changing the SSH port
Locate the SSH service configuration file in " C:\Program Files\Bosch\BVMS\bin "
Open the configuration file and find the section below. Edit the value of the BvmsSshServicePort (the port should be unused) and restart the system.
... View more
Time is everything: meetings, public transportation, religion, transactions: the whole world is working because the concept of “time” exists. Within a security (or any other) system this is not different: recording schedules, logging, authorizations, encryption keys, timelines, all of these concepts can exist because of time.
As a result, time can either make or break a system: problems can appear only due to a time difference of a couple of seconds between two system components.
This article describes how time services can be configured in a BVMS version ≤ 10.1 environment.
For BVMS version ≥ 11.0 please refer to the following article:
Where can you configure NTP server for cameras/encoders in BVMS≥11?
Time: what is the challenge?
Each device has its own internal clock, which is based on a hardware mechanism. This mechanism acts like a watch: try to put two watches together and synchronize them on the millisecond. A security system consists out of more than two devices, it can consist of thousands of devices.
Synchronizing the time of all these devices by hand is a very time consuming task. Additionally, due to small differences in electronic components, devices can have deviations from one another.
These deviations cannot be detected by the human eye, but can result in considerable time differences when a device is running for months.
The Network Time Protocol (NTP) was created to solve these challenges. The Network Time Protocol is a network-based protocol for clock synchronization between system components. The protocol utilizes a standard IP network to communicate and can maintain a time difference (considering a local area network) of less than one millisecond between components. The Network Time Protocol is a standard protocol and documented in RFC 5905.
The operation and configuration of the Network Time Protocol are complex: a hierarchical architecture needs to be set-up including several layers of systems which are able to run the Network Time Protocol. To reduce complexity the Simple Network Time Protocol (SNTP) was created. The Simple Network Time Protocol is mainly used when less accuracy (deviations of 1-2 seconds are acceptable).
Windows Time Service
The Bosch Video Management System is running on Microsoft Windows Server operating systems. Windows includes an internal time service, which is explained on Microsoft Technet:
“The Windows Time service, also known as W32Time, synchronizes the date and time for all computers running in an AD DS domain. Time synchronization is critical for the proper operation of many Windows services and line-of-business applications. The Windows Time service uses the Network Time Protocol (NTP) to synchronize computer clocks on the network so that an accurate clock value, or time stamp, can be assigned to network validation and resource access requests. The service integrates NTP and time providers, making it a reliable and scalable time service for enterprise administrators.
The W32Time service is not a full-featured NTP solution that meets time-sensitive application needs and is not supported by Microsoft as such. For more information, see Microsoft Knowledge Base article 939322,Support boundary to configure the Windows Time service for high-accuracy environments (http://go.microsoft.com/fwlink/?LinkID=179459).”
Source: Windows Time Service Technical Reference - Microsoft Technet
The Windows Time service is based on the Simple Network Time Protocol.
The Network Time Protocol requires a very complex infrastructure, which impacts the total installation and configuration effort of the system. The Simple Network Time Protocol (also used for the Windows Time Service) reduces the complexity, but at the same time also reduces the accuracy.
For most security applications the Simple Network Time Protocol provides sufficient accuracy. Bosch recommends to use the Windows Time service, based on the Simple Network Time Protocol, as basis for time synchronization in a security network. This article provides best-practices on how to configure the Bosch Video Management System and related components in a time synchronization environment based the Windows Time service.
Alternatively, the Network Time Protocol can be used whenever it is already existing inside an infrastructure or when event accuracy with a deviation less than one second is required. Due to the complexity of the infrastructure Bosch does not make any recommendations related to the Network Time Protocol.
Management server configuration
A. Operating system configuration
This section also applies for the Video Recording Manager and Mobile Video Service when these are not running on the management server.
Microsoft has prepared a lot of documentation related to time configuration Go to the Microsoft Support: How to configure an authoritative time server in Windows Server page and scroll down to the section “Configuring the Windows Time service to use an external time source”. Click the download button under the “Here’s an easy fix” section.
Figure: Download the Microsoft Windows Time service configuration utility
The utility will configure external time servers. To select these, browse to http://pool.ntp.org and select two servers which are related to the geographical location of the system, for example “de.pool.ntp.org” and “nl.pool.ntp.org”, referring to Germany and the Netherlands. Another (local or external) (S)NTP server can also be chosen.
Start the Microsoft configuration utility and configure it as indicated and shown in the figure below.
Administrative access is required to run the utility.
Figure: Pool.ntp.org locations
Figure: Windows Time service configuration
Alternatively the configuration can be done from the command-line, using the command shown below.
net stop w32time w32tm /config /syncfromflags :manual /manualpeerlist : "nl.pool.ntp.org, de.pool.ntp.org" net start w32time
The configuration can be verified by starting the Windows Command prompt and issuing the command “w32tm /query / status”, as shown in the figure below. Notice the time source, this should point towards the configured servers.
Figure: verifying configuration
It can take up to one minute before the correct time source is displayed.
When there is a problem, the configured (S)NTP server can be tested by issuing the “w32tm /stripchart /computer:de.pool.ntp.org”, which should result in the output displayed in the figure below.
Figure: test the (S)NTP service
When an unexpected result is returned, it is recommended to check access to the specific (S)NTP server. A firewall might prevent the communication between the (S)NTP server and the management server.
B. BVMS Management Server configuration
BVMS automatically points devices to its own time-server. This can be changed by editing the BvmsCenterlServer.exe.config file, located in C:\Program Files\Bosch\VMS\bin\. Find the key "TimeServerIPAddress" and adjust the value, as shown in the example below (192.168.0.1).
<!-- Ip address of the time server for VRM/NVR encoders(defaults to the Central-Server IP if not set) . --> < add key = "TimeServerIPAddress" value = "192.168.0.1" />
C. Workstation configuration
The Bosch Video Management System Operator client runs on a Windows workstation. When the workstation and server are part of the same Microsoft Active Directory service domain, no manual time synchronization needs to be configured.
Figure: workstation configuration, "192.168.0.200" needs to be replaced by the IP address or Fully Qualified Domain Name of the management server.
When the Bosch Video Management System workstation and management Server are not joined in a domain, or into the same domain, the workstation(s) need to be manually configured to use the management server as a time server. To achieve this, the description above can be used. Instead of using the pool.ntp.org as a server, the management server is now entered.
D. Camera configuration
If a camera is connected to a BVMS system the time server will be automatically configured.
... View more
BVMS uses streamlining to reduce the amount performance that is needed by a workstation to display a high resolution video stream. Opening many high resolution cameras results in a substantial increase of CPU and/or GPU load on the Operator Client workstation. We reduce the load on the workstation by configuring the (Bosch) camera with a high resolution and low resolution stream. The stream selection depends on the size of the video and the monitor resolution. For example:
You have a camera that delivers a 1280 x 720 stream.
You are running your Operator Client with 16 image panes (4x4).
On a 21" display, one image pane has an on-screen resolution size of roughly 554 x 306 pixels.
There is no benefit of opening a 1280 x 720 stream in a 554 x 306 image pane. In this case it would be sufficient to display, for example, a 4CIF stream (704 x 480). This 4CIF stream would still provide more pixels than technically fit into the selected image pane.
Every time you open a camera or change the number of image panes the Operator Client calculates which stream it should display. The selection of the stream is based on the exact resolution of the video streams and the dots per inch (DPI) on the screen.
The frames in stream 1 are 1280 pixels wide, which results in a dpi value of 1280 pixels / 5,7" (1/4th of the 21" screen) = 224 dpi
The frames in stream 2 are 704 pixels wide, which results in a dpi value of 704 pixels / 5,7" (1/4th of the 21" screen) = 123 dpi
For a good "visual fidelity", a video should have at least 64 dpi when being viewed from a distance of 50 cm.
The "Automatic Stream Selection" feature makes sure that the video resolution never falls below these 64 dpi.
For this example, the choice is clear: displaying stream 2 is sufficient, since the 123 dpi of stream 2 are clearly above the lower limit of 64 dpi.
Suppose we maximize the image pane. A maximized image pane has a width of roughly 1146 pixels and the width of the cameo on the screen is around 11,9".
Stream 1: 1280 pixels / 11,9" = 107 dpi
Stream 2: 704 pixel / 11,9" = 59 dpi
The 59 dpi of stream 2 falls below the visual fidelity limit of 64 dpi. The Operator Client decides to use the high resolution stream instead.
These two examples show how the Operator Client dynamically switches between high resolution and low resolution streams.
🛈 Maintenance hint:
The default dpi value can be changed by editing file:
...\Program Files (x86)\Bosch\Vms\bin\OperatorClient.exe.config
The default dpi value can be found in line:
< add key = "MinDpiForAutomaticStreamSwitch" value = "64" />
To get a different automatic stream switching behavior, simply change the default value of 64 to a different value.
When increasing the dpi value, the switch to the higher resolution stream will already happen for cameos of smaller size.
When decreasing the dpi value, the switch to the higher resolution stream will happen only for very big cameos.
When setting the dpi value to a very high value, the higher resolution stream will always be active. This is equivalent to disabling the stream switching automatism.
The stream selection depends on several factors, for example, monitor resolution, monitor dpi, and image pane size. The automatic use of a lower resolution stream has a second positive effect.
Display stamping texts can be read much easier in a low resolution video stream, compared to the tiny texts of a high resolution stream.
Automatic Stream Selection:
Q1: I have maximized a cameo of an UHD camera, but I still see the low resolution stream - why?
A: For your specific setup (Operator Client layout, monitor resolution/dpi), the low resolution stream might still be still sufficient to provide good image quality. If you want to get a high resolution stream, you need to zoom in or enlarge the image pane, for example, by entering full screen mode or by moving the splitter bars of the logical tree or the alarm list. Please note that the maximize cameo operation does not mean "display the high resolution stream".
Q2: I use 4:3 cameos. When I maximize a cameo, I still see the low resolution stream - why?
A: Note that for 4:3 cameos, only the width of the video is taken into account. The "black borders" around the video are not taken into consideration during the calculation of the video stream dpi. See also answer of Q1.
... View more