Hello.
I am not sure if I fully understand the question. But I will try to throw in some thoughts, hopefully that would help, or lead to refining the issue.

First of all, drawing charts based on data received from OPC subscriptions can and should be done based strictly on their values and timestamps, individually for each item. No artificial grouping is necessary, and in fact, in general case I would consider it harmful, because such *is* the nature of the data received - the received values do not really "belong" together in semantical sense. The grouping made on the OPC level (by the client putting items into OPC-groups, which form basis for subscriptions; and the by the server, taking subset of these and sending them over to the client at some point) is strictly for implementation purposes, in order to make the physical transport of the data convenient and efficient. For the meaning of the data, it bears no significance how they were "bundled" for transfer.

I am not sure what you mean by "subscription cycle", but let's assume you mean the callback that the OPC server makes and which informs the OPC client about the items whose values have changed. Internally, of course, we have an information about which items have come together. But this information is not made available through API to consumers, and that is very intentional design decision - precisely because attempting it to interpret this "grouping" in any way would be wrong. The server may, for example, split the callback into two parts, because it cannot send so many items at the same time. And you would then think they came from different "cycles" in the device - but they have not.

OPC DA has no way to force the kind of subscription updates you asked for (getting all values every time). I know this is a common issue with historians and similar software, that are basically forced to draw a straight line from the last timestamp until the values changes, although the device itself might have collected new data and therefore *knows* that the data has new timestamp but same value. Unfortunately that's how OPC DA spec works. In the newer OPC UA, you can specify that you get a value through subscription, even if it was just the timestamp that has changed.

It is possible to overcome this OPC DA limitation by doing repeated OPC reads "from device" instead of subscriptions. But at the same time, the spec will tell you that it is a discouraged practice (for efficiency reasons). But that's the way it is.

Best regards