• State Not Answered
  • Replies 1 reply
  • Subscribers 3 subscribers
  • Views 140 views
  • Users 0 members are here
Options
Related

Issue with Discrepancies in Mapped Values Between PI Analysis and PI AF Attribute

A_Alsop

Hello everyone,

I'm experiencing a strange issue with PI AF. When I create a function in PI Analysis, the result shows, for example, 181 kg.


image.png
However, when I map this result to an attribute in PI AF, the value displayed is 1007.


image_1.png
I haven't changed any configuration settings, and this discrepancy only occurs with certain values, while others map perfectly.

 

Has anyone else encountered this issue? Any insights on what might be causing this inconsistency would be greatly appreciated.

Thank you for your help!

Parents
  • 0

    Hello. Please try to create a new output attribute from the analysis, and see how the result looks like then!

     

    A possible explanation could be that you have added "UOM=...." to the config string of the PI Point Data Reference for the "Périda hexano Planta A_kg" attribute. If this specification is added with another unit than 'kg', AF will do an implicit unit conversion when you view the values. The only reason to include "UOM=..." to your PI Point DR config string, is if you know your tags have a different unit (f.ex. gram) than the one you want to use in AF (f.ex. kg).

     

    Another possible (but less likely) explanation could be that your output attribute is not configured with the correct value retrieval methods (i.e. By Time: Automatic, By Time Range: End Time), and could be performing some sort of aggregation before the value is shown.

     

    If the output number is converted on the fly, most likely you could pull up the underlying PI Point in PI Vision/PI DataLink or PI System Management Tools -> Archive Editor, and verify that the values aren't converted there. AF configuration is most likely responsible for a conversion before the numbers are shown to you!

Reply
  • 0

    Hello. Please try to create a new output attribute from the analysis, and see how the result looks like then!

     

    A possible explanation could be that you have added "UOM=...." to the config string of the PI Point Data Reference for the "Périda hexano Planta A_kg" attribute. If this specification is added with another unit than 'kg', AF will do an implicit unit conversion when you view the values. The only reason to include "UOM=..." to your PI Point DR config string, is if you know your tags have a different unit (f.ex. gram) than the one you want to use in AF (f.ex. kg).

     

    Another possible (but less likely) explanation could be that your output attribute is not configured with the correct value retrieval methods (i.e. By Time: Automatic, By Time Range: End Time), and could be performing some sort of aggregation before the value is shown.

     

    If the output number is converted on the fly, most likely you could pull up the underlying PI Point in PI Vision/PI DataLink or PI System Management Tools -> Archive Editor, and verify that the values aren't converted there. AF configuration is most likely responsible for a conversion before the numbers are shown to you!

Children
No Data