Run Time - English Manual

Runtime Guide
2009 Sielco Sistemi Srl
Runtime Guide
by Sielco Sistemi Srl
Simple and flexible, Winlog Pro is a real time SCADA/HMI
software package for the supervision of industrial and civil
plants. An integrated development environment provides
different tools (Gate Builder, Template Builder, Code Builder)
for the easy and intuitive creation of multilanguage
applications.An extensive library of drivers and an OPC Client
interface allow communication with most electronic devices
such as PLCs, controllers, motor drives, i/o modules; special
functions can be integrated directly by the developer; standard
format of history files (DBF, CSV) and ODBC (SQL) support
ensure interface with most Windows applications (Excel,
Access, etc.). Winlog Pro makes it possible to set up a
distributed Client/Server architecture with TCP/IP protocol on
Intranet/Internet network or to create web applications
accessible from standard browsers; both fix and mobile (GSM)
telephone network can be used to communicate with remote
devices or to send SMS.
Contents
Table of Contents
Foreword
Part I Introduction
Part II Runtime
Part III Recipes
11
1 Recipe Introduction
................................................................................................................................... 11
2 Recipe Models
................................................................................................................................... 12
3 Recipes Management
................................................................................................................................... 13
Part IV Supervision
17
1 Introduction
................................................................................................................................... 17
2 Template................................................................................................................................... 17
3 Events status
................................................................................................................................... 19
4 Alarms Status
................................................................................................................................... 20
5 Gates Status
................................................................................................................................... 21
6 System status
................................................................................................................................... 22
7 Devices Status
................................................................................................................................... 24
8 Events Historical
...................................................................................................................................
DB
24
9 Alarms Historical
...................................................................................................................................
DB
25
10 Operator...................................................................................................................................
Interventions
25
11 Charts
................................................................................................................................... 25
Introduction......................................................................................................................................................... 25
Groups
......................................................................................................................................................... 26
Change of a.........................................................................................................................................................
Group
27
Time Axis ......................................................................................................................................................... 28
Aspect
......................................................................................................................................................... 28
Part V Reports
31
1 Introduction
................................................................................................................................... 31
2 How to Draw
...................................................................................................................................
up a Report
31
3 How to Show
...................................................................................................................................
a Historical Report
31
Part VI Macros
35
1 Introduction
................................................................................................................................... 35
2 Execution
...................................................................................................................................
of a macro
35
Part VII Users codes
37
1 Introduction
................................................................................................................................... 37
Runtime Guide
2 Insertion...................................................................................................................................
of the Access Code
37
3 Definition...................................................................................................................................
of the Operators Codes
37
4 Definition...................................................................................................................................
of Names and Groups
38
5 Definition...................................................................................................................................
of the Access rights to Pages
39
41
Part VIII Windows Management
1 Introduction
................................................................................................................................... 41
2 Management
................................................................................................................................... 41
43
Part IX Multilanguage
1 Introduction
................................................................................................................................... 43
2 Building ...................................................................................................................................
multilanguage apps
43
3 Adding a...................................................................................................................................
new language
44
4 Changing...................................................................................................................................
Language at runtime
45
47
Index
Part
Runtime Guide
Introduction
The RunTime section allows the control and supervision of a project. To execute a project you can
call up directly RunTime (in this way the default project will be executed) or select the item
Execute of a project from Project Manager.
Part
II
Runtime Guide
Runtime
The figure below shows the main window with all its parts. At the top there is the title of the project
(application) during the supervision phase. The main menu allows you to access all the RunTime
parts; there are two ways to access the menus while you are working: by selecting with a click of
the mouse the single items, or with the ALT key in combination with the underlined letter of the
menu.
The quickstart buttons allow to access directly the desired pages with a simple click. The meaning
of the icons is the following:
printer setup: allows to specify the printer to use
print: print the page currently shown
recipe: opens the page for the recipe management
system status: shows the system status
device status: shows the devices status
gate status: shows the gates status
alarms status: shows the status of the alarms
events status: shows the status of the events
Runtime
historical alarms: shows the page with the history of the alarms
historical events: shows the page with the history of the events
user changes: shows the page with the operations done by users
chart: shows the page for the chart management
multilanguage: allows to change the language of the application
make report: allows to create a report
view report: allows to open a report
password: allows to change user
A red exclamation mark beside the icon indicates an anomaly.

