PIPoint.UpdateValues Collective/Buffering behaviour before AF SDK 2.6?

Discussion created by ee.ashley on Nov 14, 2014
Latest reply on Nov 15, 2014 by ekuwana

From my understanding, version 2.6 of the AF SDK added an overload for the PIPoint.UpdateValues method, which allows the caller to specify an AFBufferOption. The default option being BufferIfPossible when the original UpdateValues method is called without specifying an AFBufferOption.


However, what is the expected behaviour in earlier versions of the AF SDK when writing to a PI Collective using PIPoint.UpdateValues where you cannot specify the AFBufferOption?


It seems the AF SDK reference I have installed only details the 2.6 version, even though I rolled back to the 2.5 version of the SDK.