andre.moreira1
My feedback
-
78 votes
Looking for more inputs on how to determine what the last good value is (was). While it’s simple to say a numeric value is good, but what if it’s a non-sensical numeric value like 1000 for temperature? It is also possible to the source system to send out status like NoData. How should that be interpreted? Please provide your inputs.
andre.moreira1 supported this idea ·
-
3 votes
andre.moreira1 supported this idea ·
-
1 vote
andre.moreira1 shared this idea ·
-
3 votes
andre.moreira1 supported this idea ·
-
65 votes
andre.moreira1 supported this idea ·
-
9 votes
andre.moreira1 supported this idea ·
-
76 votes
andre.moreira1 supported this idea ·
-
25 votes
andre.moreira1 supported this idea ·
-
19 votes
andre.moreira1 supported this idea ·
-
9 votes
andre.moreira1 supported this idea ·
-
154 votes
An error occurred while saving the comment andre.moreira1 supported this idea ·
-
168 votes
At this time, this item is not currently scheduled for a release of PI Vision. If this changes, this item will be updated to reflect the current status.
andre.moreira1 supported this idea ·
-
150 votes
andre.moreira1 supported this idea ·
-
12 votes
andre.moreira1 supported this idea ·
-
13 votes
andre.moreira1 supported this idea ·
-
28 votes
An error occurred while saving the comment andre.moreira1 commented
I was also surprised to find out that this isn't automatic. Perhaps this request doesn't have a lot of votes because most people don't even realize this is the case.
andre.moreira1 supported this idea ·
-
5 votes
andre.moreira1 supported this idea ·
-
230 votes
An error occurred while saving the comment andre.moreira1 commented
One of the most common requests I hear from clients, specially during the adoption of AF.
andre.moreira1 supported this idea ·
-
198 votes
This functionality to set the unit of measure for AF attributes at the symbol level is in development for the PI Vision 2022 release.
andre.moreira1 supported this idea ·
-
67 votes
An error occurred while saving the comment andre.moreira1 commented
Ideally, this feature would be added to PI Vision. A substitution parameter option to extract the PI Point would also help. Would make it easier to build out with child attributes in AF, instead of using the TagName function for AF Analysis. But, as others pointed out, having this information easily available in PI Vision is preferred, since most users typically only have access to Vision.
An extra Visibility item in the Value symbol would do the trick, or at least the PI Point name in the floating box that appers when placing the mouse over an object.
andre.moreira1 supported this idea ·
This would add flexibility to leverage Element and Event Frame templates that use Table Lookup attributes.