The alarms bar shows the message of the last activated alarm. To eliminate these messages you
have to confirm active or awaiting confirmation alarms, by opening the corresponding window.
At the bottom right there are the present date and time, and the name of the last logged operator
(present operator). All the operations involving some changes in the status of the supervised
process, will be recorded with this name.
The middle part (dark grey) contains windows that the operator calls up from the menu. RunTime
allows to open as many as 8 windows simultaneously. All the open pages are continuously
updated according to the present status of the plant, so, at all times, the present situation is
displayed.
Part
III
Recipes
Recipes
3.1
Recipe Introduction
11
One of the main functions of RunTime is the recipes management.

The recipes are a set of process variables (Gates); therefore they can represent a type of
production or a particular configuration of the supervised process.
The first step to build a recipe is the creation of a Model. It represents all the variables necessary
for the recipe.
Once you have defined the models needed to manage the process, you can create various
recipes for each model, so as to have different types of process functioning.
Select the item Recipe Managment... under the Recipe menu to see the window above.
In this window you can see recipe models (the yellow folders in the left side), recipes of the
selected model (cyan icons in the right side) and a search bar on the upside.
Under menus there are common operations (creation, deletion, copy, etc...) that can be applyed to
recipe models and to recipes too; these operations, except creation, can be indiferrently applyed
to models or recipes, the actions is performed on the currently selected (blued) recipe or model.
12
Runtime Guide
The same actions are available if some elements are selected and then the right button of the
mouse is pressed.
The double click of the left mouse button over an element (model or recipe) is another way to
edit the element.
3.2
Recipe Models
A model is a set of system variables (called Gates) organized in groups. In the upper part of the
window it is possible to browse the various gates defined in the running project. A gate can be
searched by its name or by its description using the buttons in the upper part of the window. Once
the desired gate is selected, you can add it to the recipe model simply pressing the Add gate
button: the gate will be added into the group of gates shown at the bottom of the window.
It is possible to organize the gates of a recipe model in different groups. Putting in the same group
the gates that are in some way correlated, the compilation of the recipe with the desired values
will be easier.
It is possible to assign a description to the recipe model using the Comment button. Using the
Warning button you can see any eventual message that informs you about problems in the
composition of the model.
Recipes
13
The OK button allows to exit the window saving the changes made; the Cancel button closes the
window without saving changes.
A model name can be maximum 255 characters and cannot contain special characters such as: \
* : . , ; + etc.
3.3
Recipes Management
Once a recipe model is created, it is possible to generate from this all the desired recipes. To
perform the operations on the recipes press the button Recipe or press the right mouse button
over the name of a recipe. There are several options.
14
Runtime Guide
There are many ways to do the same thing in the recipe manager.
The possbility to create a recipe is available under the file menu and also in the popup menu
shown when right mouse button is clicked in the right area (the one that contains recipes).
In this way, a default name (new recipe) recipe is created and its name can be immediately
changed.
The structure of the recipe created is inherited from the parent model and cannot be modifed.
In the example in figure above the parent model of the New recipe is Produzione.
Before the creation of a new recipe it is always necessary to select a parent model to inherit from.
After the creation of the new recipe, it can be edited by the double click of the left mouse button or
the edit item of file menu (recipe must be selected); the edit choice is also available in the popup
menu that appears after the right click of right mouse button.
The only editable features of a recipe are the values (values can be imported or manually edited)
and the text description.
Recipes
15
The recipe edit window is very similar to the model one, it differs in the denied possibility of modify
the structure (gates and groups) and the availability of buttons to import or export recipe values.
Gates values (fourth column) can be manually inserted in a wise way, double click the fourth
column cell to edit the value contained.
As it is shown in figure above, after the double click, value contained in the cell will be edited.
Description column is another column that can be edited in the same way of the values one.
A window is shown during the importation (exportation too) of a recipe, it shows the live
importation gate by gate. It is possible to stop the operation with the stop button.
Part
IV
Supervision
Supervision
4.1
Introduction
17
The supervision section allows to monitor the present status of the process, change some of its
variables and analyse its historical data.
4.2
Template
It is possible to call up the configured supervision pages by selecting, from the menu Supervision |
Template, the corresponding Template. Every object on the page is updated in real time. All of
them have a contextual menu called up selecting the object with the mouse right button. This
menu varies according to the type of object it is referring to. For more details see Template
Builder.
Labels
They can represent a static text (a title or an indication) or the value of a variable (e.g. Gate TR1).
The contextual menu allows to visualize the properties of the object, or, if the label refers to a
variable, to access the dialog box showing the present status of the gate.
Images
Usually they indicate the functioning status of the corresponding parts of the template (e.g.:
normal functioning, stopped, anomaly); they are represented by bitmaps or metafiles. Every
image, can have a certain number of states and to each of them is associated a different image.
Moreover, if planned, it is possible to access the higher level Templates with a click or double
click.
The contextual menu allows to show the properties of the object or to open the expected
Templates.
Buttons
They can have different functions depending on their configuration:
They open a Template
They execute a function
They stop the execution of a function
They Apply a series of changes in the present status without closing the Template
They undo a series of changes carried out closing the Template
They apply a series of modifications carried out closing the Template
Standard Controls
The Templates can also have Windows standard controls (Edit, Combobox, Checkbox, Radio
Button, Etc.). The utilization of this controls is completely intuitive (see the Windows guide for
more details). Usually, they allow the operator to modify the process status. The carried out
modification can change the value of a gate:
1.
gate
Directly, the operator carries out a change whose result is immediately transferred to the
18
Runtime Guide
2.
On confirmation, the result of the change is transferred to the gate only if the command
Apply or OK is used (see Buttons)
Examples
As first example here is a template of an extruder.
The Template contains:
Images indicating the functioning status of the corresponding parts (normal functioning,
stopped, anomaly). The contextual menu allows to show the properties of the objects or to
open the accessible Templates, anyway they can be opened with a click or a double click (if it
is possible).
Labels showing the value of a variable (e.g. 100 C, value of the gate TR1). The contextual
menu allows to show the properties of the object, or, if the label refers to a variable, to access
a dialog box showing the present status of the gate.
Two keys (Zones Status, Startup Sequence) that, if pressed, open the corresponding
Template.
The second example shows a configuration page of the R1-50 device.

In this case all the controls have been configured so as to affect changes to the value of the gates
only if the operator press the Apply or the OK button.
Supervision
4.3
19
Events status
This page shows the list of the active events, to be confirmed or excluded.
The presence of active events is indicated by a red exclamation mark on the status icon of the
events on the bottom left of the screen (
status, shown in figure below.
) that, if pressed, opens directly the page of the events
Each row of the list represents an event; the columns have the following meaning:
1.
Active: an X indicates that the event is still active
2.
Conf.: an X indicates that the event has been confirmed by the operator
3.
Message: shows the message defined by the event
4.
Date and Time: relating to the event activation
5.
Class 1 and 2: defined by the event
6.
Acknowledge: an X indicates if the event needs to be confirmed in order to be removed

from the list
7.
Excluded: an X indicates if the event has been excluded by the operator. The excluded
events remain in the list until they are enabled. This characteristic is lost when you exit the
present session of RunTime. Each row has a color:
1.
Red: the event is still active
2.
Blue: the event is no longer active but confirmation is needed
Black: the event has been excluded
20
Runtime Guide
Sort
Press this button to show the window in figure below. In it, you can choose a criterion determining
how to sort the events list.
The possible criteria are: Date & Time, Class 1, Class 2 and Message
Confirmation
To confirm an event you just need to select it and press the Ack button or, more simply, double
click on the corresponding row.
4.4
Alarms Status
This page is the same as the events one.
The presence of active alarms is indicated by a red exclamation mark on the status icon of the
alarms on the bottom left ( ). Moreover, the messages of the active or not confirmed alarms, are
highlighted by a red line at the bottom.
Supervision
4.5
21
Gates Status
By selecting this item it is possible to show the status of the gates. It will be shown the window in
figure.
The dialog box allows to select: the type of gates to show, the channel and the device. The
sampling status is indicated by the icon OK or KO beside every gate. To have more details on the
status and properties of every single gate you just need to select the corresponding row and
press the Gate Property button or double click on the row of the gate: it will be shown the window
in next figure.
22
Runtime Guide
The presence of some anomalies is indicated by a red exclamation mark on the status icon of the
gates on the bottom left (
4.6
).
System status
Supervision
23
In this window are shown some general information about the application; more in details:
Station - Name : name associated to the computer.
Station IP address: IP address associated to the computer.
Common status - Address : if it is KO means that there is almost a numeric,digital or string

sampled gate with a wrong address (not congruent with the communication protocol selected).
Common status - Total : total number of numeric,digital,string,event or compound gates.
Common status - Sampled : total number of numeric,digital,string sampled gates.
Licence - Type : Name of the software licence

Licence - Validity : if it is KO means that the application it is not enabled to run with the current
licence type.
Total sampled gates : total number sampled gates in the application.
Total devices: total number of devices in the application.
Channel - Protocol : show the configuration parameters of the communication protocol selected.
Channel - Gates sampling : if it is KO means that no sampling is active on that channel. it can
be due to the fact that there are some sampled gates with wrong address, or the application it is
not congruent with the current licence type.
Channel - Channel status : if it is KO means that communication channel it it not opened.
Usually it is due to the fact that the hardware is not ready or is already in use from another
application.
Channel - Writing errors : number of writing errors on the selected channel.

Channel - Reading errors: number of reading errors on the selected channel.
Channel - Detail : additional details about errors (available only for particulars protocols).
Channel - Reset: reset writing and reading errors on the selected channel.
Historical files - Numeric gates : if it is KO means that can't open the numeric gates historical
file.
Historical files - Digital gates : if it is KO means that can't open the digital gates historical file.
Historical files - String gates : if it is KO means that can't open the string gates historical file.
Historical files - Event gates : if it is KO means that can't open the event gates historical file.
Historical files - User changes : if it is KO means that can't open the user changes historical file.
Historical files - Disk space
: if it is KO means that is active the Disk full alarm.
The presence of some anomalies is indicated by a red exclamation mark on the System status
icon on the bottom left (
).
24
4.7
Runtime Guide
Devices Status
RunTime allows to show the communication status of every device, in fact, any writing or reading
errors by everyone of them are shown. When the device is not answering any demand, its status
is considered KO and the corresponding row will be displayed in red. It is also possible to reset
any errors.
The presence of some anomalies is indicated by a red exclamation mark on the status icon of the
devices on the bottom left (
4.8
).
Events Historical DB
It is possible to trace back the historical situation of the events recorded on DB. In figure it is
shown the window that appears if you press the key for the events history.
By pressing the Config button it is possible to set the time range window, defining the start date
and time, along with the required time interval.
Supervision
4.9
25
Alarms Historical DB
This page is the same as the events one.
4.10
Operator Interventions
Every operation carried out by the operator is recorded on a historical DB.
The dialog box in figure shows the type of recorded operation (Code), the name of the operator,
the date and time, and a message describing the carried out operation. By pressing the Config
button it is possible to define the time range window.
4.11
Charts
4.11.1 Introduction
They are used to show graphically the trends of the gates values. The display is both historical
and realtime, and it can also be simultaneous (there is no distinction between the two modes; it
depends only on the time range used).
26
Runtime Guide
The legend on the top left, shows the color and the name of the gate of each trend. By double
clicking on the legend it is possible to modify the current group (N.B.: this change is not saved). At
the chart sides it is possible to display any two scales simultaneously. The position of the mouse
pointer is shown in the window on the bottom left. It is possible to enlarge part of the diagram by
pressing continuously the mouse left button and moving the pointer so as to define the Zoom
area; the pointer can even exit the chart area and so display hidden parts of it. The Reset Zoom
button allows to go back to the initial scale. The buttons <<, <, >, >> at the bottom allow to move
the times axis.
4.11.2 Groups
It is possible to show groups of gates (numerical, digital and composed even in the same group)
with a maximum of ten variables per group; for every gate of the group a color and a scale can be
defined. Every group can be registered with a long name (max 255 characters) so that it is
possible to call it up later on.
Supervision
27
The red icon indicates the current group, that is to say the one that is shown.
4.11.3 Change of a Group

The dialog box for modifying a group (shown in next figure), allows to add or remove the gates,
choose the trend color and the minimum and maximum values of the vertical axis, and make the
group the current one.
To simplify the choice of the gates it is possible to show a window that list and describe them.
The display changes depending on the type of gate, on the channel and the device to which it
belongs.
28
Runtime Guide
4.11.4 Time Axis

