System parameterization and parameter documentation

System parameterization and parameter

documentation

Contents
System parameterization and parameter documentation 1
Contents...................................................................................................................................... 1
Settings....................................................................................................................................... 1
Workspace .................................................................................................................................. 2
Project......................................................................................................................................... 3
Workspace ................................................................................................................... 4
Projects ........................................................................................................................ 4
Projectmanager ............................................................................................................ 4
Save project and reload................................................................................................ 5
Configuration .............................................................................................................................. 6
Standard Configuration ................................................................................................ 6
Project Configuration.................................................................................................... 7
Remote Transport........................................................................................................................ 9
Field of Usage............................................................................................................... 9
Course of actions.......................................................................................................... 9
Monitor administration.............................................................................................................. 12
Functionality............................................................................................................... 12
Configuration ............................................................................................................. 13
Projecting advice........................................................................................................ 15

Settings
After starting the control system the Editor for the creation of the project data is started and the current project is loaded.
The name of the project is displayed in the title bar.

VipWin Users Manual 3-1

System parameterization and parameter documentation

The menu line offers the pulldown menu items:

• File Function calls and auxiliary functions which relate to the currently
active project which is to be processed;
- workspace, project,
- configuration,
- set up printer, printing,
- export, import variable,
- termination.
• Edit Undo
• Pictures - Templates
- New picture
Open picture
- Selection of last pictures edited
• Tools - Recipe Group Manager
- Time control, Script management,
- Allocations, Functions management,
- Reaction matrices,
- Report module (optional)
• Options - Start runtime
- Display/suppress toolbar
- Display/suppress status line
- Display/suppress layout table
- Display/suppress color table
- Display/suppress symbol table

• Window empty
• Help - Information about
- Help

Workspace
All data which are defined and stored for a project are a component of the internal database of the control system.
Within a workspace several projects can be created and managed. The managing of several projects in one workspace
recommends itself if the same plant parameters are present (pictures etc.) and copying of the data makes the configuration
significantly easier or if several projects in one plant are connected via a network. Several projects can be processed at the
same time.
Alternatively, another workspace can be generated in another directory for the projects' recordings.
Example:
• \CLIENT1\PROJECT (one or more projects in the database)
• \CLIENT2\PROJECT (one or more projects in the database)

3-2 VipWin Users Manual

 System parameterization and parameter documentation

The structure of the database is defined by four database files (DBD). They are the basis for the completely new creation of
a project database. An additional database file in MS-ACCESS format (MDB) exists for the Recipegroup Manager.
Attention: No preconfigured data are present!

Click on "Open workspace".

The operation is shown in the status line at the bottom of the screen. After selection the file selection window is opened.

