ProDesigner - Schleicher Electronic

Operating Manual
ProDesigner
Configuring Software
Operating Manual ProDesigner Version 04/04
Artikel-Nr. 322 154 57
Operating Manual ProDesigner Version 04/04 1

Document conventions
2
ProDesinger Operating Manual
Copyright by
Schleicher Electronic GmbH & Co. KG
Pichelswerderstr. 3 - 5
13597 Berlin, Germany
Phone: +49 30 33005-330
Fax: +49 30 33005-305
Hotline: +49 30 33005-304
www.schleicher-electronic.com
info@schleicher-electronic.com
You can download all our operating manuals free of charge from our
web site at http://www.schleicher-electronic.com or order them by writing to
the following address (please quote order no.):
Schleicher Electronic GmbH & Co. KG
Pichelswerderstr. 3 - 5
13597 Berlin, Germany
® Trademarks
MS-DOS ® , Windows ® , Windows ® 95, Windows ® NT are registered
trademarks of
Microsoft TM Corporation. Delphi ® is a registered trademark of Borland.
All other trademarks or product names are registered trademarks of
their respective owners.
Object Example
File names MANUAL.DOC
Menus / Menu Items Einfügen / Graphik / Aus Datei (Insert /
Graphic / From file)
Paths / Directories C:\Windows\System
Hyperlinks http://www.schleicher-electronic.com
Program listings MaxTsdr_9.6 = 60
MaxTsdr_93.75 = 60
Keys (press first key, let go and
press next key)
(press all keys at the
same time)
Operating Manual ProDesigner Version 04/04

Contents
1 First Contact with ProDesigner.......................................................................................................................... 7
1.1 ProDesigner - the Visualization ............................................................................................................................. 8
1.2 Installation ............................................................................................................................................................. 9
1.2.1 System Requirements ........................................................................................................................................... 9
1.2.2 Starting Setup........................................................................................................................................................ 9
1.2.3 Reinstalling or Updating your Version ................................................................................................................. 10
1.3 The ProDesigner Concept................................................................................................................................... 11
1.3.1 ... and its Elements.............................................................................................................................................. 12
1.4 The ProDesigner Environment ............................................................................................................................ 13
1.4.1 The Components................................................................................................................................................. 14
1.4.2 Output Group....................................................................................................................................................... 19
1.4.3 Input Group ......................................................................................................................................................... 20
1.4.4 Graphics Group ................................................................................................................................................... 20
1.4.5 Symbol Group ..................................................................................................................................................... 20
1.4.6 Special Group...................................................................................................................................................... 21
1.5 Glossary .............................................................................................................................................................. 21
2 Tutorial Application........................................................................................................................................... 21
2.1 Concept + Application Order ............................................................................................................................... 23
2.1.1 Tutorial Application "SAMPLE_1"........................................................................................................................ 23
2.2 Create Project ..................................................................................................................................................... 24
2.3 Process Database ............................................................................................................................................... 26
2.3.1 Inserting Database Objects ................................................................................................................................. 26
2.3.2 Editing Database Objects.................................................................................................................................... 27
2.4 Creating Forms.................................................................................................................................................... 29
2.4.1 Creating a Form .................................................................................................................................................. 30
2.4.2 Inserting Visualization Objects ............................................................................................................................ 32
2.5 Testing your Application on the Development System........................................................................................ 39
2.6 Transferring your Application to the Target System ............................................................................................ 40
3 Menus and Toolbars ......................................................................................................................................... 40
3.1 File....................................................................................................................................................................... 41
3.1.1 New Project ......................................................................................................................................................... 41
3.1.2 Open Project ....................................................................................................................................................... 42
3.1.3 Save Project ........................................................................................................................................................ 43
3.1.4 Save Project As................................................................................................................................................... 43
3.1.5 New Form............................................................................................................................................................ 43
3.1.6 Insert Form .......................................................................................................................................................... 43
3.1.7 Save Form........................................................................................................................................................... 44
3.1.8 Delete Form......................................................................................................................................................... 44
3.1.9 Exit ...................................................................................................................................................................... 44
3.2 Edit ...................................................................................................................................................................... 45
3.2.1 Copy .................................................................................................................................................................... 45
3.2.2 Paste ................................................................................................................................................................... 45
3.2.3 Cut....................................................................................................................................................................... 46
3.2.4 Delete .................................................................................................................................................................. 46
3.2.5 Select All ............................................................................................................................................................. 46
3.2.6 Edit Template ...................................................................................................................................................... 46
3.2.7 Lock Object ......................................................................................................................................................... 46
3.2.8 Save As Text ....................................................................................................................................................... 47
3.3 View..................................................................................................................................................................... 48
3.3.1 Process Database ............................................................................................................................................... 48
3.3.2 Project Administration ......................................................................................................................................... 48
3.3.3 Properties ............................................................................................................................................................ 50
3.3.4 Compiler Status................................................................................................................................................... 50
3.3.5 Designer .............................................................................................................................................................. 51
3.3.6 Error Log ............................................................................................................................................................. 51
3.4 Configuration (Settings)....................................................................................................................................... 52
3.4.1 Development ....................................................................................................................................................... 52
3.5 Start..................................................................................................................................................................... 54
3.5.1 Compile Form...................................................................................................................................................... 54
3.5.2 Compile Process Database................................................................................................................................. 54
Operating Manual ProDesigner Version 04/04 3

3.5.3 Compile Project ................................................................................................................................................... 54
3.5.4 Start..................................................................................................................................................................... 55
3.6 Tools.................................................................................................................................................................... 56
3.6.1 Index Texts.......................................................................................................................................................... 56
3.6.2 Symbols............................................................................................................................................................... 57
3.6.3 Recipes ............................................................................................................................................................... 58
3.6.4 Form-/Project Report........................................................................................................................................... 61
3.6.5 Create Image File................................................................................................................................................ 65
3.6.6 Transfer ............................................................................................................................................................... 66
3.7 ? .......................................................................................................................................................................... 67
3.7.1 Help ..................................................................................................................................................................... 67
3.7.2 Info ...................................................................................................................................................................... 67
4 Process Database ............................................................................................................................................. 67
4.1 General................................................................................................................................................................ 69
4.1.1 Insert ................................................................................................................................................................... 69
4.1.2 Text Editor and Dialog Window ........................................................................................................................... 70
4.1.3 Parameters for (nearly) every Definition.............................................................................................................. 71
4.1.4 Table of Database Object IDs ............................................................................................................................. 72
4.2 ... during Runtime ................................................................................................................................................ 73
4.2.1 Object Processing ............................................................................................................................................... 73
4.3 Alarm ................................................................................................................................................................... 74
4.3.1 Overview ............................................................................................................................................................. 74
4.3.2 Bit ........................................................................................................................................................................ 75
4.4 Variable ............................................................................................................................................................... 76
4.4.1 Overview ............................................................................................................................................................. 76
4.4.2 Digital .................................................................................................................................................................. 77
4.4.3 Word.................................................................................................................................................................... 78
4.4.4 Long Word........................................................................................................................................................... 79
4.4.5 Floating Point ...................................................................................................................................................... 80
4.4.6 BCD Variable....................................................................................................................................................... 81
4.4.7 Text ..................................................................................................................................................................... 82
4.5 Formula and Condition ........................................................................................................................................ 83
4.5.1 Overview ............................................................................................................................................................. 83
4.5.2 Syntax Diagrams ................................................................................................................................................. 84
4.5.3 Formula ............................................................................................................................................................... 86
4.5.4 Condition ............................................................................................................................................................. 87
4.5.5 Jump Object ........................................................................................................................................................ 88
4.6 Diverse Objects ................................................................................................................................................... 89
4.6.1 Overview ............................................................................................................................................................. 89
4.6.2 Recipe Object...................................................................................................................................................... 89
4.6.3 Structure Object .................................................................................................................................................. 92
4.6.4 Exit Object ........................................................................................................................................................... 94
4.6.5 System Object ..................................................................................................................................................... 95
5 Process Database Parameters......................................................................................................................... 97
5.1 Image .................................................................................................................................................................. 98
5.2 Address ............................................................................................................................................................... 99
5.3 Number.............................................................................................................................................................. 100
5.4 Bit Number ........................................................................................................................................................ 101
5.5 Formula ............................................................................................................................................................. 101
5.6 IF,THEN,ELSE .................................................................................................................................................. 102
5.7 Comment........................................................................................................................................................... 102
5.8 Mode ................................................................................................................................................................. 103
5.9 Name................................................................................................................................................................. 103
5.10 Priority ............................................................................................................................................................... 103
5.11 Source Object.................................................................................................................................................... 104
5.12 Jump Width ....................................................................................................................................................... 104
5.13 Status ................................................................................................................................................................ 104
5.14 Text Index.......................................................................................................................................................... 104
5.15 Drivers ............................................................................................................................................................... 105
5.16 Conversion ........................................................................................................................................................ 105
6 Visualization Objects ...................................................................................................................................... 105
4
Operating Manual ProDesigner Version 04/04

6.1 Form .................................................................................................................................................................. 106
6.2 Output................................................................................................................................................................ 106
6.2.1 Variable Output ................................................................................................................................................. 106
6.2.2 Index Text.......................................................................................................................................................... 108
6.2.3 Bar Graphics ..................................................................................................................................................... 109
6.2.4 Alarm Line ......................................................................................................................................................... 110
6.2.5 Alarm List .......................................................................................................................................................... 111
6.3 Input .................................................................................................................................................................. 112
6.3.1 Variable Input .................................................................................................................................................... 112
6.3.2 Form Change .................................................................................................................................................... 113
6.3.3 1 Pin Switch....................................................................................................................................................... 114
6.3.4 2 Pin Switch....................................................................................................................................................... 114
6.4 Graphic.............................................................................................................................................................. 115
6.4.1 Picture ............................................................................................................................................................... 115
6.4.2 Static Text ......................................................................................................................................................... 116
6.4.3 Shape ................................................................................................................................................................ 116
6.4.4 Grid.................................................................................................................................................................... 117
6.4.5 Line.................................................................................................................................................................... 117
6.5 Symbols............................................................................................................................................................. 118
6.5.1 Symbol .............................................................................................................................................................. 118
6.5.2 Moving Symbol.................................................................................................................................................. 119
6.6 Special............................................................................................................................................................... 120
6.6.1 Formula ............................................................................................................................................................. 120
6.6.2 Condition (IfElse)............................................................................................................................................... 120
6.6.3 Date and Time................................................................................................................................................... 121
6.6.4 KeyCoding......................................................................................................................................................... 122
7 Object Properties ............................................................................................................................................ 122
7.1 General.............................................................................................................................................................. 124
7.1.1 Variable Dialog Box........................................................................................................................................... 124
7.1.2 Input .................................................................................................................................................................. 126
7.2 ... in Alphabetical Order..................................................................................................................................... 128
7.2.1 AddText ............................................................................................................................................................. 128
7.2.2 Align .................................................................................................................................................................. 128
7.2.3 AutoScale .......................................................................................................................................................... 129
7.2.4 Bit ...................................................................................................................................................................... 129
7.2.5 CharCount ......................................................................................................................................................... 129
7.2.6 CharHeight ........................................................................................................................................................ 129
7.2.7 CharWidth ......................................................................................................................................................... 130
7.2.8 ColorBack.......................................................................................................................................................... 130
7.2.9 ColorLine ........................................................................................................................................................... 130
7.2.10 Comment...................................................................................................................................................... 130
7.2.11 Condition...................................................................................................................................................... 131
7.2.12 DataSource .................................................................................................................................................. 131
7.2.13 DecPoint ...................................................................................................................................................... 131
7.2.14 DefaultKey ................................................................................................................................................... 132
7.2.15 Direction....................................................................................................................................................... 132
7.2.16 Display ......................................................................................................................................................... 132
7.2.17 Form............................................................................................................................................................. 132
7.2.18 Format.......................................................................................................................................................... 133
7.2.19 Global........................................................................................................................................................... 133
7.2.20 Height........................................................................................................................................................... 133
7.2.21 Hide (from Vers. 1.20: Visible) ..................................................................................................................... 133
7.2.22 HideBit (from Vers. 1.20: VisibleBit)............................................................................................................. 133
7.2.23 Inverse ......................................................................................................................................................... 134
7.2.24 Key............................................................................................................................................................... 134
7.2.25 KeyCoding ................................................................................................................................................... 134
7.2.26 KeyDown...................................................................................................................................................... 134
7.2.27 KeyExit ......................................................................................................................................................... 135
7.2.28 Key-IOFF...................................................................................................................................................... 135
7.2.29 Key+ION ...................................................................................................................................................... 135
7.2.30 KeyMode...................................................................................................................................................... 135
7.2.31 KeyPgDown ................................................................................................................................................. 136
Operating Manual ProDesigner Version 04/04 5

7.2.32 KeyPgUp...................................................................................................................................................... 136
7.2.33 KeyQuit ........................................................................................................................................................ 137
7.2.34 KeyQuitAll .................................................................................................................................................... 137
7.2.35 KeyUp .......................................................................................................................................................... 137
7.2.36 Left ............................................................................................................................................................... 137
7.2.37 Lines ............................................................................................................................................................ 137
7.2.38 LineType ...................................................................................................................................................... 138
7.2.39 LineWidth ..................................................................................................................................................... 138
7.2.40 Margin .......................................................................................................................................................... 138
7.2.41 MaxValue/MinValue ..................................................................................................................................... 139
7.2.42 Mode ............................................................................................................................................................ 139
7.2.43 Name............................................................................................................................................................ 139
7.2.44 Picture.......................................................................................................................................................... 140
7.2.45 SaveBkGnd.................................................................................................................................................. 140
7.2.46 SetEndPos ................................................................................................................................................... 140
7.2.47 ShadowDepth............................................................................................................................................... 141
7.2.48 ShapeType................................................................................................................................................... 141
7.2.49 StepBit ......................................................................................................................................................... 141
7.2.50 SwitchMode.................................................................................................................................................. 141
7.2.51 SymbolMaxOff/SymbolMinOff ...................................................................................................................... 142
7.2.52 SymbolOffset................................................................................................................................................ 142
7.2.53 Symbols ....................................................................................................................................................... 142
7.2.54 SymbolVariable ............................................................................................................................................ 142
7.2.55 TabIndex ...................................................................................................................................................... 142
7.2.56 TextOffset .................................................................................................................................................... 143
7.2.57 Top............................................................................................................................................................... 143
7.2.58 Width............................................................................................................................................................ 143
7.2.59 Visible (from Vers. 1.30: Hide) ..................................................................................................................... 143
7.2.60 VisibleBit (from Vers. 1.30: HideBit)............................................................................................................. 143
7.2.61 WantReturn.................................................................................................................................................. 143
7.2.62 XValueMax / YValueMax ............................................................................................................................. 143
8 Editing Objects in the Designer ..................................................................................................................... 144
8.1 Lining up Objects............................................................................................................................................... 145
8.2 Bringing Objects to the Top of the Display ........................................................................................................ 145
8.3 Putting Objects to the bottom of the Display ..................................................................................................... 145
8.4 Alignment Menu ................................................................................................................................................ 146
8.4.1 Basic Knowledge:.............................................................................................................................................. 146
8.5 Display Tab Order ............................................................................................................................................. 150
8.6 Form List ........................................................................................................................................................... 150
8.7 Zoom Factor ...................................................................................................................................................... 151
9 Error Messages ............................................................................................................................................... 151
9.1 Errors on the Development System .................................................................................................................. 153
9.2 Errors on the Runtime System .......................................................................................................................... 154
9.2.1 Error Number (Error) ......................................................................................................................................... 155
9.2.2 Object Number (Object) .................................................................................................................................... 156
9.2.3 Object Type (Object type) ................................................................................................................................. 156
9.2.4 Position in the "DTX" or "PTX" file..................................................................................................................... 156
9.2.5 Short Description or Object Name..................................................................................................................... 156
9.3 Differences between Runtime and Simulation .................................................................................................. 157
10 Lists, Codes + Interfaces................................................................................................................................ 157
10.1 Keyboard Codes................................................................................................................................................ 158
10.2 File List, Directory Structure .............................................................................................................................. 160
10.3 Files................................................................................................................................................................... 162
10.3.1 All important Files sorted according to Type................................................................................................ 162
10.4 System Variables .............................................................................................................................................. 164
10.4.1 Read-Only System Variables....................................................................................................................... 164
10.4.2 System Commands...................................................................................................................................... 165
10.5 Key Functions during the Simulation................................................................................................................. 166
10.6 System Limits .................................................................................................................................................... 166
10.7 The COP-Family Fonts...................................................................................................................................... 167
6
Operating Manual ProDesigner Version 04/04

1 First Contact with ProDesigner
Operating Manual ProDesigner Version 04/04 7

1.1 ProDesigner - the Visualization
ProDesigner is a Visualization Software program for COP terminals
running under Windows ® 95/NT. The software enables the creation
and testing of applications on your development computer.
ProDesigner is an OEM-version for the Schleicher Company,
developed from the standard visualization VisiWinDOS ® .
8
Please Note
All project dialogs are directly loaded via menu control into the target
system.
Please make sure that you keep the graphic resolution requirements
of your target system in mind!
COP Handy 256 x 64 Pixel
COP 320 x 240 Pixel
Functions Process dependent data input and output:
Variables (digital, long word, floating point, word, text etc.)
can be displayed anywhere as a value or as a bar graphic.
Mathematical and logical functions, as well as IF THEN
ELSE conditions allow the construction of control and
monitoring functions. The contents of a variable of one or
more pictures can be saved as a recipe and can, whenever
required, be transferred as a block to the control.
Alarms Output and analysis of alarm messages.
Language Applications for various languages may be realized (e.g.
English) by using index texts.
Operating Manual ProDesigner Version 04/04

1.2 Installation
1.2.1 System Requirements
Please Note
1.2.2 Starting Setup
Please Note
Windows® Development PC Target System
• Windows ® 95
• Max. required hard disk space
10 MB (actual required space is
dependent on the installed system
components)
• Recommended graphic resolution:
800 x 600 Pixel
• If the installation is to be made on a
FAT32 partition no "long" path names
may be used, because the simulation
can only process "short" DOS
compatible path names.
• COP
(320 x 240 Pixel)
• COP Handy
(256 x 64 Pixel)
The installation is started via the SETUPALL.EXE program located on
the CD.
If the autorun function of the CD-drive is not active you can start the
installation as follows. You can either double click SETUPALL.EXE
from inside the Explorer, or type SETUPALL.EXE in the dialog box
that appears:
Start / Run
You will then be taken through all necessary installation (Windows ® -
Install-Shield). The installation can be done in either English or
German.
There are three installation variants at your disposal:
Standard (Development with examples and pictures),
Minimal (Development without supplementary examples and
pictures),
Custom (User defined - installation of supplementary elements
such as examples and pictures).
Software deinstallation is done via:
Start / Settings / Controls / Add/Remove Program
Please also read the README.TXT file on CD in directory
\ProDesigner.
Please note that all operating system texts are displayed using the
language you choose during the installation or upgrading of your
operating system.
If the program is to be installed to a network server a drive must be
mapped (Drive Mapping). An installation via a path identifier according
to UNC convention is not possible.
Operating Manual ProDesigner Version 04/04 9

