Thank you, I think I understand and apologize for not being clear. I was imagining a super simple setter like:

A better way for me to ask the question would have been: Is there a way for the code in the setter to know that the value was just changed by the QuickOPC mapper as a result of a change in the subscribed value, OR was it set from within the local application expecting it to also be written to the server. The write would be unnecessary if the change just came from the server, but would be necessary if the change came from the application and needed to be reflected in the server.

I think from your answer, you're saying that there wouldn't be a circular issue because if the mapper changed that value to true and the setter then inefficiently wrote it back to the server, nothing would happen because the QuickOPC/Server would note that an unchanged value was being written and it would be ignored. Hence, no circular condition.

I realize that the write could be conditional on whether the stored private value is different from the new value.

A locally initiated change would make the write, but when the subscription change event comes back after a successful change in the server, the write would be prevented. But, if the change was initiated by the server, the setter would note the change and then make the unnecessary/inefficient write. The OPCServer would be ok with it because the node was already that value and not cause a new subscription change event. (I think)

I appreciate your quick response, unfortunately the notification went to my spam folder and I only just now found it, so sorry for my late acknowledgement.

Thanks,
Rick

I can easily carry a reference to the mapper in my mapped object. But, I have a question about your suggestion. Doesn't the setter execute when the change comes from the OPC server? If so, and you want to put an explicit Mapper.WriteTarget in the same setter, how do you prevent this from being circular where the change coming in from the OPCServer immediately triggers a write back to the OPCServer? I am new to this library and my have misunderstood your suggestion.

precisely

Hello,

thanks for the fast reply. Just to clearify to you what i'm trying to achieve ist that i have a data class with its properties which i want to bind to the applications gui. To keep the data consistent between opc server and the application i would like to have a two way subscription which is getting the data changes from the server as well as sending the changes from the user to the server just without using a separat write command or inject the mapper class to data class itself.

For Example I only want to declare a property like this

and create the two way binding.

I saw a similiar example on a other client sdk and just want to know if opc labs is supporting such a feature, too.

Hello,

First of all I am using VS 2015 and programming an wpf application via MVVM.
I subscribed a data class with its properties to a similiar structure on our opc server successfully with the attributes of your live mapping feature. I'm getting the updated values if the data on the server changes. But if I want to do it the other way around, which means the user changes data in the live mapped class through our application the data will not be transfered automatically to the server. Can you tell me what steps would be necessary to do it?
I figured out, if i'm calling the write method the changes will be transfered, but i do not want give the UAClientMapper instance to the data class where the live mapping is happening.

Thanks in advance
André