Skip to Main Content
AVEVA Product Feedback


Status Completed
Created by Guest
Created on Aug 20, 2022

NoOutput() function in Asset Analytics

I want to use the NoOutput() function in my analytic even when the output Attribute is not mapped to a PI Point
  • ADMIN RESPONSE
    Aug 20, 2022
    The AF 2018 SP2 release relaxed this requirement. Please take a look with any version newer than 2018 SP2 to see if the current behavior satisfy your needs.
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    Can you elaborate why? Is this about getting to some other desired behavior (breaking out of the calculation since there is no result or trying to "skip" certain parts of the analysis)? Is this being used with Analysis DR? OR a custom DR? It's unclear to me to immediately see the use case outside of what is being described above. If I am not writing to PI, and ignoring a custom DR, I don't see a reason I would skip an output.
  • Guest
    Reply
    |
    Aug 20, 2022
    Wanted to add notes from a case relevant to this request: The customer would like to store a value based on some logic (which lends itself well to analytics). There comes a point in the logic where we simply don't want to store a new value because we've determined the available data do not describe our interests in a meaningful way. In those cases, we'd rather the tag didn't update (and that it maintained the previous timestamp and value). As an example, we can think about a filtered expression (though this is not their use case). We could say that any value over X is obviously the result of a sensor malfunction, and state that we want a way of accessing only the data points with values under X. This should be simple enough to do on-the-fly, and it's not clear that we're adding enough value to justify creating another tag for some customers.
  • Guest
    Reply
    |
    Aug 20, 2022
    Hi Stephen, unfortunately the solution is not working for my usecase. Looks like nooutput still doesn‘t work if i want to write directly in the analysis Data Reference. At least that was one outcome of my Customer Portal Case 00851402.