Through the window in figure, it is possible to indicate the start date and time, and the time
interval (minimum 6 seconds) that will form the times axis in the chart.
4.11.5 Aspect
Through the window in figure, you can display a grid, highlight the sampled dots, change the
thickness of the stroke and the type of interpolation between sampled dots:
None: only the sampled dots are shown
Stair: the dots are connected by a vertical and a horizontal line
Point to point: the dots are connected by an oblique line
Combined: the dots are connected by one or more lines, bearing in mind the sampling time of the
gate.
Supervision
29
Part
Reports
Reports
5.1
Introduction
31
RunTime allows to draw up, display and print reports configured with Project Manager. Every time
there is a need for a new report, RunTime interprets the basic file and creates a new file
containing the assessment of all the expressions in the report.
5.2
How to Draw up a Report

The operator can create a report whenever he wants by simply selecting his name and pressing
the Ok button.
RunTime, according to the current status, creates a new file, displays it and automatically prints it,
if the configuration contemplates for this.
5.3
How to Show a Historical Report

Every type of report can have a certain number of historical files defined in the configuration
(See: Project Manager). It is possible to save particular reports in order to keep them, avoiding the
overwriting from new generated reports.
There are two possible windows to show generated reports:
32
Runtime Guide
In this first type, reports are organized in a table where for each report is specified its name, the
creation time and the type of report.
In this second type, reports are organized in a three window that shows report type (on the left)
and a table where for each report is specified its name and the creation time.
To simplify the search, it is possible to sort the table according to one of the properties of a report:
just click on the corresponding column header. Name and type sorting are increasing, while the
time sort is decreasing, so the last created report will be in the first line.
In the first column are shown the name of the reports: the names that have an extension such as
.001, .002, are reports belonging to the circular list of the historical. When a new report is
created, this will be named with the extension .001, the others will shift of one position and the last
report (the older one) will be lost. To avoid the loss of a report with the creation of new reports, it
is possible to rename it: the report will be kept also when the report list is full. To rename a report
just select it and use the button. By pressing the Delete button it is possible to delete the desired
reports.
By pressing the Report button, will be shown the selected report.
Reports
33
Using the button Template, the template with the name equal to the type of the report selected in
the table will be shown (if exists). If the report has in the first two lines a date and time of start and
a date and time of end (e.g. to be meant as a start and end of a production lot), just before the
template opens, automatically, will be called up the functions ChartSetTimeRange and
HistViewSetTimeRange (see). Doing so it is possible to show in the template the graph variables
and the alarms' historical both related to the temporal window defined in the report.
The format of the date and time of start and end of the report is (they must be in the first two lines
of the report):
gg/mm/aaaa hh:mm:ss
date and time of start
gg/mm/aaaa hh:mm:ss
date and time of end
For the two lines, after the specification of the seconds, it is possible to write whatever you like,
e.g.:
15/02/2000 08:42:10
Start lot
15/02/2000 10:12:22
End lot
To easily write dates and times, it is possible to use the function ReportLotTime (see).
Part
VI
Macros
Macros
6.1
Introduction
35
A macro is a special command defined by a language function. They can be used, for example, to
simplify or speed up long or complex procedures.
As an example here is a macro allowing to create and import a new production recipe. When the
operator selects the macro, he will simply have to insert a name and press OK.
The macro code is the following:

Function Void New_Recipe()
#Macro
String name = InputDialog("Insert the Name ","Create Recipe","");
if (name!="") then
if (RecipeCreate("Production Recipes",name,true)) then
RecipeImport("Production Recipes",name,true);
end
end
End
6.2
Execution of a macro
If in the project code there are functions defined by the directive #Macro, then their name is in the
menu. To execute the macros you just need to select the corresponding item; you can't execute
the same macro simultaneously. For more details on the creation of macros refer to the
documentation concerning the language.
Part
VII
Users codes
Users codes
7.1
Introduction
37
RunTime allows to limit the access and the changes in the pages to the authorized operators only,
thanks to its own protection system. In fact, it's possible to associate with each operator a name, a
password, and give to him a certain set of authorizations (groups); so you can define the groups
that can access and modify the RunTime pages.
7.2
Insertion of the Access Code