1.2.3 Reinstalling or Updating your Version
Please Note
10
Before you install or update to a newer version, the existing version
should be deinstalled via Start / Settings / Controls / Add/Remove
Program. All existing project settings that are not deleted during a
deinstallation (registered projects, settings in the TRANSFER.BAT file)
are saved in the USER.INI file.
What has happened on your Hard Disk Drive?
The following sub-directories were created in the directory chosen
during installation:
Pictures : Contains all picture files.
Sample_1 : Contains a sample project.
Utilities : Program for data transfer between PC and COP.
Visi : Contains the files required for the simulation and the
runtime.
Please do NOT rename or move the main directory or any subdirectories
contained in the main directory.
Please note that all sample demos are automatically overwritten
during a reinstallation or update.
Operating Manual ProDesigner Version 04/04

1.3 The ProDesigner Concept
The developer system is based on the creation of dialog and process
descriptions. These are created using the developer system
ProDesigner under Windows, and run on the operating system via a
runtime module (runtime kernel / runtime). The core of the
visualization is the process database. It contains the definition of the
used interface between the visualization and the control system /
terminal. This must be defined for every application. The process
database also contains the descriptions of all data points (process
constants and/or process variables respectively) that should be
visualized. This description contains all information about memory
location and variable data type, as well as information about the path
of communication along which data is transferred. The process
database itself is not displayed. The only parts visible to the User are
the control dialogs (Forms).
The ProDesigner developer system operates project orientated. This
means that all control dialogs (Forms) created by the User, as well as
the process database, are allocated to one project. Due to the fact
that the runtime system is bound to the control device, the application
may be tested on the developer system using a simulation program
without having to actually make a connection to the target system.
Once development, design and testing have been completed, you
may transfer all dialogs and the process database via a serial
connection to the target system where these are then processed by
the runtime kernel. The modular construction of the system, whereby
the forms and the process database are kept separately from each
other, allows you to exchange individual modules between various
application. A communications driver port allows you to expand the
system by adding new communication drivers.
Operating Manual ProDesigner Version 04/04 11

1.3.1 ... and its Elements
Development: Windows 95 ®
Runtime: COP / COP-Handy
Runtime Kernel
Communication Drivers
Simulation in the DOS Box
12
ProDesigner is a software program designed to run under
Windows 95 ® .
Menu control, double and single clicks using the mouse, saving,
loading, clipboarding etc. are all handled the same way as other
Windows ® programs.
Your application/development on the COP / COP-Handy machine is
referred to as "Runtime".
The runtime kernel is the core of the visualization. All functions (data,
pictures, formulas, drivers, etc.) of your application are collected here
where the kernel organizes, sorts and processes them.
Connecting the visualization to a process is done using the runtime
kernel’s communication module.
During the development phase you may test your application in order
to see what it will look like on the target system.
During this simulation no connection to the control is made. In other
words, no data is exchanged between PN and PLC.
Operating Manual ProDesigner Version 04/04

1.4 The ProDesigner Environment
Program Start
ProDesigner is started as every Windows ® program is:
Start / Programs / ProDesigner
If you are accustomed to Delphi or Visual Basic then the screen that
appears will not be new to you and you can skip the following
explanations.
After starting ProDesigner the last project to be processed is
automatically loaded and displayed.
"Mouse-less" between the Windows
An active Window is displayed by the blue highlighted taskbar.
Simply clicking the mouse on the corresponding window activates the
Window.
If you (for whatever reasons) do not use the mouse, choose the menu
point View in order to switch between the Properties, Compiler,
Designer, etc. windows.
Operating Manual ProDesigner Version 04/04 13

1.4.1 The Components
14
Menu Toolbar Contains all functions, from New Project to Start
runtime simulation, needed to create an application.
Symbol Toolbar The most commonly used functions, usually menu
toolbar functions, are placed here as icons.
ProDesigner
Objects
The visualization objects make up (together with the
process database) the core of the application. The
variable input or output method is determined using
the supplied visualization objects. You decide
whether an input into an application is made using
either a switch, a slide bar or via text etc., and
whether an output value is displayed as a trend, bar
graphic, text or symbol (static or moving) etc.
If you click a ProDesigner object the content of the
property page changes correspondingly.
Object Groups The visualization functions are split up into the
following groups:
Output, Input, Graphics, Symbols and Special.
Typical output functions are for example, variable
output as a text or as a bar graphic.
Clicking its respective "tag" activates an object
group.
Properties Every ProDesigner object has a list of properties that
are displayed in the properties window where its
settings can be adjusted. In this "table" you can
determine the size and color of the object, the min.
and max. limits of the object, the fonts, and most
importantly the variables to which the object is linked.
Properties are component parameters that determine
the behavior of an object.
The Form Also called the Designer. It is the "output area" of
your program, in other words the area in which your
program runs during runtime.
Inside of this area you graphically construct and
create your screen forms. ProDesigner objects are
positioned and graphics are embedded.
The size of the form is dependent on the graphics
resolution of the target system. Following graphic
resolutions should be noted:
256 x 64 Pixel black and white
320 x 240 Pixel black and white
Status Line Displays the name of, and the comment on the
chosen object.
Form Register Most projects contain more than just one form. The
individual project forms are stacked to allow simple
jumping between the forms. The procedure is similar
to Excel where you can switch between the individual
forms using a register. Switching from one form to
another automatically saves the changes made to
the latter form.
Cursor Position This line contains the co-ordinates (X/Y co-ordinates)
in Pixels of current cursor position. 0/0 are the coordinates
of the top left position.
Operating Manual ProDesigner Version 04/04

Menus, Buttons, Shortcuts
File
See chapter 3
New Project
Open Project
Save Project
Operating Manual ProDesigner Version 04/04 15
+
+
+
Create a new project.
A project, an application is made up of
many various parts. These include data,
drivers, pictures etc. A project
administration keeps all of these parts
where they are supposed to be. This
project administration forces you to assign
applications unique names and paths.
Further settings can be made via the menu
point Project / Configuration.
Using this button you can load and edit an
already existing project. Click the open
project button and a file list box appears in
which you can select the project by double
clicking the project name.
The active project is saved. Once the save
project button is clicked the save process
cannot be aborted!
Save Project As Same as new project. However you can
save your project to a different drive and
under a different path.
New Form
Insert Form
Save Form
Delete Form
A new, empty form is added to the project.
The form currently in use is saved and the
new form receives the focus, in other
words, the new form is the active form.
Copies and inserts an existing form
(including forms from other projects) into
the active project.
The active form is saved.
Exit Exits ProDesigner
If you click this button an alarm box
appears alerting you to the fact that you
wish to delete the active form. You are
asked to confirm this by clicking the
appropriate button. If you click "yes" the
active form is permanently deleted and
cannot be reconstructed, even if the form is
in the trash bin!

Editing Functions
Please Note
16
Copy
Paste
Cut
Delete
+
+
+
+
Selected objects are copied on to the
clipboard for further processing.
Objects are pasted from the Windows ®
clipboard (back) into the active form. The
pasted objects appear at the left top corner
of the form. The insertion of objects can be
repeated as many times as you like, even
into different forms. If a group containing
several objects was copied on to the
clipboard then this group’s object order is
retained.
The selected object is removed from the
active form and moved on to the Windows ®
Clipboard.
The selected object is removed from the
form.
Attention! UNDO function only available
from version 2.0 onwards!
The Windows ® Clipboard only contains the last objects that were
moved on to it. A ProDesigner object moved on to the clipboard is
lost if you use the clipboard in any other Windows ® application.
Select All
Save Template
Load Template
Edit Template
Lock Object
+ All objects in the active form are
+
highlighted (selected).
Forms, individual objects or object groups
can be saved as templates. Available from
version 2.0 onwards.
Objects in a form can be statically
fixed/locked. All statically locked objects
can be edited and processed normally via
the properties window.
Save As Text All objects are saved in ASCII format.
Operating Manual ProDesigner Version 04/04

View
Configuration
Start
Process
Database
Project
Administration
Activates the process database editor
window. Here you may insert variables,
drivers, alarm definitions, etc…
Opens a window containing an overview of
all forms, components and the current
project’s compilation status.
Properties Activates the object’s properties window.
Compiler Status Activates the compiler line
Designer Activates the form window
Error List
Places the current form’s error list into the
foreground (in place of the compiler line). If
no error list exists for this form, the next
form with an error is loaded into the
Designer and the corresponding error is
displayed.
Development Settings for the developer environment,
e.g. align objects to grid, set language etc.
Compile Form
Operating Manual ProDesigner Version 04/04 17
+ The objects of the currently active form are
Compile process
database +
Compile project
Start
+ All objects belonging to the project (the
compiled for runtime and checked for
errors.
The process database objects are
compiled.
process database and all visualization
objects) are compiled for the runtime and
checked for errors.
The simulation is started. The project and
process database must be compiled before
the simulation is started. If the project and
process database were not compiled then
they are automatically compiled and
checked for errors as soon as the start
button is clicked. If no errors were detected
the simulation is started. If errors were
detected an error box containing all error
messages is displayed.

Tools
?
18
Index Texts
... are output texts that are listed in a table where
they are assigned numbers. In the actual project
the numbers, not the actual texts, are referred to.
Multi-language text output (for online language
changes) can also be easily realized.
Symbols The symbol tool allows you to create graphic
symbols.
The symbols are administrated in a project
relevant manner.
Recipes Opens a dialog window in which recipes can be
created and edited.
Recipes are administrated in a project relevant
manner.
Form Report Creates a report of the currently active form in
RTF or CSV format respectively.
Project Report Creates a report of the complete project in RTF
or CSV format respectively.
Create Image
File
Creates an image file of all files belonging to a
project. This image file is then loaded into the
target system via the transfer command.
Transfer Transfers the created application to the target
system.
The transfer is Batch controlled (via the file
Transfer.bat in the utility directory).
Help
The online help.
Info Displays the version number of the currently
installed ProDesigner software.
Operating Manual ProDesigner Version 04/04

ProDesigner Objects + Object Groups
See chapter 6
1.4.2 Output Group
Click one of the buttons in the toolbox.
Position the mouse in the form, press and hold the left mouse button
and pull open (using the mouse) a box. As soon as the box has the
size you wish it to have, release the left mouse button and you will
have a (usually white) box.
This group contains objects used to display process variables as
simple number and text outputs, alarm messages or as bar charts.
These objects receive the property DataSource. Under DataSource
the process database variable’s name is entered enabling objects to
be coupled to the process.
Variable Output Output of a process variable using various
representations.
Index Text Output of index texts. The texts are
controlled via the process data.
Bar Charts Colored rectangles that "move up and
down".
Alarm Line Output of the triggered alarm with the
highest priority in a line inside of a picture.
Alarm List List of all triggered alarms.
Operating Manual ProDesigner Version 04/04 19

1.4.3 Input Group
1.4.4 Graphics Group
1.4.5 Symbol Group
20
This group contains objects that allow the user to directly intervene in
and manipulate a process. These objects allow the user to enter
numbers, flip switches or to control the application via a form change.
Variable Input Variable input inside of a form.
Form Change Changes screen forms via the keyboard.
Switch Switch function, 1 pin
Switch On/Off Switch function, 2 pins
The two following objects can be used to create the application’s static
background.
The objects cannot be changed during runtime.
Static Text Inserts a static text into the background of
the form.
Grid Inserts and displays a grid.
Line Inserts and displays horizontal, vertical,
diagonal and free-hand lines.
Shape Inserts elements such as circles, rectangles
etc. used for graphic picture creation.
Picture Inserts a picture into the background of the
form.
This group contains all objects needed to display animated graphics
during Runtime.
Symbol Represents a symbol with respect to the
corresponding variable value.
Moving Symbol Motion of a symbol with respect to the
corresponding variable value.
Operating Manual ProDesigner Version 04/04

1.4.6 Special Group
1.5 Glossary
2 Tutorial Application
This group contains all objects with which the user can realize
conditions, formulas, a recipe administration, date and time.
Formula Inserts a formula
(e.g. w0=w0+1).
Condition Inserts a conditional block inside of a form.
Date and Time Displays date and time in various formats.
Key Coding Used to (re-)code keys in order to
accommodate the application to devices
with different keyboards.
Form Process picture
User Dialog
Form
Page
Form Change The form displayed on the screen/page is changed to
a different form. Occurs both via keys and via
process variables.
Components A component is an object with properties such as a
variable definition in the process database, or a
variable output inside of a picture.
System variable These variables are administrated by the runtime
system and usually contain system information such
as the time.
see chapter 10.4
Drivers Drivers are runtime system modules or
communication channels that control the transfer of
data between the visualization system and the
connected PLC or control device.
Picture Database A compiled form is referred to as a picture database.
Variable(s) Is a constant or value assigned to the process
such as "pressure", "No." etc. These are defined in
the process database.
Operating Manual ProDesigner Version 04/04 21

22
Operating Manual ProDesigner Version 04/04

2.1 Concept + Application Order
The following tutorial will introduce you to the ProDesigner and
several of its functions. The application is a very simple one and is
restricted to basic ProDesigner functions.
The complete application can be found under
PRODESIGNER\SAMPLE\SAMPLE_1\SAMPLE_1.VWP.
Usual order for creating a new project:
1. Create project
2.1.1 Tutorial Application "SAMPLE_1"
Enter the directory/path where the project
should be saved.
2. Create the process database
Definition of the process variables (linking the
PLC address to the symbolic name).
E.g. alarms, formulas, digital and word
variables, etc.
3. Construction of forms using animated objects.
Insertion of visualization objects such as bar
graphics, text or variable output.
4. Starting and simulating the application on the
development system.
5. Transfer of the application to the target
system.
Here Chap./page
2.2 3/40
2.3 4/67
2.4 6/105
Operating Manual ProDesigner Version 04/04 23
2.5
2.6

2.2 Create Project All directories needed by the project are created. Furthermore, an
empty (blank) form is opened and all standard initialization files are
created.
24
Menu Activation File / New Project
Or
see also Chapter 3
Dialog box
or +
Project Name Enter a name for your project. The name may only
have a max. of 8 characters. Letters with the
exception of ä,ö,ü and ß, numbers and the
characters "-" and "_" may be used. The name must
be DOS compatible.
Project Directory It is recommended to create a new directory for every
individual project, because each project contains a
large amount of data.
Registered
Projects
Paths
Disk Drives
When you create a new project directory, the subdirectories
Develop, Picture and Runtime are
automatically created. The ProDesigner
automatically distributes data into the corresponding
sub-directories.
Shows you all registered ProDesigner projects.
A registered project means that it was a projected
created or copied (using Save As) using ProDesigner
functions.
Disk drive and directory destination where the
project should be created and saved.
Operating Manual ProDesigner Version 04/04

Please Note
Please Note
You can also directly insert this destination into the
project directory line.
Whenever a new project is created you must choose the target
system. This setting cannot be changed anywhere else. If the
installation is to be made on a FAT32 partition no "long" path names
may be used, because the simulation can only process "short" DOS
compatible path names.
You must declare the target system whenever you create a project.
This setting cannot be changed.
Operating Manual ProDesigner Version 04/04 25

2.3 Process Database
The process database is the central file of your application. All links to
the PLC, as well as internally used variables must be defined in the
process database.
26
Menu Activation View / Process Database
Or
or
see also Chapter 5
When a new project is created an "empty" process database is
displayed. You should enter all relevant project information into the
header of this file.
Position the cursor in the first line.
The insert button opens the "enter new object" list box from which you
may insert objects into the process database.
2.3.1 Inserting Database Objects
Choose an object (e.g. Variable) from an object group of choice.
Confirm the insertion by clicking OK. This now opens an input dialog
box for the chosen object.
Operating Manual ProDesigner Version 04/04

2.3.2 Editing Database Objects
This dialog box contains all input fields needed to create the object.
Please enter the following values for the tutorial:
Name Designation of the object. May only be used for one
object (unique) and is used to identify an object.
Driver Defines how this variable is linked to the process.
Structure The variable is part of a data
structure defined in the process
database.
Internal This type is created in the
visualization’s internal memory. This
memory is not linked to the PLC.
LED Special driver used to control the
LEDs on the keyboard.
Shared-RAM Link to a PLC address.
RK512 Connect made via the control
device’s RK512 protocol
Address Contains a PLC specific address designation. It
defines the location of the data inside of the PLC.
Due to the fact that the entry is “internal” no address
is needed. You can therefore enter a 0 into this field.
For a link to the PLC you should choose an address
corresponding to the documentation of your control
device.
Number This value defines the number of reserved objects
and the number of objects to be transferred.
(Definition of fields)
Factor Contains a multiplication factor with which the
variables should be multiplied. (Used for example in
unit conversion).
Map Area Defines the PLC variables’ value limits that should be
mapped in the variable.
Operating Manual ProDesigner Version 04/04 27

Please Note
28
whole word -32567 to +32568
lowest and highest byte -127 to +128
Attribute Defines the type of access to the PLC variable’s
memory.
Combined Read/write access
enabled
Read only PLC values are read
enabled only
Write only PLC values are write
enabled only
This program distinguishes between small and capital lettering.
"Temp" and "temp" therefore refer to two complete different objects.
You should therefore be careful when naming or labeling objects.
In order to create further objects of the same type just press the
"Insert" button.
The inputted data in written into the process database and the input
catalog updated (the object name is generated automatically).
If you wish to edit an existing object double-click the respective line in
the editor. This automatically activates and opens the corresponding
input dialog.
Once all process variables needed for this example have been
defined, click the Compile button. The process database now runs
through a compiler during which all files needed for the runtime are
created.
If no errors occurred (shown in the lower Window), input is terminated
and you switch to the form environment by clicking OK.
Operating Manual ProDesigner Version 04/04

2.4 Creating Forms After all process variables and internal variables have been defined in
the process database you may begin creating the forms for your
application.
Please Note
A form is constructed using a number of various objects. Changing the
properties of the objects contained in the form can influence the
appearance and function of your application.
The object properties can be placed in the following groups according
to their functions:
1. Static Properties
are graphically integrated into a form’s background whenever a
picture is created. These properties cannot be changed during
runtime. An example for a static property is ShadowDepth. This
property determines the width of the frame around an object (i.e.
variable output).
Some objects only possess "static properties". The Picture object
found in the Graphics register is such an object.
2. Dynamic Properties
are animated by the system during runtime, for example the output
of a variable value via the property DataSource. Some objects only
possess "dynamic properties". The object Switch 1 pin is such an
object.
The appearance of your application, determined by the properties of
the objects in the forms, is displayed on the development system
during the development phase. You can examine the appearance of a
form in more detail by clicking the right mouse button inside the
Designer window. This action opens a zoom box where you can
choose a magnification factor for better viewing.
Objects that are not visible during runtime, such as formulas or
conditions, are displayed as symbols (these objects cannot be
changed).
Now we will describe the forms "PG3" and "PG8" contained in
SAMPLE_1.
A valid form must always contain at least one object with dynamic
properties.
Operating Manual ProDesigner Version 04/04 29

2.4.1 Creating a Form
Please Note
30
Picture Object
Static Text
Date and Time Output
Variable Input
Variable Output
Switches
Bar Graphs
You can add a new empty form to your application via the menu
File / New Form.
This form is automatically named. This name is displayed in the
project administration and can be changed. It should be noted that this
name is unique inside of the project.
Open the menu File and click Insert Form in order to insert and use a
form from an existing project as a template.
Every application can contain up to a maximum of 50 forms.
Every application must have a "Starting Form" defined. This form is
the first form displayed when the application is started on the runtime
system.
Defining the starting form is done in the menu
View / Project Administration
by double-clicking the form list box of the corresponding form.
Operating Manual ProDesigner Version 04/04

Please Note
The form is the fundamental component of the process display. The
form contains properties via which you can influence the appearance
of the process display. In order to be able to set and adjust these
properties you just have to click the form displayed in the Designer
using the mouse. All object properties are displayed inside of the
Inspector. Below is a screenshot showing all the object properties in
the Inspector for the form:
• ColorBack:
used to set the
background color (if no
"picture" was selected).
• Inverse:
The background colors
are switched.
• Form Change:
Definition of the keys
used to switch between
forms.
• Name:
contains the form’s object
name. This name must be
both unique inside of the
form and the project.
• Picture:
Name of a background
picture. This picture is
expanded to fit the whole
screen.
BMPs can be used as background pictures. These pictures can be
created using a graphics editor of choice.
It should be noted that the target system only allows monochrome
pictures with the dimensions: 256 x 64 Pixel (COP Handy).
If you ignore these settings then you graphics will be distorted and be
displayed in false colors.
The following should be done to insert a picture into an object:
Choose the background picture from the Picture dialog list box. Once
chosen the picture is copied into your project directory. This
guarantees that all graphics required by a project are attributed to the
project.
Once these properties have been processed you can move on to
inserting the visualization objects into the form.
Operating Manual ProDesigner Version 04/04 31

2.4.2 Inserting Visualization Objects
Picture
32
All objects that are available for the construction of an application are
listed in a special toolbar. This toolbar places all the objects into
functional groups. The toolbar above contains 5 functional groups.
The buttons in each group represent the objects available in this
group.
In order to create an object in a form you must click the relevant object
listed in the toolbar and pull open a rectangle in the form. This is done
by pressing and holding down the left mouse button whilst pulling
open a box on the screen. Release the mouse button to complete this
action.
Listed below are the descriptions for the objects. These object
descriptions only contain the most common and important properties.
For a complete description:
See chapter 6+ 7
Via the tag Graphic / Picture.
The parameters for this object are displayed in the inspector. Below is
a list containing the most important properties:
Picture Name of the picture file to be displayed
in the object.
AutoScale Scales the size of the object to exactly
match the size of the graphic picture.
Inverse Inverts the graphic’s colors.
Operating Manual ProDesigner Version 04/04

Static Text
Time and Date
Form Change
Via the tag Graphic / Static Text.
Align Aligns the text inside of the object.
Caption Contains the text to be displayed.
Display Display choice: "black text on white
background" or "white text on black
background".
Font Font for the text to be displayed.
Via the tag Special / Time and Date.
Format Defines the time and date display
format, for example:
DD.MM.YYYY for the date
HH.MM.SS for the time.
CharWidth/CharHeight You have the choice between 2
character widths and heights for
dynamic output (outputs that change
during runtime) on the target system.
The font cannot be changed on the
target system.
Align Aligns the output inside of the object.
ShadowDepth Sets the frame width. This frame is
placed around the object.
("0" = no frame).
Operating Manual ProDesigner Version 04/04 33

34
This object is edited via the form’s Form Change property. The
property is used to determine how the switching between forms
should be realized. You may define up to 12 different keys with which
you can active a form change. Should you need more than 12 form
changes, because you have more forms then buttons, then you can
add further form change objects to the form using the toolbar.
Button The keycode combination used to
trigger a form change is entered here.
see chapter 10.1
Form Name Here the name of the form targeted for
the form change is entered. The name
property displays the name of the
form.
Please Note These properties defined inside of the form correspond to the
properties of the Form Change object.
If this name is changed in one form change object it must be changed
in all form objects.
Operating Manual ProDesigner Version 04/04

Variable Output
Please Note
Via the tag Output / Output Variable.
DataSource Contains the symbolic name of the
process variable as it was defined in
the process database. The
DataSource option can be either
inputted directly or be chosen via a
dialog box.
CharCount Number of characters used to display
a value.
DecPoint Number of places after the decimal
point.
AddText The static text displayed directly after a
value, for example units.
Hide Variable option which hides, if
activated, the output of a value. Should
the option be deactivated then the
output value is always displayed.
HideBit Defines the Bit that controls and
triggers the Hide property.
Display Controls the value’s display mode
(black or white font)
Autoscale Adjusts the size of the object to exactly
fit into the defined output box
Always declare the object’s datasource, because certain properties
such as CharCount are dependent on the datasource data type (e.g.
digital variables cannot be displayed using 5 digits).
Operating Manual ProDesigner Version 04/04 35

Variable Input
36
Via the tag Input / Input Variable.
KeyMode Defines the incrementation /
decrementation input method. Either via
number keys (0-Normal) or via special
keys (1-Cursor).
Min-/MaxValue Defines the input parameters. Here only
constants such as 0, 100 may be
entered.
TabIndex Defines the order in which the focus
moves from value to value whenever
the "Return" key is pressed. Usually
occurs in ascending order. "Gaps" in
the order are allowed. If the default
value "0" is not exceeded then the
order in which the objects were created
is used.
DataSource Declares the variable in which the
inputted value is written.
Operating Manual ProDesigner Version 04/04

2-Pin Switch
Via the tag Input / 2-Pin Switch.
KEY-|OFF Key used to decrease a variable and/or
reset a Bit respectively.
KEY+|ON Key used to increase a variable and/or
set a Bit respectively.
SwitchMode Determines the switch’s functionality.
0-Step: the function INC/DEC is active,
1-Bit: the function set/ reset a
DataSource Bit is active.
Step/BIT Declaration of the "jump value" for
INC/DEC, or of the Bit number for the
set/reset functions respectively.
This function is dependent on the
SwitchMode property.
DataSource Declaration of the variable effected by
the switch.
Operating Manual ProDesigner Version 04/04 37

Bar Graphics
Please Note
38
Via the tag Output / Bar Graphics.
Direction Determines the direction in which a bar
graphic moves.
Min/MaxValue The bar graphic’s display area in which
a value is displayed.
DataSource Name of the process variable to be
displayed.
In order to change and edit the properties of already existing objects
you can either choose the object from the object list box in the
inspector, or you can simply select the object directly from the form.
Please note that the compiler recognizes and differentiates between
small and capital lettering in the process variable declaration box.
Operating Manual ProDesigner Version 04/04

2.5 Testing your Application on the Development System
Once your form has been created you can start the compilation
process via the menu Execute / Compile Form.
A compilation procedure automatically occurs whenever you switch
from one form into another. Should the form already be compiled then
this procedure is ignored.
Please Note
Please Note
The compilation procedure is done as follows:
1. Creation of a static background picture.
(Creation of a *.SRC / *.SRX file in the runtime directory)
2. Creation of a list containing all dynamic objects.
(Creation of a picture database of *.PKF files in the runtime
directory).
During the compilation procedure all inputs necessary for an object
are checked. Should any parameters be missing or false they will be
displayed in the Compiler box.
More detailed information on these errors can be found under the
View / Error. Every form has its own error log. These logs can be
accessed whenever necessary.
The compilation procedure only checks whether all the object
parameters in a form are formally correct and present.
The procedure does not cross check the variable entered under
DataSource with the list of variables defined in the process database,
or whether any formulas and/or equations are correct.
If the form was compiled without any errors you can start and test your
application on the development system by clicking Start under the
menu Execute.
This simulation can be run without any connection to the PLC.
Your simulation must be error free in order to run.
Operating Manual ProDesigner Version 04/04 39

2.6 Transferring your Application to the Target System
In order to test your application on the target system it must be fully
compiled and error free. You can compile your application via the
menu Execute / Compile Project.
Please Note
3 Menus and Toolbars
40
In order to transfer the application to the target system you must
choose the transfer point under the tools menu: Tools / Transfer.
Before the transfer is started a so-called "Image File" is created. This
image file contains all the files needed for the runtime. The file is
"batch controlled" via the TRANSFER.TLP file and transferred into
control device’s utilities directory.
You may accommodate the TRANSFER.TLP file to suit your
requirements.
However, before you change this file please make a copy of your
original TRANSFER.TLP file.
see chapter 3.6.6
When creating an image file you should make sure that the COP
version and operating panel’s version are identical. This can be done
in the Configuration / Development menu.
Operating Manual ProDesigner Version 04/04

3.1 File
3.1.1 New Project
Menu Activation File / New Project
Or
Directory Window
or +
Project Name Unique project name consisting of up to max. 8
characters (DOS mode). Receives the extension
VWP and is registered and displayed in the list box
during this procedure.
Target System Choice of the hardware platform for which the
application is designed.
Project Directory It is advisable to always create a brand new directory
due to the fact that a ProDesigner project contains
several sub-directories (\DEVELOP, \PICTURE, and
\RUNTIME).
Registered
Projects
A summary of all registered projects, regardless of
their current path.
Paths Project’s path on the currently selected drive.
Drives From C:/ to Z:/
Operating Manual ProDesigner Version 04/04 41

3.1.2 Open Project
42
File Directory ... which looks like this ...
Menu Activation File / Open Project
Or
or +
Directory Window This window contains a list of all registered projects.
Info… Display of additional information belonging to the
selected project.
Add Registers projects located in the network
environment or projects that were copied and added
manually.
Remove The project’s registration is deleted, however the
actual project still exists on your hard drive.
Operating Manual ProDesigner Version 04/04

3.1.3 Save Project
3.1.4 Save Project As
3.1.5 New Form
3.1.6 Insert Form
Menu Activation File / Save Project
or
or +
Menu Activation File / Save Project As
Menu Activation File / New Form
or
Menu Activation File / Insert Form
or
The currently active project is saved. No further
confirmation is required.
The current project is saved under a new file name,
on a new driver/path. You may also select to save to
the floppy drive. After this function is called the
copied project is automatically loaded for processing.
Adds a new empty form to the currently active
project. The form active prior to this is saved.
This function is used to integrate existing forms from
other projects into the currently active project. The
form active prior to this is saved.
Operating Manual ProDesigner Version 04/04 43

3.1.7 Save Form
3.1.8 Delete Form
Please Note
3.1.9 Exit
44
Menu Activation File / Save Form
or
Save the currently active form.
Menu Activation File / Delete Form
Or
After confirmation all files belonging to this form are
deleted.
ALL files? No, not all files. A backup file (*.BWM)
remains in the \DEVELOP directory. This file can be
renamed to *.VWM and added to a project via the
Insert Form command.
The form ID number of a deleted form used by the runtime system to
uniquely identify a specific form is recycled and attributed to a different
form.
The project must therefore by recompiled before use.
Menu Activation File / Exit
Or
+
X - Top right-hand button - or
After confirmation all changes made to the project
are saved and then the ProDesigner is terminated.
Operating Manual ProDesigner Version 04/04

3.2 Edit
Important
3.2.1 Copy
3.2.2 Paste
All of the editing functions listed above are used on the visualization
objects in the project form. Functions such as copy and cut move the
selected objects into the Windows ® clipboard.
The Windows ® Clipboard only contains the last objects that were
moved on to it. A ProDesigner object moved on to the clipboard is lost
if you use the clipboard in any other Windows ® application.
Menu Activation Edit / Copy
Or
Operating Manual ProDesigner Version 04/04 45
+
Description One or several selected objects can be copied into
the form. In order to do this you must select and copy
an object using the copy command. You must then
use the Paste command to place the copied object or
objects into the designer.
The pasted objects appear at the top left-hand corner
of the form. From here they can be selected and
moved to any position in the form. If several objects
were copied and pasted, then these objects also
appear at the top left-hand corner of the new form,
however, these objects are grouped together in one
block so that they keep their relative position to each
other.
Menu Activation Edit / Paste
or
+
Description Pastes the objects stored on the clipboard into the
form. These objects appear at the top left-hand
corner of the form. Cut and copy use this function.

3.2.3 Cut
3.2.4 Delete
3.2.5 Select All
3.2.6 Edit Template
3.2.7 Lock Object
46
Menu Activation Edit / Cut
or
+
Description Elements are removed from the form and placed on
the clipboard.
Menu Activation Edit / Delete
or
+ or only
Description The selected object/objects are irrevocably removed
from the form and deleted.
Menu Activation Edit / Select All
Description All objects in the current form are select and can be
simultaneously moved or edited.
Menu Activation Available from version 2 onwards
Description Via the menu command Edit Template you can save
the complete form or just certain elements from the
form as templates for further applications. The
template is assigned a symbol and a short
description. Templates can be integrated into
applications. The template symbol, name and
description are displayed in the dialog box.
Menu Activation Edit / Lock Object
or
+
Description All objects are frozen in their current position. When
locked the objects cannot be moved using the
mouse.
Although locked, the object Properties can still be
viewed and edited.
Remove Lock Edit / Lock Object
Operating Manual ProDesigner Version 04/04

3.2.8 Save As Text
Please Note
Menu Activation Edit / Save As Text
Description All objects (with settings) are saved as ASCII texts.
The file name is the name of the form with the "ASC"
extension.
This text file can be edited using standard edit commands such as
find and replace.
In order for these changes to be incorporated into the form you must
copy the complete contents of the ASC file on to the clipboard and
paste these contents into the respective form using the Edit / Paste
command.
Operating Manual ProDesigner Version 04/04 47

3.3 View
3.3.1 Process Database
48
Using these options you can activate and open the individual program
component.
Menu Activation View / Process Database
Or
or
Description Activate the input window enabling process variable
definition in the process.
Detailed
description
Due to the fact that the process database is one of
the most important components of ProDesigner we
have dedicated a complete chapter to describe it.
see chapter 4
The parameters are listed in chapter 5 in alphabetical
order.
3.3.2 Project Administration
Menu Activation View / Project Administration
Or
Description All project forms are listed in a table.
The functions Add, Delete, New Form, PTX File and
Info are also available via the File menu.
Add Add a form to the current project. This form can be
selected using a file list box.
Delete Selected form is removed and deleted from the
Operating Manual ProDesigner Version 04/04

project.
New Form A new empty form is added to the project.
PTX File Displays the file that is used internally by the form
compiler to create a picture database. You can see
which objects and parameters are contained in the
form. You may not change any information shown.
INFO Display of a dialog in which additional project
information may be saved.
Project Name Display box
Project Type Display box
Project Path Display box
Created On Display box, corresponds to Windows file attributes.
Created By Can be edited
Changed on Display box, corresponds to Windows file attributes
Changed By Can be edited
Version Can be edited. Is displayed in the Project Open
Dialog
Customer Can be edited
Description Can be edited. May contain an arbitrary number of
lines.
Display boxes in the Project Administration Dialog.
Start YES This form is the first form displayed in
your application.
NO The form is placed into the "normal"
form queue.
Name Name of the form. The number in brackets behind
the name corresponds to the form’s number on the
target system.
Form Number The numbers shown here correspond to the numbers
used by the runtime system to identify a form.
Operating Manual ProDesigner Version 04/04 49

Please Note
3.3.3 Properties
3.3.4 Compiler Status
50
Status Compiled The form was successfully compiled.
Not
compiled
The form was not successfully
compiled.
Error An error occurred during compilation.
Objects Number of integrated visualization objects.
In order to make a form a starting form you must double-click the form
in the corresponding line.
Whenever forms are deleted, or whenever the property Form is
Starting Form is set, the picture numbers displayed in brackets behind
the form name are changed. Should you have used any conditional
operations referring to these numbers (@load B 7), then these must be
manually changed to the new setting.
Menu Activation View / Properties
or
Description Activates the Inspector. The Inspector displays the
chosen object’s properties.
detailed
description
Menu Activation View / Compiler Status
Due to the fact that the object properties belong to
the most important components of ProDesigner we
have dedicated a complete chapter to describe it.
see chapter 8
Chapter 6.6.4also contains a short description.
Description Activates the compiler window.
Operating Manual ProDesigner Version 04/04

3.3.5 Designer
3.3.6 Error Log
Menu Activation View / Designer
Description Activates the form - environment.
Menu Activation View / Error Log
or
Description Opens the error log containing the errors that
occurred during form compilation. By clicking an
entry you can automatically jump to the respective
object in the form.
see also Error Messages chapter 9
Operating Manual ProDesigner Version 04/04 51

3.4 Configuration (Settings)
3.4.1 Development
52
General parameter settings concerning the appearance and
functionality of the designer window such as "gridlines", "align to grid"
etc. It is also possible to activate an index text language.
Menu Activation Configuration / Development
Display Grid Grid visible on screen.
Grid not visible on screen.
Align to Grid The corner of an object is always placed on to one of
the grid co-ordinates.
Distance Grid X
Distance Grid Y
Distance between the horizontal grid points in Pixels.
Distance between the vertical grid points in Pixels.
Language Language change definition. The number must be
identical to the number in the offset file.
Port Determines the serial port via which data transfer
occurs.
COM1 and COM2 are supported.
Operating Manual ProDesigner Version 04/04

Please Note
Automatic
Compilation ...
Warnings ...
Background
pictures
compressed
Symbols
compressed
Create report
database
Use standard RTF
editor
Whenever you switch from one form to another the
last form is automatically compiled.
All compiler warnings (not the errors) are displayed.
Warnings are triggered whenever Min. or Max.
values are breached.
Activates or deactivates picture file compression.
This helps you to save system memory on the
operating system.
Activate or deactivates the compression of symbol
files.
Controls the creation of a report database during
compilation. This database is required for form and
project reports.
Activates the list box for editors in the form or project
report menus for the RTF file dealing with operating
system settings.
Use this RTF editor Uses the current program to view a form or project
report.
This program is only used if the option Use Standard
RTF Editor is deactivated.
COP Version COP version set-up (see system operating manual).
The Create Report Database option should only be activated if you
intend to create a form or project report. This command requires a lot
of resources slowing down the compilation procedure in the process.
Operating Manual ProDesigner Version 04/04 53

3.5 Start
3.5.1 Compile Form
54
Menu Activation Start / Compile Form
or
+
Compilation of the currently active form.
All changes made are saved before compilation
begins.
3.5.2 Compile Process Database
Menu Activation Start / Compile Process Database
Important
Please Note
3.5.3 Compile Project
or
+
Same functionality as Compile in the process
database.
All errors that occur during compilation are displayed in an error log.
This error log can be found under:
View / Error Log
All changes made in a form only become visible after the form and
process database have been successfully compiled.
The process database must be compiled In order for the ProDesigner
to recognize all objects. If the process database is not compiled then
any changes made will be ignored. Error messages are displayed in a
display below the process database window:
Double clicking the error message displays the line containing the
error.
Error Messages chapter 9
Menu Activation Start / Compile Project
or
+
Compilation of the complete project including the
process database.
Operating Manual ProDesigner Version 04/04

3.5.4 Start
Please Note
Menu Activation Start / Start
or
Operating Manual ProDesigner Version 04/04 55
or
This function starts the simulation on the
development system.
This function can only be started if the project was successfully
compiled.

