Why do a tag read good values and as Bad input at the same timestamp? EXAMPLE:
9/5/2017 9:15:00 AM
Please note that the tag is previously configured as a CALC tag and now pointsource is changed.
Can you provide us with the tag configuration? What's writing to this tag?
instrumenttag is writing
piadmin: A(r,w) | PiRad: A(r) | piscanwrite: A(r,w) | PIREAD_MARTINEZ: A(r) | PIWorld: A(r)
KE*9AI1610 ROLLING 3 HR AVG
piadmin: A(r,w) | piadmins: A(r,w) | PiRad: A(r) | PIREAD_MARTINEZ: A(r) | PIWorld: A(r)
Here is an explanation of what Bad Input means:
It 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 an integer tags) or the quality flag of the data received from the data source was “invalid”.
Taken from: https://techsupport.osisoft.com/Troubleshooting/KB/KB01298/
Since the tag is being written to by an OPC interface, I would verify the following:
1- The quality of the data on the OPC Server
2- SDK logs on the interface machine (https://techsupport.osisoft.com/Troubleshooting/KB/3248OSI8/)
If there isn't enough information to identify the root cause from the information gathered above, I believe the next step would be to configure the interface with a higher level of debugging.
Retrieving data ...