The design uses the FxRoot from Part 81 along with children in a hierarchy of AutomationComponent > Assets > OurCustomAsset.
In UaModeler, I've loaded the standard Opc.Ua.NodeSet2.ua model and the Opc.Ua.Di.NodeSet2.ua model. In addition, I've downloaded the XML nodeset files for opc.ua.fx.data and opc.ua.fx.ac from the OPC Foundation website and imported them.
That done, the FxRoot object shows up in UaModeler under the Objects folder, and has the expected node ID under the http://opcfoundation.org/UA/FX/Data/ namespace.
The complication at this point, though, is that the design I've been handed has an AutomationComponent beneath FxRoot that resides in our own server namespace (urn:mycompany:mygadget). In UaModeler, if I add an AutomationComponent object of type AutomationComponentType, it resides in namespace 4 (http://opcfoundation.org/UA/FX/AC/), and I am unable to change that namespace. The design has all the nodes beneath FxRoot mapped into our own server namespace, in fact, which isn't something I've figured out how to do in UaModeler, despite the "Enable editing of NodeIds" being checked in settings.
I suspect one of three things is going on, in order of likelihood:
- I simply haven't figured out how to use UaModeler to do this;
- UaModeler is enforcing some constraint that the designers and I aren't aware of; or
- There may be a shortcoming of some sort in UaModeler.
Thanks,
Dave