You are not doing anything wrong (though I do not know yet precisely what is the cause of the behavior you described). The OPC UA address space is a complex structure, as are the conditions used to display its parts - and they differ between clients.

Note: The "Reference Type Id: Organizes" on the n_wlcFbk node shows how we have gotten to this node from its parent (Global PV). It does not determine what shows *below* this node.

It is possible that the EURange node does not match the filter we have for showing in the dialog; for example, it could be using a reference type (from the n_wlcFbk) that is not one of the following: References, Aggregates, Organizes, HasComponent, HasProperty.

Without analyzing the communication between the client and the server, it is difficult to tell the exact cause.

I should also note that (although I truest you in describing the issue), you first picture is not indicative of the problem; for it to show what is needed, it should show the parent node in the tree view (on the left side), and the fact that b_wlcFbk does not show as its child in the tree.

If you can figure out the node Id of the node you want to bind to, you can get around the browsing issue by specifying it in a different way, The "Bind to UA Data" is really just a shortcut for easy node selection combined with binding to a default property of the selected control. There are other ways, too: you can e.g. select the control, choose "Edit Live Bindings", add a binding, and then configure its Node ID in the property grid.

Best regards