Is there an if-then-else formula for this: If a tag provides a "Bad", "Configure", "Comm Fail" (and other strings), the formula will filter these in such a way that these strings will be substituted with zero or other number. My goal is for the formula not to display message like "Data not available for attribute xxxx".

You can use a workaround like a Formula, though for performance the best solution is to output to a PI ...

The Formula data reference does not work with strings. Possible workarounds: Use an Analysis instead since it works fine with strings. Note, however, that an Analysis does not work on an Event Frame. If your input attribute is not based on a digital state, this may be your only option.

PI AF Formula Syntax I am trying to create an AF element attribute that calculates the flow to a specific vessel. The flow meter is shared, so I need to first determine if the vessel's valve is open.

One option is to use a DataSet in Processbook.Use the TagVal PE function to take the value of a tag now, and another value at a previous interval of choice, then divide the difference by the time interval (in seconds).

Attribute PI DataLink PI SQL Client; Age: Older: Newer and likely still being improved significantly: Suitability. Small direct-to-sheet reports (refreshes too slowly when there is a lot of data)

2022年9月7日 · I have written the required formula as a formula data reference on the event frame template. My problem is I don't see a way to add this formula as an output at close on the analysis and in the notification format it only gives the option of sending the value at the start time. Any help on this would be much appreciated. Thanks!

The Performance Equation syntax is also OK. I tested it standalone. As for standard calculated point, I use the "exdesc" to fill the formula. However it seems that PI is not happy when I mix location configuration for output and exdesc filled by a performance equation. PI point switch to "scan off" Can you help me to configure it? BR

Hi William . I would suggest you to implement analysis TagAvg('TagName','*-3m','*') and map to output attribute. As it is a noisy tag tag would suggest you to use periodic scheduling if that help

Make your calculations more robust by using Attributes instead of hard coding values in the expressions. When writing an expression it is not a good idea to hard code things like upper/lower limits, time ranges, and other parameters.