As it has been described in “How to create a calculator point-basic level”, after we have typed the input and output variables, we are ready to start programming. We can have local outputs which will be used to calculate the output variables, we have declared.
In the given example we will create a program which sums the Process Values of the Feeders. The input variables are the process values of F1, F2, F3 and F4. The output variable is the Summation of process values of feeders. The local output is the summation of F1 and F2.
Figure 1:
To create a local output, we select…. the one we want, and we drag and leave it in the white area (Figure 1.2). In Designation we type the name of the local output. In case we want to make any modification in the local output, by clicking on the desired local output, the options of edit are activated (highlighted red dashed rectangular). Next step is to define the arithmetic operation we will use, resulting the local outcome. The available options are the 4 fundamental arithmetic operations.
Figure 2:
Again, by clicking, dragging and letting it off on the “line” connecting inputs and local output, we create the equation that we want (Figure 2.1). We need to define the inputs. We have the option of either typing a value or browsing and selecting one of the input variables we have declared initially.
After a local output has been created, automatically it can be used as input for the next arithmetic operations. When we want to calculate one of the output variables of the program, in case of the example is “Summation”, we move the censor next to the name of the output variable. The colour becomes light blue, we click on it, we drag it to the main area, and we let it off. As it is shown on Figure 3, we have the option of using “SumF1F2”, which is local output, as input to the calculation of “Summation”.
Figure 3:
When we want to add more variables in the operation we have chosen, we select the box of the arithmetic operation and “Add Pin” is highlighted.
Figure 4:
To save the program or any modification we make, there are 2 steps, as shown below
Figure 5:
We can see the calculator point we have created in the following path: System→ Configuration→ Point Editor→ Functional. In our example we have selected the calculator point to be shown under PS_Line1→ Feeders
Figure 6:
ALTERNATIVE WAY OF CREATING A CALCULATOR POINT
Another way to create a calculator point, after we have created the Calculator Program, is through Point Editor. The path is System→ Configuration→ Point Editor→ Functional. As it is shown in Figure 7, we select where we want the outcomes/calculator points to be shown and we select “New”.
Figure 7:
In the window that is popped up; as shown in Figure 8, we declare that this point will be “Calculation Point” (1), we also declare where we want the point to be shown (2), we name the Calculation Point (3) and we link it with the desired Program (4). The outputs of the calculator program are shown. By adding “.” before the name of each output, the outputs become points (5). Finally, we define the type we want these points to be (6).
Figure 8:
To define the properties of each calculation point, we select the desired calculation point, under “General”, as it could be seen on the right side of Figure 9, we have the option of making plot of this point by browsing the “Menu” (1) and selecting either “HMIBasic.Menu.Default” or “QcxCore.Menu.Default” (2).
Figure 9:
Figure 10:
Figure 11:
In order the calculator program to calculate the outputs we want, we need to set values for the inputs. To do so, we select “Programs” as type under Hierarchy (1). We choose the program that we have linked the calculation points; in our case Calculated Moduli (2).
Figure 12:
We select the input and we have the option of either setting a constant value or link it to a process value. It is highly recommended to save every time that an input is linked to a process value. Otherwise the system might not allow you to save the changes in the end and in this case, you will need to start the tagging from the beginning.
Figure 13: