1 of 1 people found this helpful
As long as the string value received exactly matches a valid digital state in the digital state set that the tag is configured for, then yes, the value can be properly coerced and archived. Keep in mind that if the string does not exactly match a digital state for the tag, then the write will fail and a message will be logged indicating that failure.
Since it sounds like you are obtaining this data from an offshore device, I would also recommend configuring buffering (if it is not already) for whatever application is sending the string values. The reason for this is that PI Buffer Subsystem will see that the tag is digital, and attempt to coerce the string value to a digital value prior to sending the value over the network to the PI Server. This is advantageous to send the digital state offset codes over the network rather than send the full strings, which could cause further strain on low bandwidth networks.
Hope this helps,
Thanks for your input. I shall check the same and confirm.
I've tried the same as you advised.
Actually , i didn't have clue on all the values which will be sent from offshore. I just have two values with which i built the digital set as like offshore value.
The same digital set, i've assigned to the digital tag too.Moreover, i made the Loc2 as 1 ( for string data handling).
However , my tag is still not receiving the data from offshore.
Is there anything else, i should check?