User interface
If no parameter has been specified for the module when it was started, the other modules (GEDI and PARA) will not be available although you have a valid license. In this case, the user interface has to be started explicitly with the option -extend. Other options can of course be passed when starting. The correct syntax is:
WCCOAui -extend [...]
You can start the UI with a user name and a password. All other processes such as CTRL or ASCII Manager start as user root by default.It is not necessary to include an entry in the config file.
Other parameters can be specified for the long-form and short-form call:
Parameter | Comment |
---|---|
-m <type> [:<name>] [,<geometry>] | The option "m" allows you to start the UIM module listed under "type". Possible types are "gedi", "para" and "vision". This activates GEDI, PARA or VISION modules. However, the user can access every other module from each of these modules. The optional parameter "name" can be used to assign a name to the module with which you can address the module, for example, in control scripts. Under "geometry" you can specify the position where to display the module on a screen and its size. The syntax is <width>x<height>+<x-coordinate>+<y-coordinate>. If you do not pass the "m" option, the GEDI module will be displayed. |
-p <panel> | The "p" option determines what panel you want the first module of the UIM to display. If you do not pass the option, an empty module will be loaded. |
-silentMode | See below |
-display host name:0.0 | Displays to the computer host name (for example, eiwnt500) |
-help | Displays UIM call options |
-iconBar | Starts a user interface without icon bar |
-menuBar | Starts a user interface without menu bar |
Options for a standalone UI Manager on the client which is running over the HTTP server. Thus panels , which are available only on the server, can be displayed in a UI manager on the client. It is assumed that the client and server are connected via a WinCC OA web server. | |
-server <HTTP-Server-URL> |
The IP address (or the server name) to the WinCC OA HTTP server to access the WinCC OA project from the client. Example:
If there is a redundant server system, the address to the active server has to be specified. In case of a breakdown of the active server the address to the former passive server has to be changed in the source code of the HTML start page, so that the Web Client can access it. |
-proxy <HTTP-Proxy-Server-URL> | The IP address (or server name) to the proxy, which is used together with the HTTP server specified in the option above. |
-noTunne | By default the clients connect to the Event and Data Manager of the HTTP server via a unique tunnel. If a tunnel should not be used, this option can be set. |
-p option with $ parameter
By extending the command line option "-p", you can pass parameters to panels. CTRL scripts parse these $ parameters that are separated by commas.
Possible displays:
WCCOAui -p test,"$valve:Valve1","$pump:Pump1","$motor:Motor1"
Three parameters will be passed.
Three parameters will also be passed in the following case:
WCCOAui -p test,$test:Hallo,$example:World,$value:1
Two parameters will be passed in this case:
WCCOAui -p test,"$Test:Hallo World",$value:1
WCCOAui -p test,"$Test:Hallo World,$value1"
You can only use spaces enclosed in apostrophes.
Command line option -syntax
With the command line option -syntax, you can check the correctness (syntax errors)
of all scripts in the <proj_path>/scripts
directory and all
(or only specific) panels in the directory
<proj_path>/panels
:
-syntax [all, scripts, panels [-p panelname]]
Customizing tool bars and menus
For adding new menus and tool bars to the GEDI, script editor or VISION module the following CTRL function can be used:
-
moduleAddAction() - adds an action into a self created menu or toolbar
-
moduleAddMenu() - creates an individual menu
-
moduleAddSubMenu() - extends the created menu by a submenu
-
moduleAddToolBar() - creates a toolbar
-
moduleSetAction() - enables/disables an already added action