__DocumentTitlePage
pwr_logga.gif
Operator's Guide
__DocumentInfoPage
Copyright 2009 SSAB Oxelösund AB
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts.
printdisable
index
Operators Guide
pwr_logga.gif
Operators Guide
Introduction
printenable
opg_introduction
Introduction
Proview Operator's Guide is intended for persons who will be in contact with running
Proview systems in their daily work. It could be
- operators that supervise and handle a process.
- maintenance personnel troubleshooting the plant.
- process engineer fetching information about the process.
- system managers maintaining and debugging the system.
Function for all these groups are available in the ordinary operator environment, and who
belongs to a certain group are determined from the privileges the user is granted.
opg_proview
About Proview
What is Proview
Proview is a modern, powerful and general process control system. It contains all the
functions normally required for successful sequential control, adjustment, data
acquisition, communication, supervision, HMI/SCADA, history data storage etc.
Proview is a distributed system, it consists of a number of computers (nodes) connected
in a network. The nodes can be of type process station, operator station or storage
station.
printdisable
Stations Objects printenable
opg_stations
Stations
Process stations
A process station collects measuring data from different sensors and switches, it can be
analog measuring data as temperatures, flows, levels, or digital measuring data from
for example photocells or pressure switches. A control program is executed in the process
station, that from the measuring data calculates control data for the process that is sent
out to motors and actuators affecting the process.
Process stations often contains special hardware to read input data and write output data,
but this can also be performed over the network with protocols as Modbus/TCP and Profinet.
Operator station
The operator station is the interface between the operator and the process. The operator
supervises the process with the help of process graphs, displaying the state of the process
by presenting data in the shape of bars, curves, indicators etc. The operator can influence
the process, for example by entering data into input fields or pushing buttons in the process
graph.
Storage station
Some measuring data has to be stored, in order to view trends and changes, or to be able
to get back and analyze the state of the process at a certain point of time. The storage
time can vary from hours to several years. The storage is done on storage stations, that
have sufficient disk space to be able to store data for long periods, and also have backup
functions.
Development station
There can also be development stations on the network, where process, operator and storage
stations are configured and programmed. On the development stations there are tools to draw
process graphs, program sequences, logical schemas, control loops etc. When the
configuration is modified for a station, the new configuration is distributed to the station
via the network.
opg_fig1.png
Fig Components in a Proview system
opg_object
Objects
The object tree
Object is a central concept in Proview. Sensors, valves, motors, controllers etc. are all
represented by objects in a database. The objects are ordered in a tree structure where
different hierarchy levels in the tree represent parts of the plant or process. If we look
at a furnace, the top level can represent the whole furnace. The furnace consists of four
warming zones, which are represented by objects on the next level in the object tree. Each
zone has two electric heaters and two temperature sensors, still one level down. Here are
also some object that don't have any physical equivalent in the plant, a PID controller
and a control program for the zone.
opg_fig2.png
Fig Furnace with 4 zones
opg_fig3.png
Fig Object tree for the furnace
Note that several objects have quite cryptic names that follow a notation standard, but to
each object there are a more detailed description that is often viewed with the object.
Let us have a closer look at an object, for example one of the temperature sensors. The
object is shown in an overview process graph with the graphical symbol of the object, a
triangle with the letter T.
opg_fig4.png
Fig Graphical symbol for a temperature sensor
Object graph
If you click on the symbol the object graph of the object is opened. From the object graph
you can see the properties of the object. The most interesting for a temperature sensor is
of course the measured temperature, that is viewed both in figures and as a bar
(thermometer), see 'Fig Object graph for temperature sensor' below. The temperature sensor
object also contains four alarm limits, highhigh, high, low and lowlow. The level of the
alarm limits can be set from the graph, and also a hysteresis on the limits. With check
boxes you can also disable the alarm limits.
opg_fig5.png
Fig Object graph for a temperature sensor
Methods
In the upper edge of the object graph there are a number of pushbuttons that activate the
methods of the object. By the methods you can reach all the information there is on the
objects in the control system. The methods can also be activated from the menu in the
objects graph, or by right clicking on the graphical symbol in the overview graph, opening a
popup menu with the methods. Actually, wherever you find the object, in alarm lists,
process graphs, in the plc code etc, you can by right clicking on the object open the popup
menu with the methods or the object. Here follows a list of different methods, but which
methods are relevant for a specific object, depends on the type of object and how it is
configured.
Method Description
Object Graph Open the object graph.
Trend Open a trend curve.
History Fetch history data from a storage station and view in a curve.
Hist Event View a historical list of alarms and events for the object.
Block Events Block alarms and events.
Help View a help text for the object.
Note Write a note for the object. The note is viewed in the object graph.
Open Object Show the content of the object.
RtNavigator Show the object in the object tree.
Crossreferences Show were the object is referenced in the plc code and process graphs.
Help Class View help for this object type.
Datasheet Show the datasheet for the component in the plant that corresponds
to the object.
CircuitDiagram Show the circuit diagram for the object.
opg_opplace
Operator place
printdisable
Start the operator environment Operator window printenable
opg_startop
Start the operator environment
Usually the operator environment will be started automatically at login of the workstation.
In the login configuration, a operator place object is added to the starting command. In
the operator place object the properties of the operator place are configured.
At times though, you may want to start another way, for example from a terminal window.
The operator environment is started by the program rt_xtt, and you specify an OpPlace object
as argument. The command to start with the OpPlace object Nodes-OpgNode-b55 is
> rt_xtt Nodes-OpgNode-b55
There are also a number of options that can be added to the argument list
-l Language. One the following languages is specified:
en_us English (default).
sv_se Swedish.
de_de German.
fr_fr French.
-q The license window is not opened at startup.
-c A pushbutton to close the operator environment is shown in the operator window.
-u Start with a opplace object with the same name as the current linux user.
-s Displays a list of available OpPlace objects.
opg_opwindow
The Operator Window
opg_fig6.png
Fig The operator window
The operator window is placed at the upper edge of the screen, and lacks title row and
pushbuttons to iconify and delete the window. It is divided in tree parts, to the left
current alarms and messages are viewed, in the middle there are pushbuttons for some base
functions, and to the left there are pushbuttons configured for this operator place.
Status bar
The top row is a status bar. It shows who is logged in on which node. For tha current
node, and for all nodes that there are node supervision configured, an indicator for system
status is viewed. Green states that everything is all right, yellow indicates warning, red
error and flashing red fatal error. If you click on a node, the status graph for the node
is opened.
Alarms and messages
In the left part of the operator window alarm and messages are displayed.
The alarms are divided into four priority levels A, B, C and D, where A has the highest
priority and D the lowest. A alarms are marked red, B alarms yellow, C alarms blue and D
alarms violet. Furthermore there is the category Info messages that are marked with green.
In the upper field, the latest unacknowledged A alarm are displayed. Depending on the height
of the operator window, 2 to 5 alarms are viewed. There is also a button marked with a tick
to acknowledge A alarms.
In the lower field the latest unacknowledged B, C, D alarms, and info messages are viewed.
These alarms are displayed in priority order rather than in chronological order, i.e. if
there are unacknowledged B alarms, the latest of these will be displayed. Only if there are
no acknowledged B alarms, possible C alarms are viewed etc. There is also an acknowledge
button to acknowledge the B, C, D alarms and the info messaged.
An alarm is prevailing if the alarm condition still is fulfilled. This is marked with a
warning triangle to the left of the alarm text.
Menu and pushbuttons to open base functions
In the middle part of the operator window there are a menu and some buttons to open
base functions.
Menu
Below is a description of the menu items in the Functions menu.
Functions/Alarm/AlarmList Open the alarm list with prevailing and unacknowledged alarms. Open the event list, a list of the latest alarms and events. Open the event log, where you can display stored events. Open the list of blocked alarms. Display a list of all trendcurves. Display a list of all fastcurves. Display a list of process history. Display a list of all process graphs, defined by
XttGraph objects.
Functions/Navigator Open the navigator. Increase the text size in the alarmtext.
Functions/View/Zoom outDecrease the text size in the alarmtext.
Functions/User/Switch User Open the login window to login as another user.
Functions/User/Show User Show the current user.
Functions/User/Return Return to the original user.
Functions/Help/Project Show helptexts for the project.
Functions/Help/Overview Show an overview of helptexts.
Functions/Help/Operator Window Display help on the operator window.
Functions/Help/About Proview Display Proview into, for example version of install package.
Functions/Close Close down the operator place.
Pushbuttons
Below the menu there is a tool panel with a number of pushbuttons that works as shortcuts to
menu items:
- zoom in and out.
- show helptexts for the project.
- close.
- show alarmlist.
- show eventlist.
- show eventlog.
- show list of blocked alarms.
- open the navigator.
Function buttons
To the right there are a number of pushbuttons that are used to open process graphs or
execute various orders or commands. How these buttons are used depends of the configuration
of the operator place.
opg_events
Alarms and Events
printdisable
About alarm and events Displays current alarms.Displays the latest alarms and events. Search for alarms and events in the event database. Displays blocked alarms and hierarchies. printenable
opg_events_general
About alarm and events
Alarms
Alarms are sent to the operator station when something occurs that operator has to pay
attention to. It could be a temperature crossing a limit, or a bad value entered in a
process graph. In Proview there are special supervision objects that supervise signals
and generates alarms.
Alarm are viewed in the alarmlist.Priority
The alarms are grouped in four priority levels, A, B, C and D, where A is the highest
priority and D the lowest. How the priority levels are used, depends on the configuration
of the system. It is common that the alarm priorities are used in the following way.
A alarms are marked with red. They have the highest priority and indicate that a serious
error in the plant has occurred that immediately should be taken care of. Often it causes
a stop in the production as long as the alarms are prevailing.
B alarms are marked with yellow. They have a little lower priority, implying an error that
that should soon be taken care of, but the production can continue still some time.
C alarms are marked with blue and D alarms with violet. They indicates minor errors that
are not acute. In many system two alarm levels are enough, and only A and B alarms are used.
Alarmtext
Alarms contain text that is viewed in alarm and event lists. This text is in one row
and maximum 80 characters long. There is also room for longer text, a moretext, that
for example, can contain further explanation of the cause of the alarm, or how it should
be taken care of. The moretext is displayed in the alarm and event lists if the cursor
is placed on the alarmtext.
Acknowledge
An alarm has to be acknowledged by the operator. As long as the alarm is unacknowledged, it
remains in the alarmlist and gives rise to a beep. If an alarm is displayed at several
operator places it is enough for one of the operators to acknowledges the alarm.
Blocking
If an alarm is not relevant during a period, it is possible to block the alarm. You can,
for example, block the alarms for a part of the plant that is not in production. The
blocking can be performed on a separate alarm object, or for a hierarchy. Blocking is a
method of an object, and performed from a blocking window that is opened from the popup
menu for the object. Only users that are granted the privilege RtEvents are allowed
to block alarms.
Blocked objects are displayed in a blocklist. Messages
Info messages are a group that has the same functionality as alarms. They have lower
priority than alarms and are marked with green.
Events
An event is generated in the same way as alarms, by supervision objects. Also alarms
generates events. Activation of an alarm is counted as an event, as are the return
of the alarm state and the acknowledgement of the alarm.
Events are stored in an eventlist, that contains the latest events. They are also stored
in the event log, where you can go back and look at events for some period of time, and
also see event statistics. For the eventlog there is a search dialog, where you can search
for events with certain search criteria, for example time, eventtype or eventname.
Selectlist
The operator place has a selectlist that contains a list of plant parts in the object tree.
Only alarms from these plant parts will be viewed in the alarm and event lists. The other
alarms and events are filtered away.
opg_alarmlist
Alarmlist
opg_fig7.png
Fig Alarmlist
The alarmlist is opened by activating the "Alarmlist" button in the operator window. You can
also open the alarmlist from the menu in the navigator, 'Alarm/Alarm List', or by the xtt
command 'show alarmlist'.
In the alarmlist prevailing and unacknowledged alarms are viewed. Unacknowledged alarms are
marked with a bell and prevailing alarms with a warning triangle. Only alarms from the
plant parts stated in the selectlist are viewed.
The moretext of an alarm is displayed when the cursor is placed on the alarmtext.
Alarms can be acknowledged by activating Functions/Acknowledge (Ctrl+K) in the menu.
If you rightclick on an alarmtext, the methods of the alarm objects are displayed. Thus
making it easy to open the object graph or find where in the plc code the alarm is
generated.
opg_fig10.png
Fig Alarmtext
opg_eventlist
Eventlist
opg_fig8.png
Fig Eventlist
The eventlist is opened from the "Eventlist" button in the operator window. It can also be
opened from the navigator menu or by the command 'show eventlist'.
The events from the plant parts stated in the selectlist are displayed in the eventlist.
The maximum number of events are configured in the User object. When the maximum number
of events is reached, old events are removed when new ones arrives.
Each event indicates
- Color indication for alarm priority.
- Event type.
- Time of event.
- Event text.
- Event name (object/signal name).
The moretext for an event is viewed when the cursor is placed on the event text. If you
rightclick on the eventtext, the methods of the objects are displayed. Thus making it easy
to open the object graph or find where in the plc code the alarm is generated.
opg_eventlog
Eventlog
The eventlist has a limited length and displays only the latest event. All events though are
stored in a database, the eventlog. From this it is possible to look at events for a longer
period of time.
As the number of stored events often are several thousands, you search for the events you
are interested in with different search criteria. The events matching the search critiera are
diplayed in a list.
Search criteria
The event log dialog is viewed in figure 'Eventlog' below.
Time
On the upper row you can specify a time interval of the search. State requested interval
with the optionsmenu to the right. If you select 'Time' the time interval is inserted into
the input fields.
Eventtype
An eventtype is specified. If no type is selected, all types are present in the search.
- Active An alarm is activated.
- Message An info message.
- Return An alarm returns from active state.
- Ack En alarm is acknowledged.
Priority
Search for alarms with a specific priority. If no priority is selected, the search is made
for all priorities.
Eventname
Name of the object the event is connected to. Wildcard (*) is allowed, for example F1-Z1*
will search for all events in the hierarchy F1-Z1. If no object name is supplied, all
objects are searched for.
Eventtext
Search for an event text. Wildcard (*) is allowed. If no text is specified, all texts are
searched for.
When the search criteria are stated, the 'Search' pushbutton is pressed. The search is
performed and the result is presented in a list in the lower part of the window.
opg_fig9.png
Fig Eventlog
In the list of events an event is displayed with
- Priority The priority is marked with color and a letter.
- Eventtype Active is marked with an exclamation mark, Return with an crossed-out
exclamation mark and Ack with a tick.
- Eventtext
- Eventname
If you rightclick on a row the methods of the eventname object are displayed.
opg_blocklist
Blocklist
opg_fig12.png
Fig Blocklist
The list of blocked alarms is opened from the menu in the navigator, Alarm/Blocket Alarms,
or by the xtt command 'show blocklist'.
For each blocked objects are displayed:
- Color indicating the blocked priority level.
- Object name.
- User that has made the blocking.
A blocking is removed by selecting the blocking and activating Functions/Remove Blocking in
the menu.
Alarm blocking is performed by the 'Block Events' method for an object.
opg_blockingwindow
Alarm blocking
opg_fig11.png
Fig Dialog for alarm blocking
Alarm blocking is activated by the 'Block Events' method, i.e. from the popup menu for an
object, or with the xtt command 'eventlist block'.
The window is used to block alarms for an object. All alarms with the specified priority,
and with lower priorities, are blocked for the object and all its descendants.
The priority is specified by radio buttons. You can also remove blocking by the
'No Blocking' button.
Only users with the privilege 'RtEvent' or 'System' are authorized to block alarms.
opg_curves
Curves
printdisable
Trends printenable
opg_trends
Trends
Trendcurves are opened from the 'Trend' method in for example the popup menu. They can
also be opened by the Xtt command 'open trend'. Trend curves are configured by DsTrend
objects and, if several curves are viewed in the same curve window, by PlotGroup objects.
A trendcurve is a signal value, for example of type temperature, pressure or flow, that
is stored with a specific time interval. A trendcurve can store 478 values, and so the
total time window depends on the time resolution. If a new value is stored every second,
a total of 8 minutes can be stored, and with a new value every minute, eight hours can be
stored. The values are stored in the RAM memory, and will be lost at a reboot.
The trendcurves are viewed in a curve window. A curve window can display 20 different
curves.
opg_fig31.png
Fig Trendcurves
The upper part of the curve window views a table over the curves. The first column is
a color indication to identify the corresponding curve.
Description of columns in the table
View A checkbox from which you can choose to view or hide the curve.
Cursor Shows the curve value where the cursor is placed.
Mark Shows the curve value where the marker is placed.
Unit Displays the unit of the curve.
Scale From 'Scale' you can change the scale in y direction (Scale on
the Time axis row changes in x direction).
Attribute States the attribute of the trend curve.
Navigation
The tool panel contains buttons to zoom and move the view to the left or to the right.
You can also navigate with the navigation window in the lower part of the window. The part
of the curve that is displayed, is marked with a black square. With drag MB1 you kan move
the view in x direction, and by dragging the middle button you can zoom in and out.
Navigation from the keyboard is accomplished with the arrow keys. With arrow up and down
the zoom factor is changed, and arrow left and right moves the view to the left and to the
right.
opg_fastcurves
Fastcurves
Fastcurves are opened from the 'Fast' method in for example the popup menu. They can
also be opened by the Xtt command 'open fast'. Fastcurves are configured by DsFastCurve
objects and, if several curves are viewed in the same windows, by PlotGroup objects.
Fastcurves are used to display fast sequences during a shorter period of time. The
storage of the fastcurve is started by a trigger signal and continues a specific time. When
the sequence is finished the curve is viewed, and remains on the screen until the
trigger signal is set again to activate a new recording of the sequence.
The fastcurves are viewed in a curve window. A curve window can display 20 different
curves.
opg_fig37.png
Fig Fastcurve
opg_history
Process history
Process history is opened from the 'History' method in for example the popup menu. It can
also be opened by the Xtt command 'open history'. The history is configured by SevHist
objects.
Process history means that the value of a signal, for example of type temperature, pressure
or flow, is stored in a database with a specific frequency during a period of time.
The history can extend over several years and the number of values for one signal can
reach several millions.
opg_fig34.png
Fig Process history
In the upper part of the curve window views a table over the curves. The first column is
a color indication to identify the corresponding curve.
Description of columns in the table
View A checkbox from which you can choose to view or hide the curve.
Cursor Shows the curve value where the cursor is placed.
Mark Shows the curve value where the marker i placed.
Unit Displays the unit of the curve.
Scale From 'Scale' you can change the scale i y direction (Scale on
the Time axis row changes i x direction).
Attribute States the attribute of the trend curve.
Navigation
The tool panel contains buttons to zoom and move the view to the left or to the right.
You can also navigate with the navigation window in the lower part of the window. The part
of the curve that is displayed, is marked with a black square. With drag MB1 you can move
the view in x direction, and by dragging the middle button you can zoom in and out.
Navigation from the keyboard is accomplished with the arrow keys. With arrow up and down
the zoom factor is changed, and arrow left and right moves the view to the left and to the
right.
Resolution
As the number of values for an attribute can reach several millions, only a fraction of the
values are viewed in the curve. When first opening the curve, the whole time range is
viewed with a couple of hundred points. To gain higher resolution you use the arrow up
and arrow down buttons in the tool panel. Arrow up will zoom in and increase the resolution,
i.e. new values are fetched in a smaller time interval. Arrow down will zoom out and
decrease the resolution.
opg_help
Help window
Getting help
The help function can be opened in a number of different ways.
Operator window
In the middle part of the operator window there is a help button that opens the help texts
for the project.
The Navigator menu
The menu entry Help/Overview gives help on Proview and the operator environment.
Help/Project gives help on the project.
Command
A help text is opened by the Xtt command 'help'. To help you add the topic you are
interested in. The command 'help help' shows for example how you use help.
Object methods
For an object there are two help methods.
- Help, views help for the object or plant part.
- Help Class, views information about the object class.
Help and info buttons in process graphs
Pushbuttons in process graphs can be connected to helptexts. These are usually marked
with a question mark or an 'I'.
opg_fig36.png
Fig Help buttons
Navigate in the help text
Rows with links are marked with an arrow in the left edge of the row.
The first row is a link to the previous topic.
Navigate from the keyboard
With PageUp and PageDown you can scroll up and down in the text.
Links are followed by selecting the link row with the arrow up and down keys, and then
press arrow right.
Arrow left returns to the previous page.
Ctrl+N views the next topic, and Ctrl+P the previous topic. Ctrl+A returns to the start
page.
Navigate with the mouse
To follow a link, click on the arrow, or double click on the row.
By clicking on the arrow in the first row, you return to the previous page.
opg_fig35.png
Fig Help window
opg_navigator
Navigator
The navigator, also called Xtt, is started from the 'Navigator' button in the operator
window. It can also be started as a separate program, independent of the operator
environment. This is useful at maintenance or troubleshooting of the system. You then start
from a terminal window, see section 3.1.
opg_fig14.png
Fig The navigator menu
The figure above shows the navigator menu. The upper map, 'This Project' in configurable
and can contain a map structure that is specific for the project, and by default it is
missing. The other maps though are always present.
Database Shows the object tree and the objects in the database.Opens the alarm list. Opens the event list. Shows the list of blocked alarms. Shows the event log.Shows stored collection views.
System / Nethandler / Link Shows links to other Proview systems. Shows subscriptions (client). Shows subscriptions (server). Shows remote communication (nodes). Shows remote communication (transactions). Shows I/O devices. Shows Plc threads. Shows PlcPgm objects. Dialog to start logging of data. Views system messages. Views system status for the node.Shows the status graph for nodes. Shows loaded volumes. Close the navigator.
Navigate
Navigate from the keyboard
The most ergonomic way to navigate in the map structure is to use the arrow keys. With
Arrow Up and Arrow Down you select a map or a leaf. With Arrow Right you open a map and
with Arrow Left you close.
An object in the database is opened by Shift Arrow Right, i.e. you first press the Shift
button and keep it down while pressing the Arrow Right key. If the object doesn't have
any children, it is enough to press Arrow Left.
If you have the privilege RtWrite it is possible to change attribute values in the database.
By opening an object, selecting an attribute and pressing Arrow Right, an input field is
opened where a new value can be entered.
Navigate with the mouse
Of course you can also navigate with the mouse. A map is opened by clicking on the map
(or doubleclicking on the text). Then you close by clicking on the map again.
An object in the database is opened by pressing the Shift key and click on the map/leaf
for the object.
Commands
From Functions/Command in the menu, or Ctrl+B, a command prompt is opened in the bottom row
of the navigator. Here you can enter commands and execute scripts. Available commands are
described in the chapter Commands and script in the chapter Script.
printdisable
Commands printenable
Collection view
By Functions/Collect/Show, Ctrl+N, you look at collected objects and attributes. For trouble
shooting you often need to look at a number of different attributes simultaneously. By
traversing the object tree and collecting attributes with Functions/Collect/Insert, Ctrl+V,
and then activating Functions/Collect/Show these attributes are viewed on one page.
A collection view can be saved to a later session by the 'save' command. To save a collection
view with the name 'mycollection' you write the command
> save/collect mycollection
opg_fig15.png
Fig A collection view stored with the name 'mycollection'
The name can be found in the 'Store' map, and can also be restored by the command
> @mycollection
opg_nav_database
Database
opg_fig13.png
Fig The object tree from the navigator
Under the map 'Database' the object tree is shown. Here you can navigate in the object
three, open objects and examine the content of different attributes in the object. If
you have privileges, you can also change attribute values.
If you rightclick on an object, an popup menu with the object methods is opened. Buttons
to activate the methods of the objects are also found in the lower tool panel in the
navigator. Only methods that are valid for an object are sensitive.
opg_fig16.png
Fig Methods can be activated both from the tool panel and the popup menu
opg_nav_link
System / Nethandler / Link
The map 'System / Nethandler / Link' shows links to other Proview stations. The current
station is also viewed in the list.
In the figure below you can see that the local node aristotle has contact with the node
pwrutv.
opg_fig17.png
Fig Links to other nodes
Description of the columns in the table
Node Nodename
Os Operating system and hardware for the node.
Link Link status. Can be Up, Active, Connected, Down or Local.
UpCount The number of times the link is established.
TimeUp Time for the last establishment of the link.
opg_nav_subcli
System / Nethandler / Subscription Client
Shows the subscriptions the current node has to other stations.
When an operator station displays data from process stations in an process graph, a
subscription on each data viewed in the graph is created. This implies that the process
stations at regular intervals sends new data to the operator stations, which updates the
process graph with the new data.
If there is a field in a process graph that is not updated. you can enter the Subscription
Client table to see if the subscription is present and if it is updated. Each time new data
arrives for a subscription, 'Count' increments and the time is inserted in 'Time'.
In 'Unknown' on the top row, you can see the number of subscriptions where the attribute
is unknown. This can be a subscription to a station that is not yet running, but it can
also be a subscription that is misspelled, or to objects that no longer exist.
opg_fig19.png
Fig Subscription client
Description of the columns
Subid The subscription identity.
Time Latest arrival of subscription data.
Count Number of times data has been received.
Node Node sending subscription data.
Size Size in bytes of subscription data.
Attribute Database attribute for the subscription.
opg_nav_subsrv
System / Nethandler / Subscription Server
The list shows subscriptions other stations have requested from the current node, i.e.
subscription sent cyclically from the current node to other nodes, usually from process
stations to operator stations.
opg_fig18.png
Fig Subscription server
Description of the columns
Subid The subscription identity.
Count Number of times data has been sent.
Node Node to whom subscription data is sent.
Size Size in bytes of subscription data.
Offset Offset in the object from where data is fetched.
Attribute Database attribute for the subscription.
opg_nav_remnode
System / Communication / RemNode
Displays a list of nodes that the current node communicates with via Remote.
Remote is a function to send data between nodes. Nodes communicating with each other are
configured by RemNode objects, and a transaction sent between two nodes by the Remote
function are configured by RemTrans objects. A number of different protocols for the
data exchange are supported, Modbus, MQ, Serial, TCP, UDP, 3964R and ALCM.
opg_fig20.png
Fig List of RemNodes
Description of the columns
RemNode Name of the RemNode object, only the two last name segments are displayed.
Type Type of communication, Modbus, MQ, Serial, TCP, UDP, 3964R or ALCM.
Description Optional description.
By selecting a RemNode and pressing the Arrow Right key, the RemTrans objects for the
node are viewed (you can also click on the map).
By Shift/Arrow Right the RemNode object is opened.
opg_nav_remtrans
System / Communication / RemTrans
Shows a list of all RemTrans objects.
A RemTrans object specifies a transaction sent between two node by the Remote function.
The transaction implies that the current node receives or sends data.
opg_fig21.png
Fig List of RemTrans-objecs
Description of the columns
RemTrans Name of the RemTrans object, only the two last name segments are shown.
DataValid States that data that is not yet sent is present (when sending) or
that received data that has not been taken care of is present.
Direction Direction of the transaction, Snd (send) or Rcv (receive).
TransCnt Number of sent or received transactions.
TransTime Time for the last transaction.
ErrCount Number of unsuccessful transactions.
LastSts Status for the last transaction.
By selecting a transaction and pressing the Arrow Right key, the content of the transaction
is viewed (you can also click on the map). If the attribute StructFile is supplied with
the include file containing the data structures for the transactions, the data content is
viewed in this format.
By Shift/Arrow Right the RemTrans object is opened.
opg_nav_device
System / Device
Shows a list of I/O devices.
The I/O system in Proview is divided into four levels, agent, rack, card and channel.
In the device list, all the card objects are displayed.
opg_fig22.png
Fig List of I/O units
Description of the columns
Device Name of device object. Only the two last name segments are viewed.
Class Card object class.
ErrorCount Counter for read or write failures.
Process Process handling the card. 1: plc, 2 io_comm.
PlcThread Plc thread handling the card.
Address Address configured for the card.
By selecting a device and press the Arrow Right key the channels of the device are
displayed (you can also click on the leaf).
opg_nav_thread
System / PlcThread
Displays a list of threads in the plc program.
Different plc programs are running with different priority and cycletime. They are
connected to PlcThread objects that determines the priority and cycletime for the
execution.
opg_fig23.png
Fig List of plc threads.
Description of the columns
PlcThread Name of thread object.
Prio Thread priority.
LoopCnt Counter of number of cycles since Proview startup.
ScanTime Configured cycletime.
Mean Meanvalue of measured cycletime.
Coverage The execution time for the thread in proportion to the cycletime in percent.
Count 1/8 Number of cycles where the execution time is less than 1/8 of the cycle
time.
Count 1/4 Number of cycles where the execution time is less than 1/4 of the cycle
time and larger than 1/8.
Count 1/2 Number of cycles where the execution time is less than 1/2 of the cycle
time and larger than 1/4.
Count 1/1 Number of cycles where the execution time is less than the cycle
time and larger than half the cycletime.
opg_nav_plcpgm
System / PlcPgm
Displays a list of all PlcPgm objects.
A PlcPgm object contains plc code controlling a plant part, or executing other types of
calculations. The PlcPgm object is connected to a thread object specifying the priority
and cycletime.
opg_fig24.png
Fig List of PlcPgm objects
Description of the columns
PlcPgm Name of PlcPgm object.
PlcThread Plc thread the object is connected to.
Description Optional description.
PlcTrace for a PlcPgm is opened by selecting the PlcPgm object and press Ctrl+L.
Arrow Right key will display all the windows in the plc program.
opg_nav_logging
System / Logging
With the logging function it is possible to log signals and values in the database to
a text file. The content of the textfile can be viewed in a curve window, or imported
into for example Calc or Excel.
Maximum 100 attributes can be logged in one logfile, and there are 10 entries, where each
entry handles one logfile.
Start the logging
- Collect the attributes that are to be logged, into the collection view, for example by
finding and selecting the attributes in the database and press Ctrl+V.
- Check with Ctrl+N that the correct attributes are present in the collection view.
opg_fig25.png
Fig Attributes collected in the collection view
- Open Logging entry 1 (System / Logging / Logging Entry 1).
- Click on the 'Insert' button, The attributes are now transferred from the collection view
to the list of attributes in the logging entry.
- Specify cycle time in ms, and filename if needed.
- Start the logging by clicking on the 'Start' button.
opg_fig26.png
Fig Logging entry with logging started
- When the logging is complete, you click on the 'Stop' button. Note that you must not
terminate the navigator during the period of time the logging is active. Though you can
leave the loggentry page.
- Look at the logging result in the curve window by activating 'ShowFile'.
opg_fig27.png
Fig Logging viewed as a curve
There are two types of logging. Either the value of the attributes are logged continuously
with a certain frequency (continuous logging), or an attribute is logged every time its
value is changed (event triggered logging).
Continuous logging
The values of the attributes in the entry are logged every cycle. In the file, also the time
since the logging started is written. The file can be viewed in the Xtt curve window
from 'ShowFile' or imported into a spreadsheet program.
Event triggered logging
An attribute in the entry is logged if the value of the attribute is changed. Into the
logfile the time of the change, and the new value is written. This type of logging can
not be viewed from 'ShowFile'.
Buffer
The logging is first written into an intern buffer. When the buffer is full it is written
to file. At fast time critical sequences, you can increase the buffer size to avoid
interruption when the buffer i written to file.
Conditional logging
In 'Condition' a digital attribute controlling the logging can be specified. The
logging is only performed when the ConditionParameter is true.
It is also possible to insert an expression into 'Condition'. The expression starts with
'expr' followed by the condition enclosed with parenthesis. In the expression, attribute values
can be fetched with the GetA function for analog attributes, GetD function for digital
attributes and GetI function for integer attribute.
Expression example
expr( GetD("H1-H2-Dv1.ActualValue") && GetA("H1-H2-Av2.ActualValue") > 2.5)
The logging is performed when the Dv 'H1-H2-Dv1' is true and the Av 'H1-H2-Av2' is
larger than 2.5.
Store
The logging configuration is stored with the 'Store' button, and can be restored later
with the 'Restore' button.
opg_nav_systemmsg
System / System Messages
The Proview system logg contains information, warning and error messages, written by the
server processes of the system. Also applications can write to the system log by using
the errh interface.
Messages in the loggfile has different degrees of severity. The severity is marked with
a letter and color:
F red Fatal, the most serious type of error message.
E red Error.
W yellow Warning.
I green Information.
S green Success.
Also the Proview startup is marked with a yellow colored row.
Above all you should notice red messages implying something is wrong in the system.
opg_fig28.png
Fig System log
opg_nav_systemsts
System / System Status
The system status displays a list of nodes in the system, and by opening a node the
status graph for the node is shown.
The most interesting in the graph is the SystemStatus. This is an indication of the
condition of the system. If system status is green, its OK, if it is yellow or red,
something is wrong in the system.
The color markings has the same severity as in the System log above, i.e.
F flashing red Fatal.
E red Error.
W yellow Warning.
I greenInformation.
S green Success.
gray Null status. The function is not activated.
The system status is a summary status for the system and application processes. Below
system status there is a list of all these processes, and the status for each process
is displayed. Furthermore is the latest or most severe system message in the system log
from the processes are displayed.
If the system status is for example yellow, this implies that some system or application
process has a yellow status. Usually by reading the status text and look in the system log
is is possible to figure out what the error is.
rt_ini Initialization Startup process starting the system. Also handles the system log.
rt_qmon QCom monitor Handles the communication with other nodes.
rt_neth Nethandler Handles exchanged of database information between nodes.
rt_neth_acp Utility process for the nethandler.
rt_io I/O Process for I/O handling that is asynchronous with the plc program.
rt_tmon Timer monitor Handles sending of subscriptions.
rt_emon Event monitor Handles alarms and events.
rt_bck Backup process Handles backup of attributes and objects.
rt_linksup Link supervision Supervision of links to other nodes.
rt_trend Trend process Handles storing of trend curves.
rt_fast Fast process Handles storing of fast curves.
rt_elog Event log Handles event logging.
rt_webmon Web monitor Supplies the web interface with database information.
rt_webmonmh Web mh monitor Supplies the web interface with alarms and events.
rt_sysmon System monitor Supervises the system.
plc Plc process Handles I/O and executes the plc code.
rs_remote Remote process Handles remote communication.
opc_server Opc server process.
rt_statussrv Status server Webservice for the runtime monitor and supervision center.
opg_nav_volumes
System / Volumes
Displays the loaded volumes.
For each volume is viewed: name, class, version and an letter combination LCM where L
means loaded, C cached and M mounted.
opg_fig30.png
Fig Loaded volumes
opg_trace
Plc trace
Plc trace is a tool to study and debug the plc code.
Trace is opened from the method 'Open Plc', or from a crossreference in the Plc code.
You can also open trace by selecting a PlcPgm in the navigator and activate
'Functions/OpenProgram' (Ctrl+L) in the menu.
To the left there are a navigation window where the displayed area is marked with a
square. By moving the square with drag MB1 you move the displayed area. You can also
zoom by dragging with the middle button.
Digital objects with height status are marked with red in the code.
opg_fig32.png
Fig Plc Trace
You can look at the value of analog or digital outputs by creating so called analyze nodes.
They are created by dragging with the middle button from the output pin.
A set of analyze nodes can be stored and restored by 'File/Save Trace' and
'File/Restore Trace' in the menu.
When rightclicking on an object the methods of the objects are displayed. A very useful
method in this context is crossreferences, The crossreferences are also displayed when
doubleclicking on the object.
Crossreferences
The crossreferences are a list of the places an object or attribute occur in the code or
in process graphs. If the reference implies reading the value, it is marked with a book,
if it implies writing the value, it is marked with a pen. Reading can be that the value
is displayed in a graph or fetched in the plc code. A write reference can be a pushbutton
in a graph or a Set or Sto object in the plc code.
opg_fig33.png
Fig Crossreferences
By rightclicking on the crossreference, the plc or process graph the reference is pointing
at is opened. On plc references you can open PlcTrace with doubleclick. When Plc Trace is
opened the reference is marked and centered.
Debugging with Plc Trace and Crossreferences
Plc Trace and Crossreferences are a very efficient tool for troubleshooting.
A troubleshooting often starts out from an alarm or error indication in a process graph.
By activating the methods 'Crossreferences' or 'Open Plc' you find the place or places in
the code where the object is written. By analysing the code you conclude which signal
is missing, open the crossreferences for this and open PlcTrace where it is written. In
this way you can search in the code and finally find the cause of the problem.
Simulation
At simulation, i.e. when testing a system without the I/O system, you can set PlcTrace
in simulate mode with 'Mode/Simulate' in the menu. In simulate mode you can toggle
digital signals by clicking with Ctrl/Shift MB1 on them in the Plc Trace window.
opg_setupfile
Setup script
A setup script can be created on the home directory with the name
xtt_setup.rtt_com
This will be executed when the operator environment (or Xtt) is started, and can
contain script statements and xtt commands.
Here are some examples of useable commands.
Open a graph
open graph my_graph
Create a maintenance menu in the navigator
create item/text="Maintenance"/menu/destination="DataBase"/before create item/text="My graph"/command="open graph my_graph"/pixmap=graph
/dest=Maintenance/first
Remove menu items from the standarde menu of the navigator
delete item /name=close delete item /name=system-nethandler
Short command for an hierarchy in the database
define rb9 "show children /name=hql-rb9" Short command for a graph
define my_graph "open graph my_graph"
opg_symbol
Symbol
An xtt symbol can be used as a short command or a variable in a command.
If the symbol is used as a variable in a command in should be surrounded
by apostrophes.
Symbols are created by the define command. xtt> define p1 "show child/name=hql-hvk-pumpar-pump1"
xtt> p1
Example of a symbol used as a variable
xtt> define p1 hql-hvk-pumpar-StartPump1
xtt> open trace 'p1'
opg_security
Users and privileges
Proview contains a system with users that are granted privileges. To perform specific tasks
certain privileges are needed, and only if the user has this privileges he is allowed
to perform them.
The following privileges are used in the operator environment:
RtRead Read authority in runtime.
RtWrite Write authority in runtime. Authorized to change values of attributes from the
navigator.
RtEvents Privilege to handle alarm and event.
System System manager privilege. Authorized for most things.
Maintenance Privilege for maintenance personnel.
Process Privilege for process engineer.
Instrument Privilege for instrument technician.
Operator1 Privilegie for operator.
Operator2 Privilegie for operator.
Operator3 Privilegie for operator.
Operator4 Privilegie for operator.
Operator5 Privilegie for operator.
Operator6 Privilegie for operator.
Operator7 Privilegie for operator.
Operator8 Privilegie for operator.
Operator9 Privilegie for operator.
Operator10 Privilegie for operator.
Users
When the operator environment or Xtt is started, you login either as a user, or you
are assigned the default privileges stated in the Security object.
If the startup is made with an OpPlace object, the user is fetched from the UserName
attribute in the User object. If a user is missing or invalid an login window is opened
and the user has to login with username and password.
If Xtt is started without OpPlace object, the privileges are fetched from the attribute
DefaultXttPriv in the Security object. If there are no privileges that gives read
authority, the login window is opened.
Navigator
To make changes in the database from the navigator, RtWrite or System privileges are
required. This is also valid for the command 'set parameter'.
Plc Trace
To make changes in the database from PlcTrace in simulate mode, RtWrite or System are
required.
Object graphs
Generally the privileges RtWrite or System are required to make changes in the database
from an object graph. There are though some exceptions. In ChanAi and ChanAo also
Instrument has authority to change signal ranges, and to set an Ao in test mode. In the
PID and Mode graphs, Process are authorized to change beside RtWrite and System. In the
Mode graph you can furthermore control the authority by opening the graph with the
command 'open graph' and use the /access option.
Process graphs
In the process graphs the designer chooses for each input field or pushbutton which
privileges are required to make a change.
opg_functionkeys
Function keys
You can use the function keys as shortcuts to open graphs or influence objects in the
database.
Function calls
The following functions can be called when an function key is pressed.
SetDig()
Sets an attribute of type Boolean. The name of the attribute is specified as argument.
ResDig()
Resets an attribute of type Boolean. The name of the attribute is specified as argument.
ToggleDig()
Toggles an attribute of type Boolean. The name of the attribute is specified as argument.
Command()
Executes a Xtt command. The command is specified as an argument.
Setup file
The connection between the keys and the functions is specified in the file Rt_Xtt on the
login directory. In the file there are one row for each key. On the row i written
- Possible modifiers (Shift, Control or Alt).
- followed by the name of the key, e.g. F7 or m.
- a colon followed by the function that is to be called with arguments.
A '#' sign in the first position denotes a comment.
Example
#
# Configuration of Global function keys
F5: Command(event ack /prio=A)
F6: Command(event ack /prio=NOA)
F7: Command(show alarm)
F8: Command(show event)
F9: Command(close all/except=navigator)
Shift Control m: SetDig(F1-Start.ActualValue)
Shift Control n: SetDig(F1-Stop.ActualValue)
Shift Alt n: SetDig(F1-Reset.ActualValue)
opg_statusmonitor
Status Monitor
The Status Monitor is a tool to supervise and handle process- and operator
stations. You add nodes that you want to supervise and the statusmonitor views
status for the node, with color indication and status text.
opg_fig38.png
Fig The Status Monitor
Add and remove nodes
opg_fig41.png
Fig Adding of a node
opg_fig39.png
Fig Node info
opg_fig40.png
Fig Process status for a node
help command
Xtt commands
add parameterAdd an attribute to a picture Add a menu item to a xtt menu Add an attribute to collect list Call a xtt method for an object Call a xtt method filter for an object Show the collect list Clear the collect list Close alarmlist Close eventlist Close a graph Close the navigator Create a menu item in the Xtt menu Create a menu item in the operator window menu Show crossreferenses close xtt Define a symbol Delete a menu item in the Xtt menu Delete a menu item in the operator window menu Display help User login User logout Logg attributes to file Open a graph Open a java graph Open a fileview Open DsTrend or PlotGroup graph Open the operator window Read the content of an object from file Search for an object or a string Set advanced user Set a folder in a tabbed window. Set the value of an attribute Xtt setup Show xtt version Show a symbol Show PlcPgm objects Show PlcThread objects Show links Show rtt loggfiles Show subscription server Show subscription client Show devices Show RemNode objects Show RemTrans objects Show the runtime database Show files Show graph-files Show current time Show default directory Show the children of an object Show the content of an object Show object identity Show an object attribute Show a logging entry Show the event list Show the alarm list Show current user Play a sound defined by a sound object Store an attribute list in a file Write the content of an object to file
call method