2 of 2 people found this helpful
You should be able to determine quality by looking at the attributes error message.
TagBad cannot be used to determine if the PI Point is entered correctly. It could indicate that the value has a system digital state such as "calc failed". If you really need this you could have an analysis that evalutes only TagDesc('Value0') and a second analysis that checks TagBad('description') with logic to output an appropriate message such as "tag not found". Usually, end users are not entering tag names.
OK that works, so the secret is to split things into seperate analyses, I was trying to do it all in one and the one failure was stopping everything else.
1 of 1 people found this helpful
Very nice pictures and explanation!
The following can check to see if a PIPoint exists as long as that PIPoint is not a part of the trigger.
If you run this expression first and store it to a variable named Exists, then your Variable1 and Variable2 could be changed appropriately to something like:
If Exists Then TagDesc('Value0') Else "Point Not Found"
If Exists Then TagName('Value0') Else "Point Not Found"