I thought you want to integrate OPC client functionality into your application. What you have sent looks like a low-level protocol to some device.

In the OPC world, typically it is the OPC server that takes care of the communication protocol and the actual communication with the device. The data provided by the OPC server are then already in much more meaningful format, such as streams of values with timestamps and qualities.

If, for whatever reason, the string you have described is being transferred "as is" through OPC )I doubt it), then a generic OPC client has nothing to do with its internal semantics. It would be a task of the application (i.e. your code) to interpret the string.

Best regards

Can you describe in more detail what you mean by "short Data Structure"? Do you perhaps have a document, or other way to describe it?

Dear Sir,
thank you for your interest in our products.

It is correct that our QuickOPC product can be used to integrate OPC UA (and OPC Classic) functionality into a Delphi application. We provide several Delphi-based with the product (after product installation, they are under ExamplesCom/OP/DelphiXE7.

The examples are mainly aimed art showing how the basic methods of QuickOPC API can be called from Delphi, and as such, are relatively simple. The most relevant functionality (such as browsing, reading, writing, and subscribing to data changes) is, however, shown well. It is also possible to look at examples in other languages, because there are really just two APIs (one for .NET and for COM tools), and even these two are almost identical. The language that has the biggest number of examples is C#.

Due to the number of functions in the product times the number of tools/languages our product can be used from, it is unrealistic to provide comprehensive set of examples for everything and everyone. We would be, however, happy to answer any concrete questions, in case you would not know how to achieve something.

Best regards