Tip:
Highlight text to annotate it
X
Keep in mind as you work with Performance
Equations that these are simply regular PI tags that have certain
specific values that we put
in things like PointSource and Extended Descriptor,
and Location Code for Scan Class, just like any other
tag. So, these can be any type of tag.
You can actually have a Performance Equation that gives you a Digital,
you know using an If-Then statement. If flow is greater than
50, Then On, Else Off, something like that.
So, again, you can see this if you
inspect in the regular PointBuilder any of these
tags that you're gonna be building during the exercise. So,
if we look at this, you know, Pointbuilder here, this tag
0test2, as you can see it's a tag whose
PointSource is C, and whose Extended
Descriptor is simply this special
syntax that we're using for doing the Calculation.
Oh, and by the way, a good example of how
this is very similar to the other types of tags,
is that look at Location3. If your look in the
Notes in the, on this slide and also if you look
in the documentation for Performance Equations
in the Server Guide, you'll notice that Location3
is simply a toggle to indicate whose
timestamp we use when we store the
result. Do we use the timestamp at which the Calculation
was calculated? That's what happens
by default. Or, if you set this equal to one,
if it's a Triggered Calculation, Event Triggered,
we'll use the timestamp of the value that
triggered the Calculation. It's usually gonna be very close, but
it's a good example of how, just like other interfaces,
or other types of tags, these Location
Codes are just used to toggle certain functions,
or certain features.