RVsHeader.gif (20695 bytes)
 
Home

 

Installation

Content
Installing

 

User Guide

Introduction
A first approach
Example 1
Example 2
Example 3
Example 4
Example 5
Example 6
Creating a component
Creating a DataServer

 

Developer Guide

Developer guide
Classes reference

 

Examples

Running the applet

 

line.gif (43 bytes) Example 3: a process control mimic diagram

First, we will define some variables in the real-time database. To do so, open the configuration named DBDefHTTP. This configuration contains a set of lines beginning with #TagDef . Those lines define variables in the following way:

#TagDef Name; value; minimum; maximum; lowerLimit; higherLimit; limitsSetFlag; validityFlag; processName; remoteStateFlag; increment; unit

limitsSetFlag is true if the variable has some limits (minimum, …)
validityFlag is true if the value is considered a valid value
remoteStateFlag is true if the variable's value is to be fetched from the network.

You should now see a set of variables defined in the database viewer.

tanks.jpg (38216 bytes)

Open now the configuration named "Tanks" in a new window. By playing a bit with the variables, you should be able to animate the mimic diagram (apart of the Boolean variables, all variables are expected to vary from 0 to 10). This configuration is a dgsl script. Lets focus on two lines:

component SynopticView 15 15 115 130 SYNOPTICS/LIB/RDialB.txt|TagName=level1

component TextField 25 150 95 25 level1

These two lines insert two other components in the SynopticView component (the dgsl interpreter). The first one is itself a dgsl script while the second one is a TextField. This input text field is connected to level1 and may be used to modify the value of level1. If the configuration were @level1 and not level1, it would have been connected only on the output to level1 (see dgsl definition). While being able to modify level1, you wouldn't be able to see a change in level1.

If you have opened the configuration in a new window, you should see a new button on the right part of the menu bar. If you click on this button, you will see a Windows Explorer like view of the components.

Now, lets have a look to the following line.

map 18 301 111 369 SYNOPTICS/DESC/C_panel.txt

This line defines a link to the configuration which URL is SYNOPTICS/DESC/C_panel.txt. By double clicking in the rectangle (18,301)-(111,369), which is where you see the PLC crate, you will load the new configuration in a new window.
In this new mimic-diagram, you will see how on-off switches can be easily programmed in dgsl. There is also an interactive vertical cursor on the right side of the diagram. It uses the same technique we saw in the grid example.

Finally, open the configuration named "Trend". It is a trending component. If you look in the configuration list (ConfigList.txt), you will see that this component doesn’t need a configuration file like the dgsl interpreter (the configuration file being the script) but only a string. In that case, the configuration string is directly inserted in the configuration list.

line.gif (43 bytes)
author: F.Momal - CERN - LHC division - IAS group