3.6 Tools
3.6.1 Index Texts
Please Note
56
Texts are allocated via the input window to the index number shown in
the left column. Switching to a different language is done by clicking
one of the tags displayed at the bottom of the table.
The index texts are stored in the /RUNTIME directory as INDEX.TX1
for language 1 and INDEX.TX2 for language 2. One of these files is,
depending on the settings made in the Configuration / Development
menu, is copied into the INDEX.TXT file. This file is then used by the
runtime for text output.
Up to 8000 index text numbers (0 – 7999) are available per language.
However, only a maximum of 5000 texts with a memory capacity of
64Kbyte may be used because the text memory capacity on the
operating panel is restricted.
Before you start with the text input you should determine how the text
numbers are assigned. Systematic number assignment (sorted
according to pictures, error messages or alarms etc.) makes
everything a lot easier!
Operating Manual ProDesigner Version 04/04

3.6.2 Symbols
Please Note
Please Note
This tool makes it easy to create symbols that can be used in the
animation of your project.
• Existing BMP graphics are converted into a ProDesigner.
(*.SYK)
• Your pictures should be created in black-and-white.
• You can vary the picture points via the left mouse button.
The easiest method of creating symbol is to import BMP graphics.
This graphics are always imported in their original size. Symbols may
also be loaded from other projects and saved in the currently active
one.
Symbols must always be saved under a name consisting of numbers
only. These symbol files must be saved in the project’s \RUNTIME
directory.
Operating Manual ProDesigner Version 04/04 57

File
Edit
View
3.6.3 Recipes
Please Note
58
New Opens a new design area.
Load Loads a symbol (*.SYK).
Save Saves the symbol.
Save As Saves and gives the symbol a new name.
The symbol’s name must be comprised of numbers
without an extension.
Exit Back to the Designer.
Insert BMP Imports a bmp graphic.
Invert Inverts the color. Black to white and vice versa.
Zoom 1 - 4 Sets the magnification factor.
Recipes are a collection of various variables that can be processed
via the recipe object of the process database.
Using recipes you can create and administrate product data sets or
machine data sets. A maximum of 30 recipes can be created per
project. These recipes are stored on the user’s system in a recipe
memory. The recipe memory size restricts the amount of data that can
be saved.
Operating Manual ProDesigner Version 04/04

Existing Control
files
Contains a list of all creates recipe in this project.
The control files are identified by the numbers 0-29.
These numbers are automatically generated and
allocated.
New Creates a new recipe control file and opens the
editing dialog for the file.
Edit Here variables can be added to or deleted from the
control file. ( see following picture.)
Remove Removes the selected control file.
Close Closes the dialog.
Control File Name under which the recipe control file is saved.
Comment Comment for the control file. This comment is
displayed in the control file list box.
Operating Manual ProDesigner Version 04/04 59

Please Note
60
Variables and
structures of the
process database
Variables and
structures of the
control file
List of all variables and structures defined in the
process database not yet assigned to the recipe
control file.
List of all variables and structures assigned to the
control file.
< The selected element is removed from the control
file.
The selected element is added to the control file.
>> All elements are added to the control file.
Error List Should a variable or structure contained in a control
file be deleted ( or renamed) from the process
database, you receive an error message when
editing the control file. The error list displays the
variable or structure causing the error.
The information contained in the editing dialog requires that the
process database be compiled without errors.
The easiest method of copying recipe control files is to change the
name in the control file box in the editing dialog.
Operating Manual ProDesigner Version 04/04

3.6.4 Form-/Project Report
The form or project report serves as a documentation of individual
forms, or a complete project respectively. In order to be able to use
this function the project or form must compiled using the option
Create Report Database in the Configuration / Development menu.
The creation of the report database, as well as the required graphic
files occurs during compilation. These files are created even if the
project is not compiled error free. Display and analysis of these report
files occurs via the menu Tools / Form Report or Tools / Project
Report. A dialog is opened via this menu containing the tags Settings,
Data and Report.
Via the Settings tag, filters can be defined for the created data. The
result of these settings can be displayed as a table under the Data tag
and under the tag Report the results can be saved as files for further
processing.
Filter Forms Contains a list of forms that should be included in the
report.
All Forms Automatically selects all forms contained in the
report.
Choose If the All Forms options is deactivated you can
choose individual forms that should be included in
the report.
Filter Object Types Used to select certain object types e.g. outputs or
switches that should be included in the report.
All Object Types All object types existing in the forms are selected and
included in the report.
Choose If the All Object Types options is deactivated you can
choose the individual object types that should be
included in the report.
Filter Properties Used to define those object properties that should be
Operating Manual ProDesigner Version 04/04 61

62
DataSource
Properties
included in the report.
Limits the properties that should be included in the
report to those properties that contain a process
variable.
Key Properties Limits the properties that should be included in the
report to those properties that contain a key.
Form Properties Limits the properties that should be included in the
report to those properties that contain a form
number.
All Properties All object types in the selected forms are included in
the report.
Choose If none of the above options are activated you may
use this command to choose individual properties
that should be included in the report.
Blend out
Values
Blend out empty
character strings
Object properties that have the value 0 are not
displayed.
Object properties that do no have an entry are not
displayed.
The tag Data is used to display objects in table form. The output of these
objects is generated according to the options defined under the Settings tag.
Operating Manual ProDesigner Version 04/04

The tag Reports controls the output of the form or project report as a file.
There are two different report formats available:
The Report format allows a detailed report in RTF format, which can then be
processed and edited using a text processing program.
The Table format creates a table containing all object properties, which can be
processed and edited using Excel.
Report Used to define all project components that should be
included in the report.
Project Header A list of forms including all project information is
displayed according to the project administration.
Configuration
Development
Configuration
Runtime
The settings made in the Configuration menu are
displayed.
The runtime settings defined in the 0.INI file are
displayed.
Process Database Supplements the report with the complete process
database.
Index Text All index texts are included in the report.
Forms (Display
Designer)
Forms (Display
Runtime)
The designer forms are displayed graphically. All
objects in a form are visible.
The runtime forms are displayed graphically. Only
those objects visible during runtime are displayed
(e.g. formulas are not displayed).
Object Properties The visualization object properties are included in the
report.
Symbols All symbols defined in the project are included in the
report.
Recipes All recipe control files defined in the project are
included in the report.
Operating Manual ProDesigner Version 04/04 63

Please Note
64
Save Report As
(*.RTF)
Declaration of the name under which the report
should be saved. The file is always saved in the
project’s \DOCS directory and has the file extension
RTF.
Create The report is created and receives the name
declared above.
View Once the report is created it can be viewed using a
Windows program that supports the RFT format,
usually either Wordpad or Word. You may manually
choose a program with which to view the report in
the Configuration / Development menu.
Project Table Controls the report’s table format. Here only the
object properties are displayed.
Separator Comma The individual table columns are separated by a
comma.
Separator TAB The individual table columns are separated by a
TAB.
Save Table As
(*.CSV)
Declaration of the name under which the table
should be saved. The table is always saved in the
project’s \DOCS directory and has the file extension
CSV.
In order to be able to use the report functions you must activate the
Create Report Database option in the Configuration / Development
menu.
Operating Manual ProDesigner Version 04/04

3.6.5 Create Image File
The Create Image File functions is used to set-up a binary file that can
be loaded via the Transfer procedure into the operating panel. The
requirement for creating such a file is that the project be compiles
without any errors.
The image file contains all files required by the runtime system on the
COP device. These files are copied into the project’s runtime directory
using the project name with the file extension DAT.
Runtime Directory *.PKF Compiled forms.
Please Note
.SCR/.SCX Form’s background pictures (compressed or
uncompressed).
INDEX.TXT Index texts according to the language selected in the
configuration menu.
.SYK/.SYX Symbol files (.SYK=compressed,
.SYX=uncompressed).
*.REC Recipe control files.
0.DKF Compiled process database.
0.INI Runtime’s configuration file.
The parameters in the Configuration / Development menu influence
the image file creation procedure. If you change any of these
parameters you must recompile the project. Changes only become
active after the project is compiled.
Operating Manual ProDesigner Version 04/04 65

3.6.6 Transfer
66
Executes a batch file. This file controls the transfer of your project
from the development system to the target system.
The content of the batch file depends on the target system’s hardware
and may be edited by the user.
The program used for the transfer (DOWN.EXE) may be found in the
\UTILITY directory. The file TRANSFER.TPL containing the parameter
settings is also located here.
Construction of the Batch file TRANSFER.TPL located in the \UTILITY
directory:
echo ====== Information / Parameter ======
echo %1 = Drive Letter
echo %2 = Path of TRANSFER.BAT / DOWN.EXE
echo %3 = Path of Runtime-Subdirectory
echo %4 = Name of ImageFile
echo %5 = COM-Port for Transfer
%1
cd %3
dir %4
Echo ====== Start download with any key ======
Pause > NUL
%2\down %5 –x FF5726 –f %4
if errorlevel 9 goto again
goto end
:again
echo Download- Error, once again
%2\down %5 –x FF5726 –f %4
:end
Operating Manual ProDesigner Version 04/04

3.7 ?
3.7.1 Help
3.7.2 Info
4 Process Database
Calls up online help.
Detailed display of all installed program modules.
Menu Activation
Or
Or
Operating Manual ProDesigner Version 04/04 67
Red.
The current version is older than the required
version.
Green.
The current version meets the necessary
requirements.
Yellow.
The current version is newer than the required
version.

68
Operating Manual ProDesigner Version 04/04

4.1 General
4.1.1 Insert
The process database is the visualization’s central file. The database
contains the definitions of all process constants that are swapped with
the PLC or operating panel respectively. Furthermore, formulas and
conditions that function picture independent may be defined here. The
process database is saved as an ASCII file and may be processed
using other text editors. This files is converted into a binary format for
the runtime system.
The process database objects are placed
into the following groups....
see description in chapter 4.2
The process database can be edited via the dialog window
( see chapter 4.1.2), as well as directly in the editor. The method via
the dialog window is advisable when beginning a new application, or
with smaller applications. Using the text editor is easier when working
with larger applications. It is possible to switch between both editing
methods. You should always use the dialog window to define the first
few components. These entries can then be used as templates for the
following components, be it using the dialog window, or using the text
editor. Editing functions such as Find and Replace are available via
the context menu (right mouse button).
Insert Inserts a new component at the current cursor
position into the process database (editor window).
Editing an existing
component
If you wish to edit an existing component, just double
click the relevant line and the dialog window
Operating Manual ProDesigner Version 04/04 69

4.1.2 Text Editor and Dialog Window
70
displaying the component will be opened.
Compile Compiles the inserted components to the internal
ProDesigner data format.
Save Saves the inserted or edited components to the hard
drive.
OK Exits the process database level and returns to the
designer. If changes were made to the process
database these are saved and compiled.
Cancel Ignores the changes that were made and returns to
the Designer.
Creating components can also be done using the text editor. This
method is advisable when working with a large number of variables.
The standard text editor functions such as “cut and paste” allow you to
copy large text blocks into the process database. In order to
successfully work using a text editor you must adhere to the formal
component construction syntax:
e.g. for a Bit-Alarm object:
$A0 PLCAL4 "Bit-Alarm " PLCALAR1 4 4 0 #
$A0 Component ID $A0 = Bit alarm
see chapter 4.1.4
PLCAL4 Symbolic component name. Must be unique in
process database. see chapter 5.9
"Bit-Alarm " Commentary to the component, up to a max. of 28
characters.
PLCALAR1 4 4 Further parameters separated by spaces.
0
# End of line.
Operating Manual ProDesigner Version 04/04

4.1.3 Parameters for (nearly) every Definition
Name Object identification. 8 Letters without Umlauts,
numbers, _ (underline)
Text index
Data offset
(address)
Bit number
.. increment on
insertion
Automatic incrementation for
example of the Bit number
whenever insertion occurs.
Several objects have their
addresses or Bit numbers
incremented (e.g. digital
variables) whenever the
"insert" button is pressed.
Status Entry is / is not included
during compilation.
$ Entry is compiled
; Entry isn’t compiled.
Commentary Arbitrary text used to help
identify and describe an
object.
Operating Manual ProDesigner Version 04/04 71
28
Choice
Choice
Letters, Numbers,
Symbols

4.1.4 Table of Database Object IDs
72
$ = active
; = inactive
Control
Char
Scan
Type
Object group Object type
$ A0 Alarm Bit alarm
$ E0 Variable Digital variable
$ E1 Variable Word variable
$ E3 Variable Long word variable
$ E2 Variable Floating point variable
$ E4 Variable BCD variable
$ E6 Variable Text variable
$ F0 Formula/Condition Formula dialog
$ I0 Formula/Condition Condition if - then - else
$ I2 Formula/Condition Jump object
$ O5 Diverse Recipe object
$ X0 Diverse Exit object
$ S0 Diverse Structure object
$ S1 Diverse System Object
Operating Manual ProDesigner Version 04/04

4.2 ... during Runtime
This section is intended to explain the fundamental basics behind the
runtime system.
4.2.1 Object Processing
There is a difference between pressing a button during the processing
of the follow databases:
• process database
• picture database
Input objects are only periodically processed whenever a button is
pressed!
Tasta-“Tour”
Key
pressed
during
processing
yes
Process Input
Objects
Operating Manual ProDesigner Version 04/04 73
no
Start
System Initialization
CTRL + Q
no
1 x Database
Processing
yes
Drivers + ext.Variables
Variables
all other
Objects
Edit Picture
Objects
Input Objects
not
processed
System Shut Down
no
Key
pressed
during
processing
yes
Process
Input Objects
As can be seen in the flow chart, processing occurs in the following
order: Process database Picture database Others.
In the process database: Variables changes are updated using the
respective driver program. This update is done in a database mirror
and made public for the picture output by setting the change status.
The picture database only reacts according to the status change
principle. If the change status is set then the database reacts by
outputting a new picture.

Order ...
4.3 Alarm
4.3.1 Overview
74
Principally, it can be stated that drivers are the first objects to be
processed in the process database followed by all other objects in the
order that they were created.
This assures that all following components such as alarms, formulas
etc. use the updated data.
At picture level the processing occurs in the order in which the
components were defined. (The exception to the rule are input
components). The principle of status change is also valid here.
... of picture objects.
The development environment automatically generates this order.
... of entries.
Input fields do not adhere to the status change principle. An input
object is only changed if it possesses the focus (cursor). The order in
which input occurs is determined by the property TAB-ORDER, which
is activated whenever the Enter key is pressed. Use the cursor (arrow)
keys to move the cursor (input focus) in the X- and Y-directions.
Alarm objects are used in the process database to observe process
states. In ProDesigner only a Bit in a variable can be observed.
Priorities for alarms can be defined, and messages in the form of
index texts can be assigned to an alarm. Alarms can be displayed at
picture level using the Alarm Line and Alarm List objects.
Bit Triggering of an alarm due to a changed Bit. The
data source for this could include digital variables, as
well as word and long word variables.
Operating Manual ProDesigner Version 04/04

4.3.2 Bit
Parameters
Menu Activation Database / Alarm / Bit Alarm
The alarm object triggers an alarm exactly then whenever a defined
Bit is set, i.e. whenever its state changes from "0" to "1".
Name Standard see chapter 0
max. Type
Variable Variable to be monitored. 8 Letters without Umlauts,
numbers, _ (underline)
Bit number "Number" of the Bit in the
variable.
Text index Text number of the alarm text
in the index text file.
Priority "Importance" of the alarm
0 ... 99.
0 = lowest,
99 = highest priority.
Text index
Bit number
Standard see chapter 0
increment on
insertion
Status Standard see chapter 0
Commentary Standard see chapter 0
Operating Manual ProDesigner Version 04/04 75
1
2
2
Number
Digits
Digits

4.4 Variable
4.4.1 Overview
76
Digital Value range "0" to "1"
Word 16 Bit, value range -32768 ... +32767
Long Word 32 Bit, value range -2147483648 ... +2147483647
Floating Point 32 Bit, value range 10*exp(-36) ... 10*exp(+38)
BCD Word variable in BCD format
Value range 0 ... 9999
Text Variable used to record arbitrary character strings
Every value, which is read by the driver, receives a symbolic name
and data type (for example "pressure", "temperature" or "w1") during
variable definition. Valid data types are digital, word or floating point.
This regulation guarantees that the shortcuts, representations,
calculations etc. can operate using these names.
Operating Manual ProDesigner Version 04/04

4.4.2 Digital
Parameters
Please Note
Menu Database / Variable / Digital
Activation
A digital variable can only have one of the two states at any one time:
"0" and "1". Digital variables are used for triggering functions, as well
as for switch functions.
Name Standard see chapter 0
max. Type
Driver Choice of driver interface Menu choice
Address Data’s starting address Dependent on
the control
Bit number "Number" of the Bit 2 Numbers
Attribute Choice whether read or write
enabled, or both.
Data offset Standard see chapter 0
Bit number
increment on insertion
Standard see chapter 0
Status Standard see chapter 0
Commentary Standard see chapter 0
Menu choice
Digital variable are contacted wordwise where Shared-RAM, RK512
and Structure drivers are involved, i.e. each address has 16 digital
variables at its disposal. The addressing inside of each word is done
via the bit number. The address and bit number has no meaning
where drivers of the Internal are concerned.
Operating Manual ProDesigner Version 04/04 77

4.4.3 Word
Parameters
78
Menu Database / Variable / Word Variable
Activation
Word variables belong to the fixed variables in ProDesigner. The
processing of this variable type is the fastest because no complicated
floating point calculations must be made.
Name Standard see chapter 0
max. Type
Driver Choice of driver interface Menu choice
Address Data’s starting address Dependent on
the control
Number Number of variables 4 Digits
Conversion
factor
Variable’s multiplication factor 8 Digits
Mirror Declaration of a byte or word as a
variable
Menu choice
Attribute Method of data access Menu choice
Status Standard see chapter 0
Commentary Standard see chapter 0
Operating Manual ProDesigner Version 04/04

4.4.4 Long Word
Parameters
Menu Database / Variable / Long Word Variable
Activation
Long word variables together with word variables belong to the
floating-point variables in ProDesigner.
Name Standard see chapter 0
max. Type
Driver Choice of driver interface Menu choice
Address Data’s starting address Dependent on the
control
Number Number of variables 4 Digits
Conversion
factor
Variable’s multiplication
factor
Operating Manual ProDesigner Version 04/04 79
8
Digits
Attribute Method of data access Menu choice
Status Standard see chapter 0
Commentary Standard see chapter 0

4.4.5 Floating Point
Parameters
Please Note
80
Menu
Database / Variable / Floating Point Variable
Activation
Floating-point variables are processed in the ProDesigner in IEEE
format. The processing of this data type is requires a lot of processor
resources and therefore take some time. Not all controls support the
floating-point format.
Name Standard see chapter 0
max. Type
Driver Choice of driver interface Menu choice
Address Data’s starting address Dependent on the
control
Number Number of variables 4 Digits
Conversion
factor
Variable’s multiplication factor 8 Digits
Attribute Method of data access Menu choice
Status Standard see chapter 0
Commentary Standard see chapter 0
Please note that errors can occur during floating point variable
processing if values are read that are not defined in the floating point
format. This would be the case whenever an object is addressed to a
memory block containing no floating point number. Invalid bit
combinations are, e.g. 0x7FFFFFF..0xFFFFFFF (+/- not a number), or
0x7F80000..0xFF80000 (+/- infinity).
Operating Manual ProDesigner Version 04/04

4.4.6 BCD Variable
Parameters
Menu
Activation
Database / Variable / BCD Variable
BCD variables are used to save "binary coded decimal numbers". An
automatic conversion factor is realized using these variables enabling
ProDesigner to process time constants.
max. Type
Name Object name 8 Letters without
Umlauts,
numbers, _
(underline)
Driver Choice of driver interface Menu choice
Address Data’s starting address Dependent on the
control
Number Number of variables 4 Digits
Conversion factor Data type determination
Operating Manual ProDesigner Version 04/04 81
0
1
2
4 digit BCD
Time and counter S5 (1 sec.)
Time and counter S5 (1/10 sec.)
Attribute Method of data access Menu choice
Status Entry is/is not included
during compilation
Commentary Arbitrary text used to help
identify and describe an
object
28
Choice
Letters, numbers,
symbols

4.4.7 Text
Parameters
Please Note
82
Menu
Database / Variable / Text
Activation
Text variable that can contain alpha-numerical characters.
Name Standard see chapter 0
Driver Driver coupled to the
variable
LED and Shared-RAM
are not available
max. Type
Dependent on the control
(Menu choice)
Address Data’s starting address Dependent on the control
Length Length in characters
(1 Byte = 1 character)
Numbers
Attribute Method of data access Menu choice
Status Standard see chapter 0
Commentary Standard see chapter 0
Text variables may only be defined via the Internal and/or Structure
drivers. If text variables are embedded in a structure (driver Shared-
RAM), then the complete structure is written as soon as the "Return"
key is pressed during variable input, whether the trigger conditions
have been met or not. Please note that the value 00 hex inside a
character string is recognized as a termination ID. Please also note
that input and output objects do not always function correctly if a
character string contains the character string 0x00hex.
Operating Manual ProDesigner Version 04/04

4.5 Formula and Condition
The mathematical and logical functions of the ProDesigner constitute
an efficient control language used to process and logically link
database objects.
4.5.1 Overview
Using the control language, orders of events, calculations and control
functions can be realized.
The processing of formulas and conditions occurs during every
system cycle.
All four fundamental arithmetic operations, as well as certain
mathematical functions are available for calculations and conversions.
Pre-defined variables and functions, as well as common logical
operators are available for conditional objects.
Formula An object able to contain mathematical formulas and
functions.
Condition An object enabling conditional program processing
using "if-then-else".
Jump Object An object allowing jumps over a certain number of
database objects.
Operating Manual ProDesigner Version 04/04 83

4.5.2 Syntax Diagrams
Condition
Logical Concatenation
Statement
84
For more on formulas and conditions:
see chapter 4.5.3, 4.5.4, 5.6, 6.6.1, 6.6.2, 7.2.11
Available system variables see chapter 10.4
„&“ logical AND
„I“ logical OR
Condition Condition
see chapter 10.4.1
$
(
[
&
I
Condition
log. conection
System-Variable
Expression =
!=
<
>
=
Expression
see chapter 10.4.2
Variable = Expression
Statement ; Statement
@
)
]
Systemcommand
Operating Manual ProDesigner Version 04/04

Arithmetic Expression
Function
Please Note
Expression
-
Function
Operating Manual ProDesigner Version 04/04 85
+
-
* \
%
( Expression )
Constant
Variable
sin
cos
sqrt
Expression
( Expression )
Here is an example of logical concatenation in conditions:
[digit = 1] & [digit = 1] | [word1 = (3+2)]
The condition is fulfilled if
"digit1 = 1" AND "digit2 = 1"
OR
"word1 = 5".

4.5.3 Formula
Parameter
Please Note
86
Menu
Database / Formula / Formula
Activation
Using this object you can link process database variables together.
This is done using mathematical formulas and functions allowing you
to undertake special mathematical routines such as applying special
mathematical conversion factors to functions.
Name Standard see chapter 0
max. Type
Formula Statement 38 Letters without Umlauts,
numbers, _ (underline),
mathematical operators
see chapter 4.5.2
Status Standard see chapter 0
Commentary Standard see chapter 0
Formula object processing is time controlled in the runtime version.
The order in which the formulas and conditions are processed is
determined by the order in which they were inputted.
Statements must be separated by a ";".
Operating Manual ProDesigner Version 04/04

4.5.4 Condition
Parameters
Menu Database / Formula / Condition
Activation
Using this object you can program conditional processing routines.
The conditions are programmed using "if-then-else". This allows you
to construction processing routines and control structures.
Name Standard see chapter 0
max. Type
If "if" ... condition 38 Letters without Umlauts,
numbers, _ (underline),
mathematical operators
Then "then" ... statement 38 Letters without Umlauts,
numbers, _ (underline),
mathematical operators
see chapter 4.5.2
Else "else" ... statement 38 Letters without Umlauts,
numbers,_(underline),
mathematical operators
Status Standard see chapter 0
Commentary Standard see chapter 0
Operating Manual ProDesigner Version 04/04 87

4.5.5 Jump Object
Parameters
Please Note
88
Menu
Database / Formula / Jump Object
Activation
Using this object you can jump a certain number of objects. These
objects are all defined in a certain order. A jump can be defined using
a digital variable, which must be defined in the Trigger parameter.
Name Standard see chapter 0
Trigger Digital or word variable
triggers the jump. The
trigger is not reset by the
jump.
Bit number 0 for a digital variable
0-15 for a word variable
Jump target Number of objects to be
jumped
Status Standard see chapter 0
Commentary Standard see chapter 0
max. Type
8
1
3
Letters without Umlauts,
numbers, _ (underline)
Number
Digits
If a jump should be triggered by the "0" then a "!" must be inserted in
front of the trigger variable, e.g. !dig4.
Operating Manual ProDesigner Version 04/04

4.6 Diverse Objects This object group contains all objects that have a complex
functionality and therefore do not fit into any of the other groups.
4.6.1 Overview
4.6.2 Recipe Object
Please Note
Recipe Object Collection of several process variables into a data
record, which can be saved to and loaded from a
file of choice.
Structure Object Block structured group of variables.
Exit Object Application termination controlled via a trigger
variable and linked to the system level of the
operating panel.
System Object Enables the access to system structures such as
recipe status, handwheel etc.
Menu
Activation
View / Process Database / Insert / Diverse /Recipe Object
Various process variables, declared in a control file, can be processed
together using the recipe object. Processed means: Saving, loading,
deleting, writing and reading. The steps saving, loading and deleting
refer to the processing of recipe memory in the RAM area. Reading
and writing occurs from the RAM area into the control.
Zero potential recipe saving is operating panel dependent.
Operating Manual ProDesigner Version 04/04 89

Parameters
90
Name Standard see chapter 0
Recipe name Word / BCD or long word variable. The name is
composed out of the variables’ values
Control file Contains the name of the control file that contains the
recipe variables. This file (*.REC) is created or edited
under Tools / Recipe. Valid control file names are 0.REC
through to 29.REC
Save The contents of the variable is loaded from the system
memory into the recipe memory.
Load The contents of the variable is loaded from the recipe
memory into system memory.
Write The contents of the variables are written from system
memory into the control
Read The contents of the variables are written from the control
into system memory
Trigger Declaration of the variable(s) that triggers this function
Bit Number Variable’s bit number that triggers the function
Delete The recipe is deleted from the recipe memory
Status Standard see chapter 0
Commentary Standard see chapter 0
Operating Manual ProDesigner Version 04/04

Please Note
Load
Recipe Memory
Database
Write Read
Control
Delete
Save
A combination of the control bits READ, WRITE, SAVE, LOAD and
DELETE is possible. The bits are checked in the following order:
1. DELETE
2. LOAD
3. WRITE
4. READ
5. SAVE
The respective control bits are reset after they have fulfilled their
function. Recipe administration status messages can be analyzed via
the Recipe structure. The core of the recipe is the control file (*.REC).
This file is created via the Tools / Recipe menu.
Please note that errors or status reports on recipe processing can be
analyzed via the RECIPE structure of the Shared-RAM.
A description of this structure is contained in the operating manual of
your operating panel.
Operating Manual ProDesigner Version 04/04 91

4.6.3 Structure Object
92
Menu
Activation
View / Process Database / Insert / Diverse / Structure
Object
This object is used to define data blocks, as well as those user
defined data types used in most standard programming languages.
Structure expansions (e.g. mirrors of existing C-structures) and
changes can be easily made without negative effects to the structure
of the process database. This function can be compared to the
"Record", "Struct".
Operating Manual ProDesigner Version 04/04

Parameters
Please Note
Name Standard see chapter 0
Driver Driver referring to
the variable
Address Data’s starting
address
Bytes Structure size in
bytes
Read Recipe values from
the READ control:
Empty / @ / “ “ Cyclic READ
& Not READ
Variable Block READ. The
variable is reset if
the structure was
READ
Bit Number Trigger Bit in the
trigger variable
Write Current recipe value
sent to the WRITE
control
Empty / @ / “ “ Describes the
structure’s variables.
These are sent one
by one to the control.
& Not WRITE
Variable The variable is reset
if the structure was
written
Bit number Trigger Bit of the
trigger variable
Status Standard see chapter 0
Comment Standard see chapter 0
Max. Type
* Control
Dependent
* Control
Dependent
5 Numbers
8 Letters without
Umlauts and ß,
numbers, _ char
2 Numbers
8 Letters without
Umlauts and ß,
numbers, _ char
2 Numbers
The definition of structures in structures is not allowed.
Operating Manual ProDesigner Version 04/04 93

4.6.4 Exit Object
94
Menu
Activation
View / Process Database / Insert / Diverse / Exit Object
The application is automatically terminated as soon as the declared
trigger variable Bit is set.
You may exit the visualization level to the system level of your
operating system using this function.
This function can executed with or without an acknowledgement
message.
Parameters Max. Type
Name Standard see chapter 0
Trigger Name of the variable
that triggers the action.
Bit Number Variable Bit that
triggers the action.
8 Variable Name
32 Numbers
Mode No Messages: The application is terminated
without any messages
With Messages: The User is informed that the
application was terminated before returning to the
operating system’s system level.
Status Standard see chapter 0
Comment Standard see chapter 0
Operating Manual ProDesigner Version 04/04

4.6.5 System Object
Menu
Activation
View / Process Database / Insert / Diverse / System Object
This object is used to define data blocks via which access to system
internal structures/variables (such as error structures of the RK512
protocol etc.) is enabled.
Parameters Max. Type
Name Standard see chapter 0
Driver Default value "System".
Address Type of datablock
to be edited. The
values are defined
as follows.
ERR_SRAM Error structure of
the Shared-RAM
protocol.
ERR_RK512 Error structure of
the RK512
protocol.
* Control
dependent
See operating
panel manual.
See operating
panel manual.
RECIPE Recipe structure. See operating
panel manual.
HANDWHEEL Handwheel
variable.
Optional. See
operating panel
manual.
JOYSTICK Joystick variable. Optional. See
operating panel
manual.
PORT_IN Code switch inlet. Optional. See
operating panel
manual.
Operating Manual ProDesigner Version 04/04 95

Please Note
96
PORT_OUT Code switch outlet. Optional. See
operating panel
manual.
DATE_TIME Date/Time
structure used to
set the clock.
INI_REC Structure used to
completely delete
the recipe memory
in the operating
panel.
Bytes Size of data block
in Bytes
automatically
determined by the
set address.
Read Trigger for reading
data.
Empty /@/ “ “ cyclic READ
& NOT Read
Variable The variable is
reset whenever the
structure is read.
Bit Number Trigger Bit of the
trigger variable.
Write Trigger for writing
the structure.
Empty /@/ “ “ Describes the
structure’s
variables. These
are sent one by
one to the control.
& No write
Variable The variable is
reset if the
structure was
written
Bit Number Trigger variable’s
triggering Bit
Status Standard see chapter 0
Comment Standard see chapter 0
See operating
panel manual.
See operating
panel manual.
5 Not editable
8 Letters without
Umlauts and ß,
numbers, _ char
2 Numbers
8 Letters without
Umlauts and ß,
numbers, _ char
2 Numbers
The input boxes are activated / deactivated according to the set
address since not all system structures can be read or written.
Furthermore, certain system structures such as Date_Time require
that a trigger variable be declared.
Operating Manual ProDesigner Version 04/04

5 Process Database Parameters
Operating Manual ProDesigner Version 04/04 97

5.1 Image
Please Note
98
Refers to Variable: Word Variable
Description Using this parameter you can define byte variables in
ProDesigner. The default value is word. This means that
the variable is valid for both word bytes. The two settings
"low" and "high" allow you to define the lower or upper
data word byte as a variable. It is not possible to define
words for uneven data offsets.
You may choose from the following three setups:
Value Term Description
0 Whole word The complete data word
is defined as a variable
1 Lower byte Only the data word’s
lower byte is defined as a
variable
–128 ... 127
2 Upper byte Only the data word’s
upper byte is defined as
a variable
–128 ... 127
If you directly edit the database file you must insert the corresponding
number listed in the column Value.
1. Declaration of the variable word_01 with the setting whole word
wort_01
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
MSB
LSB
2. Declaration of the variable word_01 with the setting lower byte
wort_01
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
MSB
LSB
3. Declaration of the variable word_01 with the setting upper byte
wort_01
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
MSB
LSB
Operating Manual ProDesigner Version 04/04

5.2 Address
Please Note
Refers to Diverse: Structure
Variables
Description This parameter requires the address from where the
data from the control should be mirrored in the
variable or the structure respectively.
The format in which the address must be declared is
dependent on the value set in the Driver field.
Internal
The declared address has no meaning
LED
Presently always "0"
Shared-RAM
The address contains the offset inside of a PLC’s
linear memory area
RK512
Declaration in DU:DW (Data Unit:Data Word)
Structure
Structure name:Offset
System
The address is selected from a list
See COP operating manual.
When creating variables in structures, the declaration is made via the
structure’s name as well as the offset (in bytes) inside of the structure.
An offset must always be an even number due to the word orientation
of the operating panel. The declaration of an odd address would lead
to an error in the operating panel.
Operating Manual ProDesigner Version 04/04 99

5.3 Number
Please Note
100
Refers to Variable: Word Variable, Long Word Variable,
Floating Point Variable, BCD Variable
Diverse: Structure
(There are always an even number of bytes used)
Description Using this parameter you can determine how many
data elements should be loaded starting from a
certain address. This declaration creates an image
of the control’s memory in the COP/COP-Handy.
Please make certain that you have enough data
words to define all the required variables. Long word
and floating point variables each require 2 data
words.
This entry, where variables are concerned, refers to the number of
relevant field controls and not the number of data words! If for
example a single long word variable needs to be declared, then you
must insert a "1" into the number field, even though the variable
actually requires and occupies 2 data words. In data structures the
number is declared in bytes. It should be noted that only even
numbers are used.
Memorymirror in the PC
0
1
2
3
4
5
6
7
DB 20
0
1
2
3
4
5
6
7
8
Single Variable “Word”
Dataoffset = 2
Number = 1
Memorymirror in the PC Memorymirror in the PC
0
1
2
3
4
5
6
7
Single Variable “Word”
Dataoffset = 4
Number = 1
ProDesigner
Address: 020:002
Number = 6
0
1
2
Field element 1
3
4
5 Field element 2
6
7 Fieldl Variable “Longwort”
Dataoffset = 2
Number = 2
PLC / Control Memorymirror
in the visualization
Dataoffset
0
1
2
3
4
5
Operating Manual ProDesigner Version 04/04