By selecting the item Insertion... from the Password menu you can insert the user's name and his
password. This way all the rights concerning the use of supervisor software will be available.
To reset the authorizations (operator Nobody) you just need to access the insertion page and
press the button OK without inserting any user's name or password.
7.3
Definition of the Operators Codes

It is possible to define an unlimited number of operators, all identified by a password and some
groups. To do this, use the dialog box in figure. You just need to insert in the corresponding
fields: the name of the operator, his personal password, and, by pressing the Groups button,
select the groups to which he belongs.
Once you have entered these data, press the Add button and the operator will be registered as a
RunTime operator. As far as the name and the password are concerned, there's no difference
between capitals and small letters ("Smith" is equivalent to "SMITH"), moreover, the same name
can be associated with only one operator.
On the left part of the window there are all the registered operators. It is possible to delete an
operator by selecting his name and pressing the Remove button.
To modify the properties of an operator you have to double click on his name; at this point you can
modify his properties on the left part of the window. To confirm the changes press the Add button
so as to be able to overwrite the old properties.
38
7.4
Runtime Guide
Definition of Names and Groups

Using the dialog box in figure you can personalize the groups by giving them some names
(maximum12 characters). This way their management will be easier and more intuitive.
For example, it is possible to give the groups a geographic or functional meaning of the
supervised process, indicate whether the various operators can or cannot access only the parts
they are skilled in, award the groups a professional figure such as: Engineer, Technologist,
Operator etc., each of them with different change and access rights.
Press the OK button to save your choices; Cancel, on the contrary, closes the dialog box without
updating it with the changes.
Users codes
7.5
39
Definition of the Access rights to Pages

