Thank you. Now with the new full picture I have realized what the problem is.

You are binding to an OPC DA property (Value). OPC DA properties do not support subscriptions, that's why you are not getting any dynamic updates. There are also no other parameters to be configured for Read, Subscribe, or Write, and that's why System.Object is shown.

In order to achieve what you want, you need to bind to the OPC item itself. That is, when you are in the "Point Editor", you need to select the node that, in the information pane at the bottom of window, will say "OPC-DA Node", and *not* "OPC-DA Property". The properties also have a different icon, and are always shown as terminal leaves in the tree.

I hope this helps.

Hello,
thanks for clarification. Now I mostly understand the issue.

Here is some information:

- I was able to reproduce the fact that "Write Parameters" show as System.Object. This appears to be a bug on our side. We will have a look at it. It should not have, however, influence on the actual problem you have. I have not seen "System.Object" in other parameters, did you?

- I do not know where the 100 ms comes from, I was not able to reproduce it; the default should be indeed 1000 ms. Please check the "parameters templates" on the daConnectivity1 component (click on it in the component tray below the form, the view its properties). This has the initial values for newly create bindings. Anyway, 100 ms should work too, or you can change it back to 1000 ms if you like.

- Please check "Binding Operation" property on the binding (this is in the same property grid as you have sent the picture of, but a bit higher, so that I cannot see its value in your snapshot). The value should be "ReadAndSubscribe" (and not e.g. just Read).

- If the above is correct, it could be that the Read works, but Subscribe gives some error, but you do not see the error, because in Live Binding, you need to take care of displaying the errors yourself. This is described here: opclabs.doc-that.com/files/onlinedocs/QuickOpc/Latest/User%2...ing%20in%20Live%20Binding.html (at the bottom). Errors are typically displayed by making a second binding with "Argument Path" set to Exception, ErrorMessage or such, but that might be too complicate for now. I suggest that you simply change the "Argument Path" on the existing binding from "Value" to "ErrorMessage", and see if running the project shows any error in the control.

Regards

Hello,

unfortunately your post is not clear to me. Please read Rules for Forums Posts (www.opclabs.com/forum/announcements12/2365-rules-for-forum-posts ) and clarify the information provided.

Best regards