5.4 Bit Number
5.5 Formula
Important
Refers to Digital Variables
Description This parameter determines the position of a digital
variable inside of a data word. A data word consists
of 16 Bits (Bit number 0 ... 15). This means that
every data word can have a max. total of 16 digital
variables assigned to it.
Bit arrangement inside a data word:
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
MSB
LSB
Refers to Formula/Condition: Formula (see also:
chapter 4.5.3, 4.5.4, 5.6, 6.6.1, 6.6.2, 7.2.11
Description Here you may insert simple equations such as:
Distance = velocity / time, or y = 2*sin(x).
Reserved signs
+ functions:
+ Addition
- Subtraction
* Multiplication
/ Division
sin(...) Sine Function
cos(...) Cosine Function
sqrt(...) Square Root Function
The formula text must be placed in quotation marks (" "). If you create
a formula directly in the database window you must manually insert
the quotation marks. However, if you use the input dialog box, you
shouldn’t insert any quotation marks because these are automatically
inserted when the entry is confirmed and applied.
You may also use a large number of pre-defined variables in your
formulas.
Operating Manual ProDesigner Version 04/04 101

5.6 IF,THEN,ELSE
Please Note
5.7 Comment
Please Note
102
Refers to Formula/Condition: Condition
Description The three parameters IF, THEN and ELSE constitute
the core of conditional program processing.
(see also: chapter 4.5.3, 4.5.4, 5.6, 6.6.1, 6.6.2,
7.2.11
IF
THEN
Here you must enter the condition ("if..."). Please
make sure that the individual arguments are placed
in brackets "[...]". It is also possible to logically
combine several conditions. To make this possible a
number of basic arithmetic functions and operators
are placed at your disposal.
Here you must enter the formulas or instructions that
should be processed whenever the condition
("then...") is fulfilled.
ELSE Here you may declare the formulas or instructions
that should be processed whenever the condition
("then...") is not fulfilled ("else...").
If you wish to declare more than one instruction or formula in one
THEN or ELSE line you must separate these entries from each other
by using a semicolon, e.g. x=sin(y); dig1=0; w3=5.
Refers to all objects
Description Here you can enter an arbitrary text. This parameter
can, if you enter short texts describing the
functionality of the relevant object, generally
increase the surplus value of an object and make
orientation far easier.
If you directly create an object in a text file (in combination with a
database compiler) then the comment must be manually enclosed in
quotation marks (" "). If you use the ProDesigner input dialog window
you do not need to manually insert these quotation marks, because
they are automatically inserted whenever the object is saved.
Operating Manual ProDesigner Version 04/04

5.8 Mode
5.9 Name
Important
5.10 Priority
Refers to Variable: BCD Variable
Description Using this parameter you can determine the data type of
the BCD variable. Following data types are at your
disposal:
Type Term
0 4-digit BCD
Refers to All objects
1 KT Format Siemens PLC (resolution in seconds)
2 KT Format Siemens PLC (resolution in tenths of
seconds)
Description The name parameter is used to uniquely identify an object
inside of the process database. You must make sure that a
name is not assigned to two different objects. The
database compiler runs a "syntax test" before compilation
begins. If a name is assigned to two different objects, a
syntax error message appears informing you of this.
It is differentiated between lower and upper case lettering!!
Refers to Alarm: Bit Alarm
Description Using this parameter you can determine the
"importance/priority" of an alarm. The higher the value of
the parameter, the higher the priority of the alarm. The
priority determines what is displayed inside the dynamic
output object. This object always displays the alarm with
the highest priority.
Operating Manual ProDesigner Version 04/04 103

5.11 Source Object
5.12 Jump Width
5.13 Status
Please Note
5.14 Text Index
104
Refers to Alarm: Bit Alarm
Description
Bit-Alarm This parameter defines the digital
variable that should trigger an alarm
whenever the variable is set and has the
state "1".
Refers to Formula/Condition: Jump Object
Description This parameter is used to define the number of objects
that are jumped whenever this object is triggered.
Refers to All objects
Description These parameters control the compiler:
Active : The object is integrated into the database.
The control character "$" is inserted in front
of the Scan-Type definition.
Inactive : The object is not integrated into the
database. The control character ";" is
inserted in front of the Scan-Type definition.
Deactivating an object can make sense if the relevant object is
removed from the database for testing purposes, but the object
definition itself is not be deleted from the database.
Refers to Alarm: Bit Alarm
Description Using this parameter you must declare the text number of
the text from the index text file that is displayed in the
dynamic output control Alarm Line or Alarm List
whenever an alarm is triggered.
Operating Manual ProDesigner Version 04/04

5.15 Drivers
5.16 Conversion
6 Visualization Objects
Refers to Variables
Diverse: Structure object/System object
Description The driver type enabling a data transfer is defined via
this parameter. The following driver types may be
selected.
♦ Structure
♦ Internal
♦ LED
♦ Shared-RAM
♦ RK512
♦ System
The type Internal is used whenever no link to a real
control exists, i.e. during simulations or internal
usage.
Refers to Variable: Word, Long Word, Floating Point and Word
Description Using this parameter you can insert a conversion
factor used to adapt variable values. Usually this
conversion factor is a multiplicative factor used in
converting such values as kW to PS or km/h to
m.p.h.
Operating Manual ProDesigner Version 04/04 105

6.1 Form
6.2 Output
6.2.1 Variable Output
106
ColorBack
Comment
Inverse
Form change
Name
Picture
Form’s background color (only used if no background
picture is loaded).
Commentary used to describe the object’s
functionality.
Color swapping done inside of a graphic
(background graphic).
White turns to black, black to white.
True: Swap
False: Do not swap
You may define 12 keys with which to trigger a form
change.
Form object’s name
File name of the background graphic (formats: either
WMF or BMP).
The input and output of variable values belong to the
most important functions of process visualization. The
ProDesigner control VarOut regulates the output.
The VarOut control provides you with a large number of
setup possibilities. The property DataSource establishes
the connection to the process database. Here a predefined
display format is used. Via the Format property
you may change the pre-defined display format to a
Operating Manual ProDesigner Version 04/04

format suiting your personal requirements.
AddText
Align
AutoScale
CharCount
CharHeight
CharWidth
Comment
DataSource
DecPoint
Display
Height
Hide
HideBit
Left
Margin
Name
ShadowDepth
Top
Width
Places a text behind the variable value’s input or
output box
Aligns the display inside of the object
Automatic autoscaling to the object’s size
Number of characters in the variable text
Height of the characters in the variable text
Width of the characters in the variable text
Commentary used to describe the object’s
functionality
Link to a variable in the process database
Allows the display of decimal points
Inverse or normal object color display
Object height
If the variable’s declared HideBit is set "1" then the
object is invisible during runtime (if value is 0 then
visible). The HideBit must be reset "0" for all digital
variables.
Distance to the reference object’s left margin
Margin settings. Distance from the object’s surface in
the form to the actual object itself.
Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
Margin width
Distance to the reference object’s top margin
Object width
Operating Manual ProDesigner Version 04/04 107

6.2.2 Index Text
108
Output of a text from an index text file. You can define
the output text via the index. The text is loaded once (as
a template) during form display build-up. Color (black or
white) and index text font size can be chosen freely. The
Offset property enables various texts to be displayed,
even according to languages. (Offline language change)
The language change is realized on the development
system Configuration / Setup.
Align
CharCount
CharHeight
CharWidth
Comment
Display
Height
Hide
HideBit
Left
Margin
Name
Offset
ShadowDepth
TextOffset
TextVariable
Top
Width
Aligns the display inside of the object
Number of variable text characters to be displayed
= 0 Text displayed in its original length
> 0 Text is formatted to the defined character
length, i.e. longer entries are shortened, and shorter
entries are centered.
Height of the characters in the variable text
Width of the characters in the variable text
Commentary used to describe the object’s
functionality
Inverse or normal object color display
Object height
If the variable’s declared HideBit is set "1" then the
object is invisible during runtime (if value is 0 then
visible). The HideBit must be reset "0" for all digital
variables.
Distance to the reference object’s left margin
Margin settings. Distance from the object’s surface in
the form to the actual object itself.
Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
Determination of the various choosable output texts.
Margin width
Constant that is added to the text variable
Contains the name of the variable. The text to be
displayed in the output box can be directly
determined via the variable’s content from the index
text file
Distance to the reference object’s top margin
Object width
Operating Manual ProDesigner Version 04/04

6.2.3 Bar Graphics
The ProDesigner control offers a large number of ways to
display output variable values as bar graphs. The direction
in which the bar moves can be defined via the Direction
property. The default value for directional movement is
down to up.
Comment
DataSource
Direction
Display
Height
Hide
HideBit
Left
MaxValue
MinValue
Name
Top
Width
Commentary used to describe the object’s
functionality
Link to a variable in the process database
Direction in which the bar moves
Inverse or normal object color display
Object height
If the variable’s declared HideBit is set "1" then the
object is invisible during runtime (if value is 0 then
visible). The HideBit must be reset "0" for all digital
variables.
Distance to the reference object’s left margin
Max. variable value that can be displayed
Min. variable value that can be displayed
Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
Distance to the reference object’s top margin
Object width
Operating Manual ProDesigner Version 04/04 109

6.2.4 Alarm Line
110
An alarm or a message is displayed in one line inside of a
picture/graphic. The line size is proportional to the font
size and can therefore not be graphically changed or
edited.
CharHeight
CharWidth
Comment
Display
KeyQuit
Left
Margin
Mode
Name
ShadowDepth
Top
Height of the characters in the variable text
Width of the characters in the variable text
Commentary used to describe the object’s
functionality
Inverse or normal object color display
Triggers the acknowledge function of the selected
alarm.
Distance to the reference object’s left margin
Margin settings. Distance from the object’s surface in
the form to the actual object itself.
Display format in which the alarm output is realized.
Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
Margin width
Distance from the starting point to the form’s top
inner margin
Operating Manual ProDesigner Version 04/04

6.2.5 Alarm List
Displays incoming alarms in list form.
Actions such as, e.g.: Individual and collective alarm
acknowledgements are possible.
The display format depends on the alarm strategy setup
made during runtime.
CharHeight
CharWidth
Comment
Display
KeyDown
KeyExit
KeyPgDown
KeyPgUp
KeyQuit
KeyQuitAll
KeyUp
Left
Lines
Margin
Mode
Name
Tabindex
ShadowDepth
Top
Height of the characters in the variable text
Width of the characters in the variable text
Commentary used to describe the object’s
functionality
Inverse or normal object color display
Key pressed: Triggers function for downward cursor
movement.
Key used to exit the list
Key pressed: Triggers function for downward page
scrolling.
Key pressed: Triggers function for upwards page
scrolling
Triggers the Acknowledge function for the selected
alarm.
Triggers the Acknowledge function for all alarms
Key pressed: Triggers function for upward cursor
movement.
Distance to the reference object’s left margin
Number of displayed lines
Margin settings. Distance from the object’s surface in
the form to the actual object itself.
Display format used to display the alarm
Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
Declaration of the order in which input objects are
processed.
Margin width
Distance from the starting point to the form’s top
inner margin
Operating Manual ProDesigner Version 04/04 111

6.3 Input
6.3.1 Variable Input
112
The input and output of variable values belong to the most
important functions of process visualization. The
ProDesigner control VarIn regulates the input. The VarIn
control provides you with a large number of setup
possibilities. The property DataSource establishes the
connection to the process database. Here a pre-defined
display format is used.
AddText
Align
AutoScale
CharCount
CharHeight
CharWidth
Comment
DataSource
DecPoint
Display
Height
Hide
HideBit
KeyMode
Left
Margin
MaxValue
Adds a text after the variable value’s input box
Aligns the display inside of the object
Automatic scaling of the control’s size to that of the
output format
Number of characters in the variable text
Height of the characters in the variable text
Width of the characters in the variable text
Commentary used to describe the object’s
functionality
Link to a variable in the process database
Allows the display of decimal points
Color in which the object is displayed: Inverse or
normal
Object height
If the variable’s declared HideBit is set "1" then the
object is invisible during runtime (if value is 0 then
visible). The HideBit must be reset "0" for all digital
variables. Available from version 1.30!
Defines the mode in which input should occur:
0-Normal: Input is made via numbers or keyboard
characters
1-Cursor: Input is made via special "fictive" keys
Distance to the reference object’s left margin
Margin settings. Distance from the object’s surface in
the form to the actual object itself.
Max. allowable input value
MinValue Min. allowable input value
Operating Manual ProDesigner Version 04/04

6.3.2 Form Change
Name
ShadowDepth
TabIndex
Top
Width
Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
Margin width
Position in the tabulator queue
Distance to the reference object’s top margin
Object width
By pressing a pre-defined key you can trigger a form
change. This control is useful due to the fact that a
project usually contains more than just one form. Using
this control allows you to switch from and into all the
forms existing in your project.
Comment
Key
Left
Form
Name
Top
Commentary used to describe the object’s
functionality
Pre-defined key that triggers, whenever pressed, a
form change
Distance to the reference object’s left margin
Name of the form or of a variable containing the form
number. If a variable is inserted into this field you
must add the "$" character as a prefix to the variable
name.
Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
Distance to the reference object’s top margin
Operating Manual ProDesigner Version 04/04 113

6.3.3 1 Pin Switch
Please Note
6.3.4 2 Pin Switch
114
Using this control you can graphically realize the
functionality of a 1 pin switch. The SwitchMode property
defines the switching behavior. The object is only visible in
development mode and is not graphically displayed during
runtime.
Bit
Comment
DataSource
Key
Left
Name
SwitchMode
Top
The object’s function is based on this one bit number
Commentary used to describe the object’s
functionality
Link to a variable in the process database
Defines the keycode used to trigger the object
Distance to the reference object’s left margin
Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
Switches operation mode
(On - Off, Non-locking key ...)
Distance to the reference object’s top margin
The operation type non-locking key (SwitchMode = Push Button)
cannot be executed in a simulation.
This object is used to realize a 2 pin switch. The object is
only visible in development mode and is not graphically
displayed during runtime.
Comment
DataSource
Key-IOFF
Key+ION
Left
Name
SwitchMode
StepBit
Top
Commentary used to describe the object’s
functionality
Link to a variable in the process database
Key for bit decrease or bit off
Key for bit increase or bit on
Distance to the reference object’s left margin
Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
Switch operation mode (On - Off, Non-locking key ...)
Step width or bit number declaration
Distance to the reference object’s top margin
Operating Manual ProDesigner Version 04/04

6.4 Graphic
6.4.1 Picture
Import of additional BMP or WMF graphic into the
background.
AutoScale
Height
Left
Name
Picture
Top
Width
Automatic adaptation of the graphic control to the
exact size of the loaded graphic.
Height of the graphic control
Distance to the reference object’s left margin
Name of the graphic control
File name of the graphic to be displayed. Formats:
either BMP or WMF in black and white!
Distance to the reference object’s top margin
Width of the graphic control
Operating Manual ProDesigner Version 04/04 115

6.4.2 Static Text
6.4.3 Shape
116
Using the graphic control Static Text you can permanently
place a text into the background.
This object is not linked to a process variable.
Align
Caption
Comment
Display
Font
Height
Left
Margin
Name
ShadowDepth
Top
Width
Alignment of the text display inside of the graphic
control
Text shown in the graphic control
Commentary used to describe the object’s
functionality
Inverse: opposite color with respect to the
background
Normal: Same color as the background
Font dialog box (Windows ® Dialog Window)
Height of the graphic control
Distance to the reference object’s left margin
Positioning of the variable text output inside of the
output line.
Name of the graphic control
Margin width
Distance to the reference object’s top margin
Width of the graphic control
Using the ProDesigner graphic element you can insert
geometric shapes into the background picture. These
shapes are defined via the Shapetype property.
The object is not linked to a process variable.
ColorBack
ColorLine
Height
Left
LineWidth
Name
ShapeType
Top
Width
Fill color of the geometric object.
Color of the geometric object’s line.
Height of the graphic object
Distance to the reference object’s left margin
Line width of the graphic object. An input of “0”
means no border.
Name of the graphic object
Shape type Chooser
Distance to the reference object’s top margin
Width of the graphic object
Operating Manual ProDesigner Version 04/04

6.4.4 Grid
6.4.5 Line
Using the Grid element you can insert a grid into the
background of a form. The grid segment size, as well as
the width and color of the gridlines may be chosen freely.
The object is not linked to a process variable.
AutoScale
ColorLine
GridWidthX
GridWidthY
Height
Left
LineWidth
Name
Top
Width
Automatic setting to line grid size
Color of the geometric object’s line
Horizontal width of a grid segment
Vertical width of a grid segment
Height of the object
Distance to the reference object’s left margin
Grid line width, 0 = none, 1 = 1 Pixel wide
Name of the graphic object
Distance to the reference object’s top margin
Width of the graphic object
Using the graphic element Line you can construct custom
forms and lines inside of the form.
The object is not linked to a process variable.
ColorLine
Height
Left
LineType
LineWidth
Name
Top
Width
Color of the geometric object’s line.
Height of the object
Distance to the reference object’s left margin
Defines the line course (diagonal, horizontal, custom
defined line changes ...)
Line width, 1 = 1 Pixel wide
Name of the graphic object
Distance to the reference object’s top margin
Width of the graphic object
Operating Manual ProDesigner Version 04/04 117

6.5 Symbols
6.5.1 Symbol
118
Using this symbol object you can create various
graphics and symbols in dependent to a process
variable. If the Symbol Variable property is not declared,
then the output of the symbol is done as declared in the
Symbol Offset property. The symbol is then static and
can only be blended in and out via the Hide variable.
Comment
Height
Hide
HideBit
Left
Name
SaveBkGnd
SymbolOffset
Symbols
SymbolVariable
Top
Width
Commentary used to describe the object’s
functionality
Height of the graphic element; this value cannot be
changed. It is based on the size of the symbol to be
displayed.
If the variable’s declared HideBit is set "1" then the
object is invisible during runtime (if value is 0 then
visible). The HideBit must be reset "0" for all digital
variables.
Distance from the starting point to the forms left
margin
Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
Background is saved whenever a symbol is changed.
This guarantees that the background is always
retained
Constant that is added to a symbol variable
Icon used to represent a symbol in the development
environment
Contains the variable name. The contents of this
variable is used to determine the symbol displayed
on the screen
Distance from the starting point to the form’s top
inner margin
Width of the graphic element; this value cannot be
changed. It is based on the size of the symbol to be
displayed.
Operating Manual ProDesigner Version 04/04

6.5.2 Moving Symbol
Using this control you can move a graphic (symbol)
across the screen in the X/Y direction. The graphic’s
motion across the screen is controlled by a process
variable. The movement always occurs along a straight
line. The area in which the object moves is determined
by the properties XmaxValue, XMinValue, as well as
YmaxValue, YminValue.
The properties MinValue and MaxValue are used to
scale the movement. During runtime the displayed
symbol can be switched using a process variable
(SymbolVariable).
Comment
DataSource
Height
Hide
HideBit
Left
MaxValue
MinValue
Name
SaveBkGnd
SetEndPos
Symbol Max Off
Symbol Min Off
SymbolOffset
Symbols
SymbolVariable
Top
Width
X / YvalueMax
Commentary used to describe the object’s
functionality
Link to a variable in the process database; this
variable determines the position where the symbol is
displayed.
Height of the graphic element; this value cannot be
changed. It is based on the size of the symbol to be
displayed.
If the variable’s declared HideBit is set "1" then the
object is invisible during runtime (if value is 0 then
visible). The HideBit must be reset "0" for all digital
variables.
Distance from the starting point to the forms left
margin
Max process variable value
Min process variable value
Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
Background is saved whenever a symbol is changed.
This guarantees that the background is always
retained
Simple end position determination for a moving
graphic symbol
The symbol, disappears whenever the max value is
breached
The symbol, disappears whenever the min value is
breached
Constant that is added to a symbol variable
Icon used to represent a symbol in the development
environment
Contains the variable name. The contents of this
variable is used to determine the symbol displayed
on the screen
Distance from the starting point to the form’s top
inner margin
Width of the graphic element; this value cannot be
changed. It is based on the size of the symbol to be
displayed.
max. X-/Y- coordinate variable value. If this value is
breached the symbol is blended out
Operating Manual ProDesigner Version 04/04 119

6.6 Special
6.6.1 Formula
6.6.2 Condition (IfElse)
120
Using this function you can execute “simple“ calculations.
e.g.: c = a + b ; c = a * b
Comment
Condition
Left
Name
Top
Commentary used to describe the object’s
functionality
Formula and condition block
(see also: chapter 4.5.3, 4.5.4, 5.6, 6.6.1, 6.6.2,
7.2.11)
Distance from the starting point to the forms left
margin
Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
Distance from the starting point to the form’s top
inner margin
If-then-else enables simple case differentiation during
runtime.
(see also: chapter 4.5.3, 4.5.4, 5.6, 6.6.1, 6.6.2,
7.2.11)
e.g.: automatic counter 0 to 100
Comment
Condition
Left
Name
Top
if [w0

6.6.3 Date and Time
Using this element you can display the date and time
anywhere inside the form.
The displayed time is based on the internal clock of your
operating panel.
Align Aligns the display inside of the object
CharHeight Height of the characters in the variable text
CharWidth Width of the characters in the variable text
Display Color in which the object is displayed: Inverse or
normal
Format Date and time format used in the display
Height Object height
Left Distance to the reference object’s left margin
Margin Margin settings. Distance from the object’s surface in
the form to the actual object itself.
Name Object’s name, up to a length of max. 8 letters or
numbers. Symbols and Umlauts, as well as underline
are not allowed. Name must begin with a letter!
ShadowDepth Margin width
Top Distance to the reference object’s top margin
Width Object width
Operating Manual ProDesigner Version 04/04 121

6.6.4 KeyCoding
122
Used to recode keys to accommodate for the various
operating panel variations .
The keys (e.g. S1 to S9) can trigger other functions (e.g.
numbers 1-9, function keys F2-F11, letters or special
characters).
Only one keycoding object may be used per form!
Up to 10 keys may be redefined using this object.
Comment
DefaultKeys
Global
Left
Name
KeyCoding
Top
7 Object Properties
Commentary used to describe the object
True Keycoding entries are filled with default
values
False Entries are taken from the KeyCoding
property
Defines the keycoding for all subsequent pages until
a form change is triggered that contains a new
keycoding object
Distance to the reference object’s left margin
Name of the object, max. 8 numbers or letters,
underline, no symbols, no umlauts. Must begin with a
letter!
Input dialog for keycoding
Distance to the reference object’s top margin
Operating Manual ProDesigner Version 04/04

Operating Manual ProDesigner Version 04/04 123

7.1 General
7.1.1 Variable Dialog Box
124
Menu activation
Activates the Inspector
Or Clicking the visualization object using the mouse
automatically adapts the Inspector contents to the
chosen object.
Simply click the window using the mouse.
Every ProDesigner object has its own Inspector.
Chapter structure In this chapter the individual properties are described
in alphabetical order.
The setup modalities, e.g. variable dialog box that
are valid for many of the properties will be described
once in this section.
This dialog box is displayed for all those properties where the
declaration of a process variable is enabled. The dialog, when called
up the first time, contains all variables defined in the process
database. Display of certain data types can be manipulated via the
Filter tag.
Name Name of the variable according to its definition
in the process database.
Operating Manual ProDesigner Version 04/04

Please Note
Data Type Data type of the variable according to its
definition in the process database.
Driver Variable’s driver according to its definition in the
process database. The structure driver is
displayed for variables embedded in structures.
Address Address of the variable according to its
definition in the process database.
Comment Comment of the variable according to its
definition in the process database.
The Filter tag is used to select the display seen under the Variables tag.
Filter Variable Type
Filter Driver”
Filter Data Type
All Variable Types
All Drivers
All Data Types
Shows the selected variable types, driver types
and data types that should be included in the
Variable tag display.
All types defined in the process database are
displayed here.
Change If the All … Dialog is deactivated, individual
components may be selected or unselected.
The variable list displayed in the dialog box is based on the last
compiled version of the process database. Variables that were
added after the last compilation are not included in the dialog box list
(Run / Compile Process Database).
Operating Manual ProDesigner Version 04/04 125

7.1.2 Input
126
The choice and set-up of object properties occur via the Properties
window. There are various input possibilities depending on the type of
property.
Choosing an object for editing can
be done by either clicking the
object inside of the Designer or via
the list in the Properties dialog.
The keyboard can be used to enter
simple inputs, e.g. a bit number.
Operating Manual ProDesigner Version 04/04

Please Note
Inputs such as, e.g. a variable, can
be both inputted directly via the
keyboard or via a dialog.
Properties that use dialogs display
a button. Clicking this button
opens the corresponding dialog.
Inputs that await a pre-defined
value, e.g. the SwitchMode
property, can only be entered via a
list. Properties that use lists display
a button. Clicking this button
opens a Chooser list. Selection
inside of this list is done using the
cursor keys. A double-click or
pressing the key
enters the selected value.
Property editing is only done for each individual object. Multiple object
selection is not possible here.
Operating Manual ProDesigner Version 04/04 127

7.2 ... in Alphabetical Order
7.2.1 AddText
Description This property is used to an arbitrary text to the input
or output of a variable value field. You can display
output variable values together with a letter
combination representing a unit, e.g. "1V" etc.
7.2.2 Align
128
Settings see chapter 7.1.1+ 7.1.2
Insert the test entry.
Allowed Input: max. 200 characters (including ® , ©,
£ ... ASCII), however not index texts!
Description This property is used to determine the alignment
of the input, output or of the text display inside of
an object.
Settings Menu Dialog
Example
TopLeft Top left
TopCenter Top center
TopRight Top right
MiddleLeft Middle left
MiddleCenter Middle center
MiddleRight Middle right
BottomLeft Bottom left
BottomCenter Bottom center
BottomRight Bottom right
Operating Manual ProDesigner Version 04/04

7.2.3 AutoScale
7.2.4 Bit
7.2.5 CharCount
7.2.6 CharHeight
Description This property is used to automatically scale the
size of an object to the exact size of the area in
which it is displayed. Objects that have the Picture
property have their settings adjusted to original size
of the graphic.
Function After the entry has been made the value is
automatically reset to zero.
Settings Menu Dialog
True Autoscaling to the object’s font or
graphic size.
False Objects can be arbitrarily scaled to any
size.
Description If you declared a word or long word variable under
the DataSource property then you can determine a
certain Bit of this variable that should be surveyed,
displayed or edited.
Settings Allowed Input: Numbers 0 ... 31
Description The CharCount property determines the number of
characters used in the control’s output text during
runtime.
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: 1 to max 80 characters. Dependent
on chosen object.
Description The CharHeight property determines the height of
the text inside of the control. The base value is a font
size of 8. The entry 1 would therefore mean a Pixel
height of 8 (1 * 8 (base value)), an entry of 2 would
result in a height of 16 etc.
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: 1 ... 2
Operating Manual ProDesigner Version 04/04 129

7.2.7 CharWidth
7.2.8 ColorBack
7.2.9 ColorLine
7.2.10 Comment
130
Description The CharWidth property determines the width of the
text inside of the control. The base value is a font
size of 6. The entry 1 would therefore mean a Pixel
width of 6 (1 * 6 (base value)), an entry of 2 would
result in a height of 12 etc.
Settings ... see CharHeight
Description Fill color of the geometric object.
Settings Menu Choice: Black or white.
Description Color of the geometric object’s line.
Settings Menu Choice: Black or white.
Description The Comment property is used to add a custom text
or name to the name of an object. This name
appears at the lower border of the window.
Example
Allowed Input: max. 28 characters
Operating Manual ProDesigner Version 04/04

7.2.11 Condition
7.2.12 DataSource
7.2.13 DecPoint
Description This property allows you to operate simple
calculations (manipulation of process values).
Settings
Variables ( ) all types of brackets in
conditions
= Allocation to variables (not in
conditions)
=, !=,

7.2.14 DefaultKey
7.2.15 Direction
7.2.16 Display
7.2.17 Form
132
Description This setting is used to restore the default key settings
after a KeyCoding procedure has taken place.
Settings True
False
A KeyCoding object is created. The
settings in this object can be filled with
default values.
Applies the entries made in the
KeyCoding property.
Description This property allows you to determine the display’s
direction of propagation
Settings see chapter 7.1.1+ 7.1.2
Up Bar moves upwards
Down Bar moves downwards
Left Bar moves to the left
Right Bar moves to the right
Description Object’s display color.
Settings Menu Dialog
Normal: Black fonts on white background
Inverse: White fonts on black background
Description Name of the form to be switched into, or alternatively
the declaration of a variable containing the form’s
number.
Example $Variable name must have the "$" prefix
Form name without "$" prefix
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: 8 characters (according to DOS
regulations)
Operating Manual ProDesigner Version 04/04

7.2.18 Format
7.2.19 Global
7.2.20 Height
Description Changes the time and date’s input and output
format.
Settings see chapter 7.1.1+ 7.1.2
HH
MM
SS
YY
YYYY
DD
Hour
Minute or Month
Seconds
Year displayed using 2 digits
Year displayed using 2 digits
Day
Description Is used in the KeyCoding object and determines
whether the object's settings should be valid for the
following forms that do not have an own KeyCoding
object. The user is therefore able to create a starting
form containing this object, whereby all the following
forms refer to the object on the starting page.
Settings True
False
Global settings active.
Not active. Settings are only valid for the
currently active form.
Description The Height property determines the height of an
object in Pixels. This can be used as an alternative to
the mouse.
Settings see chapter 7.1.1+ 7.1.2
7.2.21 Hide (from Vers. 1.20: Visible)
Description The variable’s content decides whether the object in
a picture is processed or not. Allows the blending out
of momentarily non-required functions.
Settings Variable declaration
7.2.22 HideBit (from Vers. 1.20: VisibleBit)
Description This property is only used in combination with the
Visible (Hide) property.
Operating Manual ProDesigner Version 04/04 133

7.2.23 Inverse
7.2.24 Key
7.2.25 KeyCoding
7.2.26 KeyDown
134
Description The Inverse property allows the reversal of the
color display: Here between black and white.
Settings True Colors are reversed
False Colors are not reversed
Description The Key property defines the key used to trigger an
object function.
Settings Allowed Input: Keyboard codes according to list
see chapter 10.1or selection via a dialog in which
all keys are displayed respectively.
Description
The KeyCoding dialog The existing "key" (of the
operating panel) is inputted into the Key dialog. In
the Key New dialog the new key to be used instead
of the old key is inputted. see chapter 10.1
Settings Valid field entries see chapter 10.1
Description The KeyDown property defines the key that is used
to move one step down the alarm list.
Settings Allowed Input: Keyboard codes according to the list
see chapter 10.1
Operating Manual ProDesigner Version 04/04

7.2.27 KeyExit
7.2.28 Key-IOFF
7.2.29 Key+ION
7.2.30 KeyMode
Description The KeyExit property defines the key that is used to
exit the editing of an object (alarm list).
Settings Allowed Input: Keyboard codes
see chapter 10.1
Description The Key- property defines the key that is used to
decrease a certain variable. StepBit defines the
measure by which the variable is decreased
whenever the key is pressed.
The KeyOFF property defines the off switch key used
in changeover switches.
Settings Allowed Input: Keyboard codes
see chapter 10.1
Description The Key+ property defines the key that is used to
increase a certain variable. StepBit defines the
measure by which the variable is increased
whenever the key is pressed.
The KeyON property defines the on switch key used
in changeover switches.
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: Keyboard codes
see chapter 10.1
Description This property defines the mode how inputs are
confirmed and accepted.
Settings 0-normal Enter key accepts value and
moves the input focus to the next
input object.
1-Cursor Input is made via special "fictive"
keys with which an input can be
made without the numeric
keypad. The following keys are
available:
INP_INC: The character/symbol
in possession of the input focus is
incremented.
INP_DEC: The character/symbol
in possession of the input focus is
decremented.
INP_L: The cursor in the input
field is moved one place to the
left, or the input mode is activated
respectively.
INP_R: The cursor in the input
field is moved one place to the
right, or the input mode is
activated respectively.
Operating Manual ProDesigner Version 04/04 135

7.2.31 KeyPgDown
7.2.32 KeyPgUp
136
Description The KeyPgDown property defines the key used to
scroll a document or list down one page
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: Keyboard codes
see chapter 10.1
Description The KeyPgUp property defines the key used to scroll
a document or list up one page
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: Keyboard codes
see chapter 10.1
Operating Manual ProDesigner Version 04/04

7.2.33 KeyQuit
7.2.34 KeyQuitAll
7.2.35 KeyUp
7.2.36 Left
7.2.37 Lines
Description The KeyQuit property defines the key used to
acknowledge an incoming alarm
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: Keyboard codes
see chapter 10.1
Description The KeyQuitAll property defines the key used to
acknowledge all alarms
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: Keyboard codes
see chapter 10.1
Description The KeyUp property defines the key that is used to
move one step up the alarm list.
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: Keyboard codes
see chapter 10.1
Description The Left property determines the X position of an
object. The reference point and zero point is the
corresponding parent object
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: Numbers 0 to max. display size
(dependent on the form’s format or display size
respectively)
Description Number of lines to be displayed in the alarm list.
Settings Allowed Input: Numbers 1 to max. display size / font
height (display size dependent)
Operating Manual ProDesigner Version 04/04 137

7.2.38 LineType
7.2.39 LineWidth
7.2.40 Margin
138
Description Type of used line.
Settings Diagonal 1: From top left to bottom right.
Diagonal 2: From bottom left to top right.
Horizontal: Horizontal line.
Vertical: From top to bottom.
UserDef:
Clicking the line adds navigation points to the line.
These points may then be pulled to a arbitrary
position inside the object thus creating a custom line.
Description Line width of the graphic object.
Settings Valid Input: Numbers from 0 to max. display size
(dependent on format of form or display size
respectively).
Description The Margin property defines the margin settings,
e.g. the distance between the output (text) to the
object’s margin.
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: Numbers 1 = 1 Pixel
Example
30
10
0
Operating Manual ProDesigner Version 04/04

7.2.41 MaxValue/MinValue
7.2.42 Mode
7.2.43 Name
Description The MaxValue/MinValue properties are used to
define the max./min. boundaries of input or output
variables.
If the variable value is larger than MaxValue, or
smaller than MinValue, then no changes are
displayed on the screen.
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: Variable or number – dependent on
the object type
Description The Mode property determines the output mode of
an alarm.
Settings _
P
D
Z
S
Non
Priority
Date
Time
Status
e.g.
____
___S
__Z_
__ZS
_D__
_D_S
_DZ_
P___
P__S
P_Z_
PD__
PD_S
PDZ_
PDZS
Description The Name property assigns an object a name. This
name uniquely identifies the object.
Settings Allowed Input: max. 8 characters (DOS level). The
first character must be a letter. The name of an
object may only be assigned once (i.e. unique) to
each form. The name of a form may only be
assigned once (i.e. unique) in each project.
Operating Manual ProDesigner Version 04/04 139

7.2.44 Picture
7.2.45 SaveBkGnd
7.2.46 SetEndPos
140
Description The Picture property is used to load a graphic into
the background of an object. Valid graphic formats:
BMP or WMF with a color palette used by the target
system (here black and white).
Settings see chapter 7.1.1+ 7.1.2
Double click the selected graphic file. The graphic is
inserted and the dialog window is automatically
closed.
Description The background behind a symbol is saved so that
the background can be restored whenever the
position of a symbol is changed. If the background
behind a symbol is not saved then the background
picture displays “holes” whenever the symbol is
moved. This property requires a large amount of
memory and should therefore only be used if the
symbol moves across a large enough area (i.e.
moves across more than one graphic picture).
Settings True Background is saved
False Background is not saved
Description The SetEndPos property enables you to
automatically set the XvalueMax and YvalueMax
properties via graphic object positioning.
Position the graphic to its start position
- setting to TRUE
Move the graphic to its end position
- setting to FALSE
The graphic then moves back to its start position and
memorizes the path it took.
Allowed Input: True and false
Operating Manual ProDesigner Version 04/04

7.2.47 ShadowDepth
7.2.48 ShapeType
7.2.49 StepBit
7.2.50 SwitchMode
Description The ShadowDepth property defines the margin width
in Pixels.
Settings Allowed Input: 0 ... "½ of the object size"
Description The ShapeType property defines the type of shape.
This object may assume various shapes.
Settings tCircle Circle
tEllipse Ellipse
tRectangle Rectangle
tRoundRect Rectangle with rounded edges
tRoundSquare Square with rounded edges
tSquare Square
Description The StepBit property defines the step size or the
number of the Bit that should be set/reset.
Settings Numbers from 0 ... 256
Description The SwitchMode property determines the mode of
1 pin and 2 pin switches.
1 Pin Switch Switch Rotation between "0" and "1".
SwitchOn Sets the Bit to "1"
SwitchOff Sets the Bit to "0"
PushButton Bit is "1" as long as the key is
pressed
2 Pin Switch Step The switch functions as a step
switch
Bit The switch changes a
DataSource bit
Operating Manual ProDesigner Version 04/04 141

7.2.51 SymbolMaxOff/SymbolMinOff
Description This property determines whether a symbol is
displayed whenever the MaxValue or MinValue is
reached.
7.2.52 SymbolOffset
7.2.53 Symbols
7.2.54 SymbolVariable
7.2.55 TabIndex
142
Settings True
False
is not displayed
is displayed, however remains static at
the Max/MinValue
Description The SymbolOffset is added to the SymbolVariable
content resulting in the number of the symbol to be
displayed.
Settings 0 ... 99
Description The symbol name must be entered here in order for
the corresponding symbol to be displayed on the
development system (only numbers without a file
extension).
Description Variable that contains the number of the symbol to
be displayed (added to SymbolOffset).
If the SymbolOffset is 100 and the SymbolVariable
value is "0" or "1" then symbol100 or 101 are
displayed.
Description The TabIndex property determines the Tabulator
order of the object inside of the form.
This is the order in which objects get the focus when
or is pressed respectively.
The order is incremental and successive numbering
is not required. This allows for future changes such
as the insertion of new input fields.
The tabindex can be blended in and out via the
Designer’s context menu.
Settings see chapter 7.1.1+ 7.1.2
Allowed Input: 0 ... n (whole numbers)
Example
Operating Manual ProDesigner Version 04/04

7.2.56 TextOffset
7.2.57 Top
7.2.58 Width
Description This property is used in the index text object and
declares the value (offset) that is added to the
content of the variable declared in the DataSource
property. This is done to get the text number to be
displayed.
Settings 0 … 7999
Description The Top property determines the Y position of an
object. Reference and zero point is the respective
parent object. This is normally the form and the top
property contains the distance between object and
the top border of the form.
Settings see chapter 7.1.1+ 7.1.2
Allowed Input:
Numbers 0 ... max. display size
Description The Width property determines the width of an object
in Pixels. This can be used as an alternative to the
mouse and used pixel-exact measurements.
Settings see chapter 7.1.1+ 7.1.2
Allowed Input:
0 ... to max. display size
7.2.59 Visible (from Vers. 1.30: Hide)
Description The variable’s content decides whether the object in
a picture is processed or not. Allows the blending out
of momentarily non-required functions.
Settings Variable declaration
7.2.60 VisibleBit (from Vers. 1.30: HideBit)
Description Contains the number of the variable’s bit that causes
an action.
7.2.61 WantReturn
Settings Whole numbers corresponding to the data type of the
variable (0 for digital variables, 0 … 15 for word
variables, …)
Description This property determines the behavior of input fields
when input is concluded by pressing .
Settings True
False
The input focus remains in the input field
after is pressed.
The input focus is moved to the next
input field after is pressed.
7.2.62 XValueMax / YValueMax
Description These properties determine the highest possible
value for the movement of a variable from its starting
point. Minimal values are the declared start positions
Left and Top.
XvalueMax = 100 means that the object can move a
Operating Manual ProDesigner Version 04/04 143

8 Editing Objects in the Designer
144
maximum of 100 Pixels along the X-axis.
Settings Allowed Input based on the target systems display
size in Pixels.
The user has various method at his/her disposal in order to edit an
edit and change an object via the Designer’s context menu (right
mouse button click in the Designer).
Selecting Click the object to be changed using the mouse.
Small squares (see above) mark the object and the
Inspector displays the corresponding parameters.
Changing size If you place the mouse cursor above one of these
squares the cursor changes into an arrow. Press and
hold the left mouse button and pull the mouse to
enlarge or make the window smaller.
Selecting several
objects
Changing size
In order to simultaneously move a group of objects
click and hold the left mouse button near one of the
objects and pull open a frame. This frame should be
made as large as necessary to contain all those
objects you wish to move. All objects contained in
this box are surrounded by the same small squares
as mentioned above. If one of the marked objects is
moved then all marked objects are moved. The
relative positions of the objects to one another
remain identical.
direction.
to zoom in the corresponding
Move to move the object in the
corresponding direction.
Each time you press the above combination the
object moves one unit in the corresponding direction.
Operating Manual ProDesigner Version 04/04

8.1 Lining up Objects The selected object is „docked“ to the „nearest“ grid coordinate point.
This function is dependent on the settings made in the Configuration /
Development menu.
See also chapter 3.4.1
8.2 Bringing Objects to the Top of the Display
8.3 Putting Objects to the bottom of the Display
The selected object is brought to the top of the form and is placed above all
other objects.
The selected object is pushed to the bottom of the form and is placed below
all other objects.
Operating Manual ProDesigner Version 04/04 145

8.4 Alignment Menu
8.4.1 Basic Knowledge:
146
The prerequisite for aligning and positioning objects is that the objects
can be selected together GroupWise (Lasso function or + left
mouse button).
The result of this is that the controls can be aligned, can have their
size changed and can be better positioned on the form making form
development far easier. High precision is achieved by using various
dimension fields. You no longer have to make educated guesses
when aligning and changing the size of controls, with respect to both
containers and controls.
Selecting controls: Keyboard combination + left mouse button
Reference
control:
Lasso function: Click and hold the left mouse button
near one of the objects and pull open a frame until
the frame contains all those controls you wish to
select.
Is usually the first control in the group that was
selected.
When selecting objects using the Lasso function it is
not always clear which object was selected first. If
this happens then control alignment and positioning
occurs as follows:
The "Position" functions assume that the reference
control is either the control that is positioned farthest
to the right, left, top or bottom.
The "Group" functions assume that the control
farthest to the left or right is the reference control.
Functions referring to size require a reference
control. If none exists a message appears asking you
to do so. To do this and go back one step and select
the control you wish to use as your reference control.
You may now continue and use the size functions.
You do not require a reference control for centering
functions.
Operating Manual ProDesigner Version 04/04

Position Arrangement
These functions apply to groups of selected controls. The following
functions are normal alignment functions.
Clicking... Has following effect on the controls...
The left sides of the controls are aligned.
The right sides of the controls are aligned.
The top sides of the controls are aligned.
The bottom sides of the controls are aligned.
The controls are horizontally aligned to their centers.
The controls are vertically aligned to their centers.
The controls are horizontally and vertically aligned to
their parent.
The controls are vertically aligned to their parent.
The controls are horizontally aligned to their parent.
Two controls swap their respective positions.
Operating Manual ProDesigner Version 04/04 147

Size Arrangement
148
Using the size tools you can change the size of controls in various
ways: The size of controls (groups of controls) can be simultaneously
changed whilst retaining their relevant dimensions and positions to
each other or the parent can be adapted to the size of the controls
and vice versa.
Clicking... Has the following effect on the controls...
Same vertical and horizontal size.
Same vertical size.
Same horizontal size
Objects have the same size as their parent’s client
area. Using you can define the
horizontal and vertical margin to the parent in Pixels.
Objects have the same size as their parent’s client
area, however only vertically.
Objects have the same size as their parent’s client
area, however only horizontally.
Has the following effect on the parent
Parent is matched to the size of the control.
Parent is matched to the size of the control, however
only vertically.
Parent is matched to the size of the control, however
only horizontally.
Has the following effect on the number of Pixels
Defines the margin in Pixels between the controls and
the parent.
Operating Manual ProDesigner Version 04/04

Grouping
These tools are used to arrange the selected controls into groups in
different formations.
Clicking… Has the following effect on…
The controls’ vertical arrangement
The controls’ vertical arrangement
to ON
a) Aligned to the right control side
b) Aligned to the left control side
c) Aligned to the center of the control
The distance between the controls is defined in the
dialog box (see left). All values are defined in Pixels. If
the value is negative the controls overlap each other.
a) Aligned to the lower control side,
b) Aligned to the upper control side,
c) Aligned to the center of the control.
The distance between the controls is defined in the
dialog box (see left). All values are defined in Pixels. If
the value is negative the controls overlap each other.
The controls are stapled regularly inside of the parent.
The defined spacing between the objects is ignored.
This function is useful whenever Option buttons need to
be aligned inside of a control.
Operating Manual ProDesigner Version 04/04 149