The desired customer workspace (e.g. "C:\PROJECT\workspace1.wsp6”) is selected and confirmed with the "OK" button. All
projects contained in the opened workspace are then displayed in the Projectmanager.

Project
Once the workspace is open, one or more projects can be edited or selected in the Project manager. An existing project can
be inserted into the current workspace.

VipWin Users Manual 3-3

System parameterization and parameter documentation

Workspace

If a new project or a new workspace is to be created, a dialog mask appears after selection of the menu item
"Workspace/project new..".

Projects

After a name and a path for a new workspace is entered it will be created.

After entering a project name and path you can choose whether the new project should be inserted into the current
workspace or a new workspace for this project should be created.
In addition to “Blank project” you also can select “Global project”. This means a project that is not connected to a process.
The objects of a global project (templates, alarm groups, etc.) are available to all projects of the workspace.

Projectmanager
Selection of an existing project is done by selecting the project in the Projectmanager by clicking on it with the left mouse
button. The right mouse button opens the following context menu.

The following commands are available

• Runtime
- Create changed creates changed Runtime files for the active project
- Create all Save current changes in the project (selected files)
- Import Files that can be edited in the Runtime are read back to the Editor
path
– Standard recipes

3-4 VipWin Users Manual

 System parameterization and parameter documentation

– Recipes of the Recipegroup Manager

– User administration
– Schedules and profiles
• Project as start project Defines the selected project as the startproject for the Runtime (only
visible, if the selected project is NOT the Runtime startproject at the
moment)
• Start Runtime Runtime is started with the project defined as start project
• Project active set active project for the toolbars of the Editor and the cross reference
list
All other projects, not marked as "Keep project in memory", are
deactivated
• Keep project in memory the project stays in the memory, even if another project is activated
• Project
- Rename… Rename selected project
- Save as… saves the project under a new name in a new directory
- Properties ... opens the properties window with the project properties
- Remove from workspace removes the project from the current workspace, but does not delete
it physically
- Delete deletes the project physically
Create backup... creates a backup of the project
Load backup... loads a saved project to the current workspace
• Project administration… opens the project configuration
• Alarm administration… opens the alarm configuration
• CEL administration… opens the CEL configuration
• Monitor administration… opens the screen configuration
• Project Remote Transport Update runtime files on other computers
- Establish connection Initiate remote connection
- Transport changed Runtime files Transport changed runtime files to target station
- Transport all Runtime files Transport all runtime files to target station
- Read back all Runtime files All Runtime files are read back to th Editor files
- Project as start project Set start project for target station
- Start Runtime Start Runtime on target station
- Stop Runtime Stop Runtime on target station
- Reload project Execute function “Reload” on target station
- Request Runtime error files Get error file from target station
- Restart OS Restart operating system on target station
- Get system status Get system status of target station
- Remote password change the password for the remote access to the project computer is
changed
• Help Opens online-help
Every project can be protected by a password (chapter "Password administration") i.e. on opening the project the password
defined in the projected is requested. If the entry is correct the project is opened.

Save project and reload

The project backup creates a ZIP file with the saved project. This backup then can be restored to the same or another
computer.
This is the only way to copy a project from one computer to another.

Create backup
The following dialogbox is opened, when a project backup is to be saved:

• Package File Name of the ZIP file for the project backup
• Description Free textstring as comment
• Multiple disk spanning No spanning: One large ZIP file is created

VipWin Users Manual 3-5

System parameterization and parameter documentation

1,44 MB spanning: Several 1,44 MB size ZIP files for copying to a

floppy disk are created

ATTENTION: As the service zenDbSrv.exe only runs with local rights and not with the rights of the logged in user, a backup
to a network drive is not possible!

Load backup
The following dialogbox is opened, when a project backup is to be restored:

• Filename Name of the ZIP file to restore the project from

Configuration
The configuration is split into two parts:
• Standard Configuration System control
Serial number
Standard...
• Project Configuration Project
Alarms administration
Chronologic event list
Screen
Password
Project Backup
Project Rename
Project Save as...

Standard Configuration
System control
With the help of the system control, the system configuration of various hardware and software options can be set.
This application module is a component of Microsoft Windows. Therefore the symbols corresponding to the Windows
version installed at the time appear here. Precise description of the many possibilities for system configuration can be found
in the "Windows user manual" . The system parameters can also be selected directly from the Windows system
environment.
Serial Number
The current serial number and the activation key (from the ZENON6.INI file) can be read out by selecting the menu item
”File\Standard Configuration\Serial number”.
Standard
By selecting the "File\Configuration\Standard" menu item, non-project-related settings are possible for the following
characteristics:
• Printer selection Global printer settings for all database projects
• Directories Definitions for projects being newly created

Printer selection
Printers can be assigned for the following functions:
• for online Alarm- or Cel-list Online alarm report list or chronologic event list
(global setting under ”Configuration/Project”, format via the files
ALARM.FRM or BTB.FRM).
• for offline Alarm- or Cel-list Offline alarm report list or chronologic event list
(global setting under ”Configuration/Project”, format via the files
ALARM_G.FRM or BTB_G.FRM)
• for reports and values for output for protocols from the Report Generator and for HD values
• for hardcopies Printer for screen hardcopies
• for lists Output of closed logs and texts from list windows
By pressing the "Select printer" button, selection can be made from the printers defined and installed in the Windows
system.

3-6 VipWin Users Manual

 System parameterization and parameter documentation

If a printer is assigned for the corresponding output then the printer setup can be altered by pressing the button "...".
If you need different settings for one printer, you can load the same printer serveral times with different settings.
For different printer interfaces the same printers can be used with different parameters.

Directories
Pressing the "Paths" button defines the project paths for projects which are to be newly created in the database.

• Graphic Graphic files

• Export Exported archives, chronologic event lists, alarm lists
• Alloc. Only for campatibility reasons to older versions
• Backup Only for campatibility reasons to older versions
• Exp. Archives Directory for archive backup
• Online help Only for campatibility reasons to older versions

Project Configuration
After creating a new project, the project parameters are defined in the menu item "Project administration" in the
contextmenu of the project. Belonging to this, for example, are the paths for the project-related files, the default colour for
character and background, and the printer configuration.

VipWin Users Manual 3-7

System parameterization and parameter documentation

Possible options are:

• Project administration Settings for the project
• Alarm administration Settings for the alarm management
(See chapter "Alarming")
• CEL adminsitration Settings for the operating log
(See chapter"chronologic event list")
• Monitor administration Settings for virtual and physical monitors
(Also see tutorial "Monitor Administration")
The configuring of the alarms administration and the chronologic event list are explained in the corresponding sections.

Project info

The following information on the project can be defined:

• Author Author of the project
• Manager Manager of the project
• Company Company for the project
• Comment Free comment for the project
Directories

The following paths can be set:

• Graphic *.DXF, *.WMF, *.BMP, *.JPG
• Export *.DBF, *.TXT
exported files
• Alloc. only for compatibility reasons with older versions
• Backup only for compatibility reasons with older versions
• Exp. Archives *.ARV
• Online help only for compatibility reasons with older versions
RT changeable data
There are different data, that can be changed in the Editor as well as in the Runtime. If all Runtime files are created resp.
transported, the files meanwhile changed in the Runtime would be overwritten. In order to avoid unwanted overwriting the
files, that should not be created resp. transported, can be selected here in the section "Do not generate and transfer".
Data changed in the Runtime can be read back. In this case the corresponding Editor data are overwritten. In order to avoid
unwanted overwriting the files, that should not be read beack, can be selected here in the section "Do not decompile".

The following file types can be selected:

• Recipe group Manager Recipe groups and recipes of the Recipegroup Manager
• Standard recipes Standard recipes

3-8 VipWin Users Manual

 System parameterization and parameter documentation

• Passwords User administration for the password system

• PFS Changes in the time models and schedules of the PFS
• Message-Control Recipient database of the Message Control

Remote Transport

Field of Usage
The Remote Transport is used to transport Runtime files to a target system. Reason: Projects are created in the Editor. The
projects created in the Editor have to be translated, so that the Runtime can understand them. This happens, when the
Runtime is started from within the Editor, resp. when "Create Runtime files" is executed.
If the Runtime and the Editor are on the same PC, the Runtime files now are directly available to the Runtime. If the Runtime
is not on the same PC, there are two possibilities:
The according directory with the Runtime files is connected as a network drive or
The Runtime files are copied to the target system.
The second possibility can be done with the Windows Explorer or easier and more systemantic with the Remote Transport of
the control system. The Remote Transport makes sure, that always all necessary files are transported to the target system.
Also any other files can be transported with the Remote Transport.
Additional to that pure copy function the Remote Transport offers other functionalities:
Incremental copy The Editor automatically knows, which files of the target system are different to the
local ones, and only copies the changed and not all files. This leads to enormous
time savings with large projects.
Setting the start project With the Remote Transport the start project on the remote station can be set.
Starting and stopping the The remote station can in a certain way be remotely maintained.
Runtime
Transfer the system status The current status of the remote PC (operating system, control system version,
existing drives, etc.) can be found out.
PC reboot A remote PC can be rebooted.
Read error files Error files can be read from the remote Runtime.
Copy back project data An entire project can be copied back from the remote system.

Course of actions
General
The Remote Transport consists of two parts: A sender (=Editor) and a receiver (=transport service). Sender and receiver
have to be of the same version, so that the Remote Transport works correctly. If this is not the case, an error message is
displayed in the Output Window on establishing the connection.
Remote version: 6.01.0....... Compatibility: 'NOT GUARANTEED'
Configuration
The destination settings for transporting files are in the Editor in the context menu of the project under "Project
administration… - Remote transport".

TCP/IP
In the Remote Transport configuration the name of the target system is defined under "Configuration parameters":
HOST=target system;
Attention! Do not forget the ; (semi-colon) at the end.

VipWin Users Manual 3-9

System parameterization and parameter documentation

HINT: Automatic setting in server projects:

If the project to be transported is a server project, the name of the remote PC may not be entered in the
Remote Transport configuration under "Configuration parameters". The standard setting HOST=; can be
kept. In this case the Remote Transport always uses the PC entered in the network configuration as "Server".
So it is guaranteed, that the changes are always transported to the server, which then automatically
transports them to all clients!

As a default the Remote Transport is defined so, that it works with TCP/IP without any problems. If there is no entry under
[SYS_REMOTE] in the zenOn6.ini, the standard settings are active.
The TIMEOUT, within which a connection problem is noticed, can be changed. This can be necessary with very slow or
overloaded networks.
To do this the following entry in the zenOn6.ini of the remote system has to be changed or created:
[SYS_REMOTE]
CONFIG=DEVICE=TCP/IP;TIMEOUT=xx;
Where xx is the number of seconds.
The entry under "Configuration parameters" in the Remote Transport configuration in the local Editor has to be in the
following way:
HOST=target system;TIMEOUT=xx;
Attention! The entries in the Editor have to correspond with those on the remote system!
Also the TCP/IP port, via which the transport service communicates with the Editor, can be changed. As a default the Remote
Transport always uses the TCP port 1101. In certain cases this port can already be occupied by other programs (especially in
Novell networks). These changes have to be made by the user.
In the zenOn6.ini on the remote system for the transport service:
[SYS_REMOTE]
CONFIG=DEVICE=TCP/IP;PORT=xxxx
xxxx stands for any free TCP port number (e.g.: 5000)
The entry under "Configuration parameters" in the Remote Transport configuration in the local Editor has to be in the
following way:
HOST=target system;PORT=xxxx;
Attention! The entries in the Editor have to correspond with those on the remote system!

Serial
As a default the transport service is always defined for TCP/IP communication. Exception: Under Windows CE the transport
service can be configured in the user interface.
If the communication type of the transport service should be changed, the zenOn6.ini on the remote device has to be edited.
The Editor can be set comfortabely in the Remote Transport configutation.
Attention! If the zenOn6.ini is edited, the changes become effective after a restart of the transport service.
If the transport service should be used for serial transport, the following entries have to be made in the zenOn6.ini on the
target system by hand: (Under Windows CE these entries are automatically generated in the zenOn6.ini with the help of the
user interface of the transport service.)
[SYS_REMOTE]
; SysService attached to the COM interface:
CONFIG=DEVICE=COM;PORT=COM2;

With this setting the Remote Transport works with the baudrate 115200 bits/second. As a default the Editor is also set to
this baudrate.
In the Editor "Serial" has to be selected as "Transport device" and the according COM port of the source PC has to be
entered under "Configuration parameters".
Attention! Do not forget the ; (semi-colon) at the end.
If the baudrate should be changed, the alternative baudrate has to be set in the Editor as well as in the transport service:
In the zenOn6.ini on the remote system for the transport service:
[SYS_REMOTE]
; SysService attached to the COM interface with changed baudrate:
CONFIG=DEVICE=COM;PORT=COM2; BAUDRATE=57600;
Under "Configuration parameters" in the Editor the COM interface and the baudrate have to be entered, e.g.:
PORT=COM1;BAUDRATE=57600;

Attention!

3-10 VipWin Users Manual

 System parameterization and parameter documentation

The baudrate on the target system and on the development station have to be the same! The COM interfaces however can
be different, e.g.: COM1 on the development station and COM2 on the target system.

Define files
In the column "active" of the Remote Transport configuration all fields that should be transported are marked with a
doubleclick. Line 2 with the project basis path cannot be deactivated. The project files always are transported.
The source paths should always be defined as relative to the project basis path.

Attention! All settings defined here also have an influence, if the project is used in a network! Everything which is to be
transported here, will be transported to the clients during runtime resp. will not be transported.
Example: Transporting graphics is deactivated, because the graphics are on the server already. Then a client is started. The
client finds out, that the graphics should not be transported and thus does not transport them to itself. So no graphics will
be displayed on the client. Of course it also can be the other way round, so that files are transported to the client, that
should not be transported.
As a default the project basis path, the graphics path, the list path, the video path and the report path can always be
transported. From the project basis path the project.ini, the project.vba, the monitor.mon files and the directory "project"
are transported as a default.
All files in these directories will be transported.
Special case global project: If there is a global project in the workspace, it will automatically be listed for the transport in
line 1. No additional settings have to be entered. Always all files necessary for the global project will be transported.
If additional files should be transported, these files can be copied to one of the standard paths or be entered additionally.
A click on the field "Source" with the right mouse button opens a context menu, where "File selection" or "Directory
selection" can be chosen. Now single files or entire directories can be selected for the transport.
Then the column "active" of that line has to be activated, and now any files stated here will be transported with the project.

HINT: relative paths/files:

Here again alternative files can be entered reelative to the project basis path. This has the advantage, that
independent of the target system the right directory structure always is retained.
Example: Under source you enter \default.iso by hand. The Remote Transport now automatically knows,
that the file is in the project basis path. The same procedure is possible for directories.

Usually only the target path of the project basis path has to be defined. The according path available on the target system
has to be entered under "Destination". "Destination" also may stay empty. The the files are transported in the same
directory structure as defined under "Source".

VipWin Users Manual 3-11

System parameterization and parameter documentation

HINT: relative paths/files:

If the source files are defined relatively, nothing has to be entered under "Destination". (Only the destination of the project
basis path). All other files then are automatically transported relative to this directory!
Example: If the file "default.iso" should be transported from the project basis path to the target system, you enter
\default.iso under "Source". The destination stays empty. The file then will be in the right place on the target system,
namely in the project basis path.
Special case Windows CE: If the target system is a Windows CE terminal and no explicit destination is entered for the project
basis path, the destination \Storage Card\Data is used as a default.

Storage card
The transport service supports a special transport type, where the project is transported directly to a storage card instead of
using a serial or TCP/IP connection.
For that a notebook (or a PC) that can directly access a storage card (PCMCIA, ATA card, Compct Flash, etc.) is necessary.
Attention! It has to be guaranteed, that the CE Runtime and the zenOn6.ini are in the root of the card!
Insert the card in the according slot and check which drive letter is assigned to the card by the operating system. (D:, or E:,
...)
Attention! The following steps are only possible, if "CE project" is activated in the project configuration!
The computer name of the own PC has to be entered in the Remote Transport configuration under "Configuration
parameters", e.g.: HOST=LOCALHOST;
The storage card inserted in the PC and the desired directories have to be entered under "Destination".
"CE - Project basic path" has to be activated. Here the path under which the project then can be found on the storage card
has to be entered. Example: if the storage card is listed as \Storage Card under CE, then c:\Storage Card\project path has to
be entered as "CE - Project basic path"! The C:\ will then automatically be removed by the Remote Transport!

Now a connection to the own PC can be established, and the files are transported to the local storage card.
The path entered under "CE - Project basic path" is written to the zeOn6.ini of the storage card with "Remote project as
start project".
Now the storage card is inserted in the CE terminal and the Runtime can be started.

Monitor administration

Functionality
The tasks of the screen configuration are:
• Output Free output of a picture on any monitor and changing of the assignment of a
picture to a monitor in the Runtime. All pictures (e.g. alarms list, menus, ...)
and functions (e.g. Quit picture), related to the picture or template, must
automatically be taken over.
• Integration Integration of stations with different resolutions into one project (e.g. in
network)
• Operation Mixed operation of 1 and 2 monitor systems
The monitor administration only effects templates and pictures of the control system. Dialog boxes – even those of the
control system – are influenced only by the Windows settings.

3-12 VipWin Users Manual

 System parameterization and parameter documentation

Configuration
The projectation distinguishes between the following levels:
• General settings
• Station settings
• Assignment of virtual monitors to real monitors
• Functions calls for picture selection
General settings
The general settings are made in the context menu of the project under ”Monitor administration…/General”.

Configurable variables:
• Monitor With the button ”Change...” you here define the number of real monitors
• Virtual monitors With the button ”Change...” you here define the number of virtual monitors
which are added to the list below with the names V_01 to V_0n. With
”Rename...” you then can change the names of virtual monitors.
• Computer profiles Computer profiles are generally defined here. With the button ”Copy...” you can
create a new profile based on the currently selected profile. A new property page
is added for each profile. Under ”Profile for this computer” you can select the
appropriate profile for the current computer.
The computer profiles only effect the Runtime.
• Screen size Here the resolution is entered in which the project should run in the Runtime.
This resolution should be set before the start of the project parametrization and
not be changed afterwards, as this can lead to stretching of the pictures, if the
relation width/height of the resolutions is not the same!
Default: For new projects the resolution of the current station is entered here as a
default.
PLEASE NOTE: The first virtual monitor is the default monitor.
Station settings
The selective settings are made in the context menu of the project under ”Monitor administration…/Profile name”.

• Monitor settings
adjust monitor resolution Here you can fix the resolution of the project, i.e. the resolution of the project
is not adjusted to the current resolution.
Scrollbars Scrollbars are displayed in the Runtime, so that you can scroll in projects with
a higher resolution than the monitor.
• Online menu These entries erfer to the menu which is opened in the Runtime, when you

VipWin Users Manual 3-13

System parameterization and parameter documentation

switch to another picture and ”Online select” in the dialogbox ”Virtual

Monitor” is activated.
TimeOut Time (in seconds), for which the Online menu is kept open.
Item ”Cancel” Text in the last line of the Online menu, with which you can cancel the menu.
The character ”%” inserted in this text displays the remaining seconds of the
TimeOut.
ESC-Key Allows the closing of the Online menu with the ESC-key.
• Monitors This list offers information about the real monitors. With the button
”Change...” you can change the parameters for the selected monitor.
• Virtual monitors This list offers information about the virtual monitors. With the button
”Change...” you can change the parameters for the selected virtual monitor.

• name Name of the monitor

• Map to With this entry you can relate a real monitor to another real monitor.
• Position Resolution of the real monitor (e.g. left monitor 0/0 – 1024/768; right monitor
1024/0 – 2048/768)
• Display in OnlineList Define here whether this monitor should appear in the Online list for picture
selection.

• name Name of the virtual monitor

• Online select When activated each time a picture is opened, a menu is opened to select a
monitor.
• Map to The virtual monitor is assigned to a real monitor. This assignment can be
changed in the Runtime with the function ”Monitor assign”.
Functions calls for picture selection
The function ”Switch to picture” now has additional parameters where you can define the target monitor.

• Monitor Here you define the virtual monitor, where the picture schould appear. With the
selection ”relativ zum Aufrufer” the picture is displayed on the monitor from which
it was opened. This selection is e.g. appropriate for menu pictures that are called

3-14 VipWin Users Manual

 System parameterization and parameter documentation

from a picture script. Die Selektion “Auswahl“ bedeutet, daß bei der Bildanwahl
immer das Menü zur Monitorselektion erscheint.
Similar options to those in the function ”Picture switch” now are also available in the function ”Change the picture with
selection”.
If in the Runtime pictures with the option ”Online selct” are switched to, before the picture is opened a menu appears that
allows you to select the real monitor for the picture.

Projecting advice
Before you start projecting the functions for the monitor handling you should plan a general concept keeping in mind the
following points:
You should not work permanently with the monitor selection menu because every opening of a picture then requires two
user inputs instead of one.
The option ”relativ zum Aufrufer” only makes sense for pictures that are opened by picture scripts like e.g. menu pictures.
This option also makes sense with functions like ”Quit blinking of alarms”, ”Close the template” that refer to templates. This
setting cannot be changed in the Runtime.
If pictures are defined as main pictures on another monitor you must bear that in mind when changing the monitor
selection.
For new projects
The following procedure is recommended with new projects:
Before th start of project parametrization the screen resolution has to be set. This resolution should be set before the start
of the project parametrization and not be changed afterwards, as this can lead to stretching of the pictures, if the relation
width/height of the resolutions is not the same!

PLEASE NOTE:
For new projects the resolution of the current station is entered here as a default. If the project (Runtime) should run on a
station with a different resolution, this setting has to be changed before the start of projct parametrization.

Define the appropriate number of virtual (technical) monitors (e.g. for overview and detail pictures, lists, trends, protocols,
etc.). So it is possible to generate different combinations for the monitor selection via the function ”Monitor assign”.
For the change of the monitor selection you should use predefined scripts with the required ”Monitor assign” functions.
The online monitor selection in the Runtime only makes sense if all the pictures that are switched in one step should be
opened on the same monitor.
Templates have to be related to the left monitor.
For existing projects
In existing projects the handling of different monitors can offer the following advantages:
• Surpressing of double pictures for different resolutions
• Integration of computers with different numbers of monitors in one network project
In large projects the change of all ”Switch to picture” functions requires a great amount of work in projecting and testing. So
we recommend the following procedure:
When integrating computers with a small number of monitors (e.g. home control) the overview window should be used. So
all monitors can be accessed quickly and the only change in the project is the integration of the function ”Overview
Window”.
Templates have to be related to the left monitor.

VipWin Users Manual 3-15

System parameterization and parameter documentation

3-16 VipWin Users Manual