Configuring a display monitor
The display monitor can display up to 24 live streams.
Creating a display monitor
Open the context menu with a right mouse click on Display Monitor and select create new object. The following window is opened:
After entering the name of the display monitor the configuration panel will be opened.
The name of the display monitor must be specified according to the config entry "MyControllerName" in the AccVimaccDisplay<id>.conf file (see also Configuration of the display server).
E.g.: MyControllerName=MD15GZBC_Display_00055
In this case you must use "Display_00055" for the display monitor name.
Configuration of a display monitor
Host
All created hosts can be selected in this selection list.
Active
Activates/deactivates the display monitor.
Default live stream
Defines which stream of a camera is displayed by default.
Default Playback stream
Defines which stream of a camera is used as default for playbacks.
If you don't change the settings of a new created display monitor, stream 1 is used as default for live streams and playback streams.
Use streaming proxy
If enabled, streams are requested via the streaming proxy.
List of streaming proxies
Defines the streaming proxy which shall retrieve the video streams.
Type of transmission for video streams to this Display Monitor
- UDP Unicast from Interface
- The display monitor requests the stream via UDP unicast communication from the interface. In addition, transport=0 is written to ".object.device.definition" of the respective data point.
- UDP Multicast from Interface
- The display monitor requests the stream via UDP multicast communication from the interface. In addition, transport=1 is written to ".object.device.definition" of the respective data point.
- TCP Unicast from Interface
- The display monitor requests the stream via TCP unicast communication from the interface. In addition, transport=2 is written to ".object.device.definition" of the respective data point.
- Multicast from device
- The display monitor requests the stream via multicast from the image source. In addition, transport=5 is written to ".object.device.definition" of the respective data point.