Location5 is used to indicate how the point is to use data that has the quality of “Uncertain”.
Data can have a quality of GOOD, Uncertain or BAD.
0 – “Uncertain” data will be sent to PI with the questionable bit set.
1 – store the digital state “Bad Quality” if the quality is “Uncertain”.
2 – “Uncertain" quality will be treated as good quality
If the Quality is “Bad”, then the digital state “Bad Input” will be sent to PI.
All our HDA tags have Location 5 set to zero. I found a tag that was receiving "Bad Input" every 15 minutes, and tried changing Location 5, firstly to 2, then to 1 but each time I still get "Bad Input"
If you are planning to filter bad data then i would request you to set PI AF analysis to use BadVal function to store only good data (set to trigger based) especially for critical tags.
Bad Input is the value written to a tag if the data received was invalid. For example, if the data received does not match the point type (trying to write a float value to integer tags) or the quality flag of the data received from the data source was “invalid”.
So My recommendation is for you to compare the tag properties of PI tag with source tag and investigate the root cause of these "Bad Input" values.
Tag properties are the same, it looks like it's when the instrument on the sending system has a comms fail :-
(ignore timestamp difference as one is GMT, the other BST)
0.14300000667572 12/07/2018 13:15:00
0.204000011086464 12/07/2018 13:29:59
0.150000005960464 12/07/2018 13:44:59
0.144000008702278 12/07/2018 14:00:00
Bad Input 12/07/2018 14:11:32
0.136000007390976 12/07/2018 14:11:36
0.220000013709068 12/07/2018 14:15:00
0.144000008702278 12/07/2018 14:29:59
12/07/2018 12:15:00 0.143000006675720 m Timed Report Good
12/07/2018 12:30:00 0.204000011086464 m Timed Report Good
12/07/2018 12:45:00 0.150000005960464 m Timed Report Good
12/07/2018 13:00:00 0.144000008702278 m Timed Report Good
12/07/2018 13:11:32 0.136000007390976 m Value Change Comm Failure
12/07/2018 13:11:36 0.136000007390976 m Value Change Good
12/07/2018 13:15:00 0.220000013709068 m Timed Report Good
Thanks for the details. As you said there was communication failure in your source system side, you need to get it fixed in source level in order to avoid the bad inputs in PI system.