With the window in figure you can give the various groups the opportunity to access and/or
modify the RunTime pages.
On the left part of the screen there are the menu items corresponding to the RunTime pages. If
you select an item, on the right of the screen the change and access groups, authorized or not,
will appear. If on the page there aren't any selected groups, everybody can access or change it..
To close the window and save the changes press the OK button. If you don't want to save the
changes, press Cancel.
Part
VIII
Windows Management
Windows Management
8.1
Introduction
41
In RunTime phase it is possible to open as many as eight different windows at a time. Each
window can be maximized, minimized and closed like any other Windows window. The pages with
information on the status of the supervised process are updated in real time.
8.2
Management
You can arrange the windows automatically using the commands in the Window menu. This menu
contains also the list of all the open windows so as to make their activation easier (e.g. windows in
the background that can't be seen).
Cascade
It arranges the windows one on top of another with a certain offset starting from the upper left
side; this allows to see the titles of all the windows open at that moment.
Tile
It arranges the windows one beside another resizing them, if possible, suitably.
Arrange Icons
It neatly arranges all the icons of the minimized windows on the bottom left.
Part
IX
Multilanguage
Multilanguage
9.1
Introduction
43
MLEditor help you in developing multi language applictions.
You can also develop mono language applications, and so you don't need to use it.
9.2
Building multilanguage apps

To develop a multilanguage application follow these steps:
Create the application with Template Builder

Execute the application and be sure to have seen (shown) all the templates created in the previous
step
Update the multilanguage database using the Multi Language Editor (MLEditor).
It's very important to show templates at run time (step 2) so languages database is correctly
made,
after db creation you can edit it with MLEditor.
Strings used to build database are:
application name,
tamplate captions,
template object descriptions,
some object labels (label, button, groupbox, checkbox, radiobutton, tabsheet,combobox)
gates descriptions,
event and alarm messages.
Each time the application is executed the language database is updated, new strings that haven't
been found in the
44
Runtime Guide
db are inserted.
Strings comparison is case sensitive, it means that db can contain both 'Gate' and 'GATE'
If you change an application it's necessary to execute the app. before handling multi language
stuffs.
<NOT-FOUND> is the string apperaing when you change the current language of the application
and a label isn't found in the database, so its translation is <NOT-FOUND>
This can happen when you add a new template component (containing a label for example), you
execute the application and change its language.
9.3
Adding a new language

When language database is created (see Building ml apps) the first column is the source
language (defined as language0), the language you write your application, then another column is
added for a secondary language (defined as language1)
Each column is a language and rows are words of the language.

It's really important that language of the built application is in the first column.
Yellow cells contain language's names, names that are shown at Runtime when you choose to
change current application language.
Multilanguage
45
Once you change first cell of first column, multilanguage will be available at execution time.
Clicking on the first cell show you a dialog that let you modify the cell content.
Only changing Language0 (first cell first column) with another string will activate the
multilanguage feature .
9.4
Changing Language at runtime

After the creation, the visualization of templates built and manipulation of db of languages, the
multi language feature will be available at run time.
Under menu Supervision there is the item Language...
If application is correctly configured the next dialog will appear:
46
Runtime Guide
By this you can change the current language of the application through choices available.
If you haven't configured or wrongly configured the multilanguage stuffs, you won't change
application language and
a messagebox will advise you of this circumstance.
Index
Index
-RRecipe Introduction 11
Recipe Management 13
Recipe Models 12
Reports How to Draw up 31
Reports How to Show a Historical Report
Reports Introduction 31
-AAlarms Historical DB
Alarms Status 20
25
-C-
31
-S-
Charts Aspect 28
Charts Change of a Group
Charts Groups 26
Charts Introduction 25
Supervicion System status 22

Supervision Alarms Historical DB 25
Supervision Alarms Status 20
Supervision Charts Aspect 28
Supervision Charts Change of a Group 27
Supervision Charts Groups 26
Supervision Charts Introduction 25
Supervision Charts Time Axis 28
Supervision Devices Status 24
Supervision Events Historical DB 24
Supervision Gates Status 21
Supervision Introduction 17
Supervision Operator Interventions 25
Supervision Template 17
System status 22
27
-DDevices Status
24
-EEvent Status 19
Events Historical DB
24
-GGates Status
-T-
21
-IIntroduction
47
Template
Time Axis
6
-U-
-MMacros Execution 35
Macros Introduction 35
Multilanguage Adding a new language 44
Multilanguage Building apps 43
Multilanguage Changing language at runtime
Multilanguage Introduction 43
-OOperator Interventions
17
28
25
45
Users codes Introduction 37

User's codes Definition of Names and Groups 38
User's codes Definition of the Access rights to Pages
39
User's codes Definition of the Operators Codes 37
User's codes Insertion of the Access Code 37
-WWindow Management Handling 41

Window Managment Introduction 41
48
Runtime Guide
Endnotes 2... (after index)

Run Time - English Manual

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Run Time - English Manual

Încărcat de

Drepturi de autor:

Formate disponibile

Runtime Guide

2009 Sielco Sistemi Srl

Part III Recipes

Part VII Users codes

2009 Sielco Sistemi Srl

Part VIII Windows Management

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

A red exclamation mark beside the icon indicates an anomaly.

2009 Sielco Sistemi Srl

One of the main functions of RunTime is the recipes management.

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

They open a Template

They execute a function

They stop the execution of a function

They undo a series of changes carried out closing the Template

They apply a series of modifications carried out closing the Template

2009 Sielco Sistemi Srl

The Template contains:

The second example shows a configuration page of the R1-50 device.

2009 Sielco Sistemi Srl

) that, if pressed, opens directly the page of the events

Active: an X indicates that the event is still active

Message: shows the message defined by the event

Date and Time: relating to the event activation

Class 1 and 2: defined by the event

Acknowledge: an X indicates if the event needs to be confirmed in order to be removed

Red: the event is still active

Blue: the event is no longer active but confirmation is needed

Black: the event has been excluded

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

Common status - Address : if it is KO means that there is almost a numeric,digital or string

Licence - Type : Name of the software licence

Channel - Writing errors : number of writing errors on the selected channel.

: if it is KO means that is active the Disk full alarm.

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

4.11.3 Change of a Group

2009 Sielco Sistemi Srl

4.11.4 Time Axis

None: only the sampled dots are shown

Stair: the dots are connected by a vertical and a horizontal line

Point to point: the dots are connected by an oblique line

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

How to Draw up a Report

How to Show a Historical Report

There are two possible windows to show generated reports:

2009 Sielco Sistemi Srl

2009 Sielco Sistemi Srl

date and time of start

date and time of end

2009 Sielco Sistemi Srl

The macro code is the following: