An example of how I'd like to use it...
We have some data that used to be scanned from an analog instrument and passed into PI. This instrument was specialized and expensive to maintain so we investigated calculating the data from simpler, cheaper instrument signals. We end up with two PI tags for comparing the data side by side.
Some end users are probably using one point, some the other. We can't tell and they are not savvy enough to be able to tell us! So we point both tags at the new calculated data and forget it.
However, it would be nice to be able to determine which users are actually using which point, get the minority to use the majority's point and delete the now unused one.JamesGibb shared this idea ·
How can the version of the OPC Client affect whether you can get data out of the OPC Server? If the Server is 2.05 compliant any Client should be able to test it. Never used the OSI OPC Client for testing, but is it not 2.05 compatible?
Throwing an error or selection box would break the existing behavior. If the behavior is documented then I can't see any reason to do anything else.