8.5 Display Tab Order
The contents of the Tabindex property are displayed in the object.
This function is used to check the object input order.
8.6 Form List
150
See chapter 7.2.55
This function is used to quickly switch between all existing forms of a
project. The user may either select the form via a dialog, or just
directly input the form to which he/she wishes to switch into.
Operating Manual ProDesigner Version 04/04

8.7 Zoom Factor
9 Error Messages
Changes the size in which the form is displayed.
Zoom Factor 1
Zoom Factor 2
Zoom Factor 3
Operating Manual ProDesigner Version 04/04 151

152
Operating Manual ProDesigner Version 04/04

9.1 Errors on the Development System
Whenever the form or project is compiled an output dialog window is
displayed showing the current status of the compilation process.
Important
The compiler window is displayed at the bottom of your screen. It
contains information on the status and displays any incoming error or
warning messages that occur during compilation.
If an error message is displayed you can receive more detailed
information concerning the error via the menu
View / Error List (or ). This opens a window containing a detailed
list of all the errors and messages that occurred during the compilation
of the form or project respectively. If a project was compiled and the
currently active form contained no errors, but an inactive form did,
then the ProDesigner informs you of this and requests permission to
switch into the form containing the error.
Double clicking the line in the error list window automatically assigns
the focus the object in the corresponding form containing the error, i.e.
the cursor moves to the exact object that caused the error to occur. As
soon as the object containing the error receives the focus its inspector
is opened and the corresponding property with the error is selected.
It should be noted that whenever a form is compiled no check is made
as to if the DataSources defined in the objects really exist.
Please make sure that you, when declaring DataSources, keep in
mind that the program does make a distinction between lower and
upper case lettering!
Operating Manual ProDesigner Version 04/04 153

9.2 Errors on the Runtime System
If an error occurs during runtime or during a runtime simulation the
program is automatically terminated and an error message is
displayed, which can exited by pressing the or key
respectively.
154
The displayed error message has the following structure:
• Error Number
• Object Number
• Object Type
• Position in the DTX- or PTX file respectively
• Short description or object name respectively
E.g.: Error: 13 Object:-1 Type:-1 Position:0 -> no object defined
Operating Manual ProDesigner Version 04/04

9.2.1 Error Number (Error)
The error messages from error number 400 upwards are exclusively
reserved for COP-Handy runtime errors.
No. Comment
2 Variable type is not valid.
3 Declared object not found in the database.
5 Declared minimum value is greater than maximum value.
12 Not enough memory.
13 No objects defined in the database (not valid).
100 Colon missing after structure (Structure:Offset).
101 Variable offset in structure is greater than the structure size.
102 Text variable not embedded in a structure.
103 Structure variable has an odd offset.
403 Wrong variable type (write) used with the Shared-RAM driver.
405 Wrong variable type (read) used with the Shared-RAM driver.
410 Variable type used with the LED driver not digital or word (read).
420 Variable type used with the LED driver not digital or word (write).
484 Shared-RAM version and driver version do not match.
490 The structure length to be read is larger than the ERROR structure size.
491 Shared-RAM size is smaller than the structure size (read).
492 Shared-RAM size is smaller than the structure size (write).
500 The wrong driver was selected in the Set-Up menu, or a false driver is being
used in the application’s process database.
501 A false address was declared in the process database.
502 The variable type is undefined (should not be able to happen!).
503 The created error structure (ERR_RK512) is larger than allowed (max. 12
Bytes = 6 words).
601 Recipe structure could not be installed (simulation only).
602 Variable for recipe name not found.
603 Invalid variable type for recipe name. Only INT, BCD, LONG allowed
606 Invalid variable type for recipe saving. Only DIGIT, BCD, INT, LONG allowed
607 Invalid variable type for recipe loading. Only DIGIT, BCD, INT, LONG
allowed
608 Invalid variable type for recipe writing. Only DIGIT, BCD, INT, LONG allowed
609 Invalid variable type for recipe reading. Only DIGIT, BCD, INT, LONG
allowed
610 Invalid variable type for recipe deletion. Only DIGIT, BCD, INT, LONG
allowed
800 Invalid address declaration in system driver
801 Invalid structure length of a system driver object
Operating Manual ProDesigner Version 04/04 155

9.2.2 Object Number (Object)
n-th object in the "PTX" file (picture database) or "DTX" file (process
database), beginning at 0
9.2.3 Object Type (Object type)
156
You can examine the PTX file in the development environment via the
menu View / Project Administration.
Type Process Database Picture Database
0 Digital variable Var. input
1 Word variable Var. output
2 Floating point variable Bar graphics
3 Long word variable Form change
4 BCD Variable Index text output
5 Formula Formula
6 Condition Condition
7
8 1-pin switch
9 Alarm 2-pin switch
10 Double Precision Variable Time and Date
11 Structure Static symbol
12 Moving symbol
13 Alarm list
14 Alarm line
15 Line object
9.2.4 Position in the "DTX" or "PTX" file
The n-th object property as defined in the "PTX" or "DTX" file order.
see chapter 3.3.1+ 3.3.2
9.2.5 Short Description or Object Name
Short description of the location where the error occurred, or the
declaration of the object name where objects are missing or objects
are of the wrong type.
Operating Manual ProDesigner Version 04/04

9.3 Differences between Runtime and Simulation
The development system contains a simulation of the target system
(COP-Handy, COP) enabling the user to test the project. This
simulation emulates the behavior of all individual application
components (forms, form changes, formula and condition processing
etc.). Differences in behavior between runtime and simulation can
occur due to the hardware differences between the target system
(Motorola) and the development system (Intel), as well as the nonexistent
link to a control.
- No changes occur in the control’s process variables, because no
link to the PLC actually exists.
- Recipes can only be saved for the duration of the simulation.
- Time and date on the PC cannot be changed.
- The display of symbols (moving and static) only occurs "correctly"
if the complete symbol is placed inside of the screen’s display
area. Symbols placed outside of the visible screen display area
are automatically moved into the screen display area.
- The Push Button mode is not simulated for switch objects (the
switch variable always remains set).
- Invalid bit combinations in a floating point variable results in a
runtime error message during the simulation.
- Due to the various existing keyboard layouts, all keys of the
operating panel are rerouted to the PC keys.
10 Lists, Codes + Interfaces
Operating Manual ProDesigner Version 04/04 157

10.1 Keyboard Codes The following keyboard terms listed in the table below must be
inputted for all properties that require the input of a key code (Key…-
Properties). Enter the text contained in the column titled "Keyboard
Term" from the table below into the dialog field. This may be done
either manually, or via a choice dialog.
158
=
Keyboard Term
(COP-Family)
0 – 9 0 – 9
MINUS -
PUNKT .
ESC ESC
DEL Backspace
ENT Enter
PGUP PgUp
PGDN PgDn
CUR_L Cursor-Left
CUR_R Cursor-Right
CUR_U Cursor-Up
CUR_D Cursor-Down
HELP Ctrl-H
PAGE Ctrl-P
S1 Shift-F1
S2 Shift-F2
S3 Shift-F3
S4 Shift-F4
S5 Shift-F5
S6 Shift-F6
S7 Shift-F7
S8 Shift-F8
S9 Shift-F9
S10 Shift-F10
S11 Ctrl-F1
S12 Ctrl-F2
S13 Ctrl-F3
S14 Ctrl-F4
S15 Ctrl-F5
S16 Ctrl-F6
S17 Ctrl-F7
S18 Ctrl-F8
S19 Ctrl-F9
S20 Ctrl-F10
S21 Alt-F1
S22 Alt-F2
Assigned to PC key during the
simulation
Operating Manual ProDesigner Version 04/04

Important
Keyboard Term
(COP-Family)
S23 Alt-F3
S24 Alt-F4
S25 Alt-F5
S26 Alt-F6
S27 Alt-F7
S28 Alt-F8
S29 Alt-F9
S30 Alt-F10
S31 Alt-A
S32 Alt-B
S33 Alt-C
S34 Alt-D
S35 Alt-E
S36 Alt-F
F1 F1
F2 F2
F3 F3
F4 F4
F5 F5
F6 F6
F7 F7
F8 F8
F9 F9
F10 F10
INP_INC
"Fiktive" key
INP_DEC
"Fiktive" key
INP_L
"Fiktive" key
INP_R
"Fiktive" key
TAB
"Fiktive" key
STAB
"Fiktive" key
Assigned to PC key during the
simulation
Ctrl-PgUp
Ctrl-PgDn
Ctrl-Home
Ctrl-End
Operating Manual ProDesigner Version 04/04 159
Tab
Shift-Tab
Not all keys are available on every operating panel. Please refer to list
contained in the panel’s operating manual for all available keys.
"Fictive" keys are foreseen for recoding via the KeyCoding object and
also for the control of special object functions.
see chapter 6.3.1

10.2 File List, Directory Structure
160
After installation the directory structure depicted above is created.
This directory structure contains all those files required by the
development system to function correctly.
README.TXT New changes and supplements.
PRODESIGNER.EXE Development system’s program file.
PRODESIGNER.GER
PRODESIGNER.ENG
PDSGN_G.INI
PDSGN_I.INI
PDSGN_K.INI
RTF_FORMAT.INI
Development system’s message files.
Development system’s parameter files.
USER.INI This file is creates when the development
system is started for the first time. This file
contains window positions, as well as a list
of all registered objects. The list is updated
regularly and is not deleted whenever the
software itself is deinstalled. This saves
your setup in case you update, install a new
version or just reinstall your software.
\PICTURES Directory: Example graphics
\SAMPLES Directory: Supplied examples (assuming
they were selected during installation).
\SAMPLE_1
Project directory for the supplied example
containing all project files and the
PROJECTNAME.VWP file.
\DEVELOP
contains all files required by the
development system
\PICTURE
contains all picture files used by the project
\RUNTIME
contains all files required by the runtime
system
\DOCS
contains all files required to create the form
and project report. (This directory is only
created if the Create Report Database
option was set in the configuration menu)
Operating Manual ProDesigner Version 04/04

Please Note
Important
Important
In order to save a complete project, or to transfer a complete
project to another system, the directory (\SAMPLE_1) together with
all its sub-directories must be copied.
Please note that all included sample projects are overwritten if you
update or re-install the program.
The sub-directories \DEVELOP, \PICTURE, \RUNTIME and \DOCS
may not be renamed or moved to a different path!
\UTILITIES Directory: Help programs used to transfer the project to a
target.
DOWN.EXE Download program for the serial
transfer of the program to the target
system.
TRANSFER.TPL Transfer control program.
\HELP Contains the development system’s help files.
\VISI Runtime system directory.
WINDOWS\
FONTS
Development system fonts.
The COP fonts installed by ProDesigner are used to display the
operating panel fonts as they appear on the development system. It is
important that you do not rename or move these files to a different
path and that you do not use these fonts in other Windows
applications.
Operating Manual ProDesigner Version 04/04 161

10.3 Files
10.3.1 All important Files sorted according to Type
D = DEVELOPMENT directory
P = PROJECT directory
R = RUNTIME directory
V = VISI directory
O = DOCS directory
162
Important
The following files are used by the development system for a project.
*. .BWM Form’s backup files D
0. .DKF Compiled process database R
0. .DTX Process database in ASCII format. D
*. .ERR Error logfiles D
VWD_RUN. .EXE ProDesigner runtime system R
COP6X8_0
COP6X8_1
COP8X10_0
COP8X10_1
.FNT Font files for the simulation
*_R
*_D
.BMP Report functions’ graphic files
* .REF Report databases of the individual forms
O
O
* .RTF Report file in RTF format O
* .CSV Report file in ASCII format for import to Excel or
Access
0
1
.FNT
.FNT
System font ProDesigner Version R
0 .INI Initialization file for the runtime system.
This file is present twice in the project: In the
Runtime and in the Visi directory.
The contents of these files are not identical.
Settings of 0.INI User Manual COP or COP-
Handy respectively.
R0 .INI Default initialization file for the runtime system.
This file is automatically copied (as 0.INI) into
the runtime directory whenever a new project is
created.
* .PKF Compiled forms (picture database) R
* .REC Recipe control files R
* .SCR Uncompressed background pictures R
* .SCX Compressed background pictures R
* .SYK Uncompressed symbol files R
Operating Manual ProDesigner Version 04/04
V
O
V
R
V

* .SYX Compressed symbol files R
* .BMP Windows bitmap format graphic files P
* .WMF Windows Meta file format graphic files P
INDEX .TXT Contains the currently used index texts. R
INDEX .TX1
.TX2
Contains the index texts of languages 1 and 2.
The selected file corresponding to the language
selected on the development system is
converted into the INDEX.TXT file whenever
the simulation is started.
* .LOG Development system’s error log files D
* .VWM Application forms. Only used by development
system
* .PTX Forms in ASCII format. Only used by the
compiler.
"PROJECT
NAME"
.DAT Image file. Contains the compiled project and is
used for the transfer procedure
* .VWP Development project file. Contains project
configuration settings.
Operating Manual ProDesigner Version 04/04 163
D
D
D
R
D

10.4 System Variables The runtime system administrates a row of internal variables that allow
the user to request or set system states. Access to these variables
occurs at the formula and condition level and can be used to control
the application. You may allocate custom variables to the system
variable processing procedure. These variables however, must
correspond to the value areas of the system variables of the type
"Word" or "Long Word".
10.4.1 Read-Only System Variables
$SEKUNDE $SECOND Contains the current Second
(0 ... 59)
164
$MINUTE $MINUTE Contains the current Minute
(0 ... 59)
$MINUTE_NEU $MINUTE_NEW Has the state "1" whenever the
Minute changes
$STUNDE $HOUR Contains the current Hour
(0 ... 23)
$STUNDE_NEU $HOUR_NEW Has the state "1" whenever the
Hour changes
$WOCHENTAG $DAYOFWEEK Contains the current weekday
(1 ... 7) 1 = Monday
$TAG $DAY Contains the current Day
(1 ... 31)
$TAG_NEU $DAY_NEW Has the state "1" whenever the
Day changes (1 Cycle )
$MONAT $MONTH Contains the current Month
(1 ... 12)
$MONAT_NEU $MONTH_NEW Has the state "1" whenever the
Month changes (1 Cycle )
$JAHR $YEAR Contains the current Year
(YYYY - 4 digits)
$JAHR_NEU $YEAR_NEW Has the state "1" whenever the
Year changes (1 Cycle )
$ZEIT $TIME Contains the current time
HHMM
$ZEIT_S $TIME_S Contains the current time
HHMMSS
(Long Word!!)
$DATUM $DATE Contains the current date
MMDD
$DATUM_J $DATE_Y Contains the current date
YYYYMMDD
(Long Word!!)
$AKTION $ACTION Time in Seconds since the last
action (a button being pressed)
occurred
$PAGE $PAGE Contains the form number of the
currently active form (as declared
Operating Manual ProDesigner Version 04/04

10.4.2 System Commands
Important
in the project administration file)
after a form change is triggered
The ProDesigner runtime system supports the user by supplying
special commands and system variables. The user can access this
level via formulas and conditions.
All commands must begin with a „@“.
@LADE @LOAD B Form number Loads the form with the
corresponding number.
The form number that must be declared under @Load can be found
in the project administration. This number is displayed directly after
the form name. View / Project Administration.
Form numbers are automatically assigned. The form with number "1"
is the first form loaded when the application is started.
If forms are deleted the number automatically change!
Operating Manual ProDesigner Version 04/04 165

10.5 Key Functions during the Simulation
10.6 System Limits Maximum number of ... per project:
166
Important
+
+
Forms 50
Objects per form 1.000
Objects in the process
database
Exits the simulation and returns to the developer
environment.
Switches between single and double screen size mode.
1.000
Index Texts Per language 0 ... 7999 index texts may be
used. However, since the memory for texts
on the operating panel is limited a further
check is made on the operating panel. Here
the limit is set to 5000 texts with a max.
memory limit of 64 KB.
Alarms A total of 100 alarms can be administrated
simultaneously.
Recipes Max. 30 different recipe control files.
Symbols 100 symbol numbers can be assigned
(0 … 99).
All info listed above is dependent on the memory size of your
operating panel.
Operating Manual ProDesigner Version 04/04

10.7 The COP-Family Fonts
The character set Windows-Latin 1 (ANSI) is used by the COP-
Handy/RTE.
The characters with the character code from 20h to FFh correspond to
this font. These are all supported by ProDesigner.
The characters with the character code from 00h to 1Fh correspond to
the IBM-DOS character set. These are only internally available to the
COP-Handy.
The font size in the COP-Handy/RTE is 6x8 Pixel.
Operating Manual ProDesigner Version 04/04 167

168
The font size in the COP Touch is 8x10 Pixel.
Operating Manual ProDesigner Version 04/04