CIRCUTOR PowerStudio Series - Manual (Page 33)

PowerStudio
User Manual 33
• classic  Launches the client with the classic look and feel instead of the substance option.
Example: java -jar AppletScada.jar classic
• multipleinstance  Launches the client with permission to run if there is another client open.
For safety purposes, the last version would check to ensure that there were no other clients
open when running, and would not run if there were. We can override this restriction with this
parameter. Example: java -jar AppletScada.jar multipleinstance
• user:user password:password  Automatically logs in with the specified user and
password. Example: java -jar AppletScada.jar user:john password:xh234
• sleep:x  Establishes the refresh time of SCADA screens for monitoring devices and for
checking active and reported events. It is set in milliseconds, with a minimum of 20
ms. Example: java -jar AppletScada.jar sleep:200
• address[:port]  Indicates the http address (IP or name) to which the client will attempt to
connect. If necessary (the engine is not in port 80), the port may also be indicated.
Example: java -jar AppletScada.jar powerstudio.circutor.com:8080
3.2.13 I am making my first screen or report and I cannot add a background
image or a still picture. What is happening?
You should remember that the images that can be included on the SCADA screens and the
reports must have been added previously through the image manager. Therefore it is necessary before
starting to design a screen or report to add the images you will need through the image manager.
3.2.14 What can be "counted"?
Any event added to the system contains a variable that indicates how many times it has been
enabled, how many times it has been recognized, how many times it has been deactivated, how long
has it been active, if it is active at the moment and how much time has elapsed since it was last
enabled.
One can also count how many times something has occurred in the current hour, day, etc. For
this purpose a forced calculated variable will be created and initialized to 0 and an event, which when a
condition is fulfilled performs the action of forcing that variable to its same value plus one unit.
[R$CAL_FORCED.COUNTER1]=[R$CAL_FORCED.COUNTER1]+1
We then just need to add an event that would reset this counter to 0 when the date was
outside XX / XX / XX 00:00:00 (00:00:00 hours each day) with which the counter would have the
number activations of the day in course. The counter reset could be carried out with a variable forced
control on the SCADA screen, in this case manual instead of automatic.
3.2.15 I would like to export the report data in order to process it later. How can
I do it?
The data displayed in a report is log data grouped together for the period of the report,
therefore we have a value per period (if it is an expression where several variables are involved the
value of each variable is recovered for the period of the report and the expression assessed).
For practical purposes, the values of the variables that are used in the reports can be
consulted by requesting / services / user / records.xml (which is documented in the XML user
requests section).
Imagine then we have a report with the following appearance: