../pvss.htm menu.gif

  Remote UI

If you want to open a user interface on a remote computer over a network or dial-up connection, proceed as follows:

  • A TCP/IP connection is required

  • The same WinCC OA version is required on the server and on the client. At the least, a minimum installation of WinCC OA has to be available on the client computer. Note that if the configuration module (PARA) has to be used in a remote UI project, you must perform a full WinCC OA installation on the client.

  • The project directory must be shared on the server computer (data and event host) for client user. Note that a project that is not executable, cannot be selected as the server project. Under Linux, the project directory has to be  mounted with nfs.

  • The license file of the server must allow enough user interfaces (UIs) for all locally used UIs as well as for all remote UIs.

  • The user interface numbers used on the remote computer must not be in use on the server computer when using a remote UI. This is only valid if you assign fixed numbers to the UI Manager on the remote or server computer by using the command line option "-num". If you do not use this option, the Data Manager automatically assigns the numbers to the UIs in your project.

  • Mixing of 32-bit and 64-bit on client and server is supported. For more information please refer to software-requirements.

caution.gifCaution

When creating a WinCC OA project, the project is not automatically shared. Thus, when the used server project is not shared, you can use Web Client to establish a connection to the project.

caution.gifCAUTION

ActiveX components will not be installed automatically when creating a remote UI project. Install the Microsoft ActiveX Control Pad from:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaxctrl/html/cpad.asp.

caution.gifCaution

Changes on the server project (for example, changes in panels or scripts) always have to be synchronized manually with the client project.

IconExample FOR creating a remote UI project

caution.gifCAUTION

If the configuration module (PARA) should be used in a remote UI project, perform the full WinCC OA installation on the client.

 

  1. Click on the New project button in the project administrator panel.

  2. Select the option Remote UI project.

  3. Define a project name and project path for the project (see figure below).

 

Figure: Create a new Project

Pmon_Consolepanel-79.gif

 

  1. Click Next > and select the server project.

 

Figure: Settings of the remote UI Project

Pmon_Consolepanel-80.gif

note.gifHint

If you have only one HTTP access to the server project you should use the Web Client.

 

  1. Click Next > and create the project. Select the created project from the project administrator panel.

  2. Start the project with the start project button. The console opens and the project will be started. The console should look as in the figure below.

note.gifNote

If you choose the configuration option for your project, no start panel will be shown by default and the starting panel will be grayed out. Visualization allows to display the panels, configuration allows to configure data points. The difference is that configuration allows to do more.

 

Figure: Start the Project

PMON_CONSOLEPANEL-81.GIF

 

The config file of the remote project could look as follows:

 

[general]
pvss_path = "
C:/Siemens/Automation/WinCC_OA/<version>/"
#Remote project path
proj_path = "//eiwrk117/Testproj_de_en"
#Local installation directory
proj_path = "C:/WinCC_OA_Proj/Remote_project"
#Local project path
proj_version = "<version>"
userName = "root"
password = ""
langs = "en_US.iso88591"
event = "Eiwrk117"
#Computer name of the server
data = "Eiwrk117"
#Computer name of the server
pmonPort = 5001

 

The config entries "data"/"event" have to be set correctly and can also be specified using the IP addresses, for example:

 

data = "192.168.0.2"

note.gifNote

The following config entries must be set under Linux on the client:
[ui]
alivePort = <port number>
aliveTimeout = <timeout in seconds> // !=0


See also Entries for different sections.

 

For more information on these config entries, see General settings.

The console writes messages into the log file of the local project <proj_path>/log/PVSS_II.log. Error messages are written into the local log directory only for local managers.

 

If a computer with only one network port should be reachable with more than only one name (name for clients in the local network, name for clients from the Internet), both names can be specified comma separated - in the "data" and "event" entries, for example:

 

data = "server01,WinCC_OA_Server.mycompany.com"
event = "server01,WinCC_OA_Server.mycompany.com"

 

Multiple host names are also defined comma-separated when configuring a redundant network connection. For further information see, Redundant network connections.

caution.gifCaution

The WCCOAascii -out filename command cannot be used when using a remote user interface.

note.gifNote

An "event" entry has to exist for each "data" entry . Both entries have to contain the same host name.

 

Chapter

Content

Remote UI

How to create a remote UI project as well as an example of a config file (of a remote project).

User Interface

Module parameter and further options of the UI.

 

Top Of Page

V 3.11 SP1

Copyright ETM professional control GmbH 2013 All Rights Reserved