How to map nodeset variables to existing nodeset-ids in address-space

[Suslsuk]

Hello,

we use the DataAccessServer as a reference for our server. The server creates variables/blocks on startup with
an underlying system that updates the values depending on the datasource.

Now we have to read a nodeset file (compagnion files and map them
to the existing variables in another namespace. ImportXml works fine to create the objects in defined in the nodeset file into a new namespace. But how to map these objects (variable types)?

We checked Alias but couldn't find an implementation example.
Would be great if someone has a simple solution.

Thank you

[romanett]

Hi Sulsuk, you could take a look a the reference servers Boiler NodeManager, which makes use of a predefined nodeset:
https://github.com/OPCFoundation/UA-.NETStandard/tree/master/Applications/Quickstarts.Servers/Boiler

Does this help solve your question?

[Suslsuk]

Hi, thanks for the fast answer and suggestion. The Boiler reference is a good starting point that I have already looked at.

I assume that it is not an uncommon use case that all tags of an HMI, PLC or other automation solution are made available in a UA data access for MES/ERP etc. systems. systems.
So there are one or more namespaces with tags with different data types/structures that are read from and written to. These tags already have ready-made implementations for IO layers that read/write the real-time data.
Now there are customers who have interface descriptions for MES/ERP systems in the form of nodeset files to standardise access to data in various devices/systems.

To avoid having to implement a separate node manager for each customer, it would be helpful to be able to refer to existing tags in existing namespaces in the nodeset file. I thought this could be solved with aliases or similar (https://reference.opcfoundation.org/Core/Part17/v105/docs/A.2#FigureA-3) but couldn't find an example.
Perhaps this use case is not specified at all and the only way is via implementation/coding - please confirm.

Thank you very much