Hello.

1) Regarding the BC40056 warnings: Not sure. Would have to have the project. It could be that you have a separate project where you copied over the Import-s but have not actually referenced the NuGet packages.

2) Regarding the IntellISense warnings: You have not provided the actual warning text. Since the editor is showing them in gray, it might be that those Import-s can be simply removed, because they are not used in that particular file.

3) I am glad that LooseReferenceTypes worked for you.

Regards

Hello.

Please upgrade to version 5.80.191 or later - NuGet packages are now on www.nuget.org, and installation program (probably not necessary in your case right now, if you are referencing the packages from www.nuget.org), on our Downloads page.

The UADataDialog now has an addition LooseReferenceTypes property. It defaults to False, which is the old and correct behavior. You can set it to True before running the dialog. In this case, it will browse with "wider" parameters, in order to cope with non-compliant servers.

Note that I do not have the Citect Plant SCADA server, not any other similarly misbehaving server, available. I therefore could not actually test whether/how the LooseReferenceTypes = True. Let's cross our fingers that it will do what you want.

best regards

Hello.

To the first corrected link: The text under it says "The HasChild ReferenceType is an abstract ReferenceType; only subtypes of it can be used.". This proves my argument, and disproves theirs.

To the second corrected link: That is a long text, so not sure what they wanted to say by linking to it. It contains the above text, plus additional parts in support of my arguments, such as that HasComponent is the reference type used for DataVariables.

The fact that other clients show what you want has no significance. Those clients have a different purpose. They are designed to show everything. The browsing dialog you are using from QuickOPC to show *subset* of the address space. The subset is chosen as to show the nodes that can get you the actual data values. The fact that the server has chosen an incorrect (and, in fact, invalid) reference type breaks the OPC specification and therefore the QuickOPC cannot show the intended subset.

The problem with "showing everything" is that there can be millions of other references that you do not want to see. So if QuickOPC was to show everything, it would work in this case (with broken server), but will not work well in other cases, with servers that actually do work well. That is not something I can allow.

The solution would be to have a special setting that would allow you to specify that you explicitly want the broken behavior. Or, a new dialog for the same kind of browsing that other clients have. In both cases I would recommend against doing it, for the reason explained above.

Regards

Hello.
There really is nothing I can add.

I have provided 3 working links that clearly show, in the OPC UA specifications, that what they are doing is wrong.
They have provided 1 link that does not work, and some opinion of their own which contradicts the OPC UA specifications.

Part of their provided answer is plain nonsense even in their own terms. For example, " However, it’s not a violation to have such a reference. The key point is that only subtypes of it can be used.". Having a reference *is* using it.

Regards