I’m trying to implemet AutomationML into my UA Model. Therefor I add OPCUAforAutomationML .xml files as existing model in Unified Automation UAModeler. After adding BaseTypes I get several errors of the same kind: Incomplete internal reference detected: NodeBrowseName (ns:ID) and after adding AMLLibraries Value of ns:ID has invalid type.
As I took a closer look at the BaseTypes.NodeSet.xml, I noticed that the ParentID is missing at some nodes ( <UAObject NodeId=”ns=1;i=5006″ BrowseName=”1:AutomationMLFiles” ParentNodeId=””> for example). I’m still looking what caused the error in Opc.Ua.AMLLibraries.NodeSet2.xml. I only noticed, that many nodes were not imported.
After running the consistency check even more errors appear. It seems like there is an issue with ID and Version variables.
Is that a known error or maybe I’m doing something wrong? Did someone had similar troubles?
I am not used to the UAModeler from Unified Automation, so first question would be, if you can tell, which version of the UAModeler you are using? I assume that the UAModeler includes a version of the AMLBaseTypes. Do you know which version of the OPC UA AML Nodeset it includes? Is it described somewhere? The AMLBaseTypes are referenced in all AML-OPC-UA.xml models via references to the included NodeIDs. Currently, there is the version of the AMLBaseTypes which was published as Companion Specification in February 2016. This version also includes the corresponding AMLLibraries model. Did you use these ones for your model or a newer version? There is an extended version of the AMLBaseTypes (with different NodeIDs) for the DIN SPEC 15692 “Combining AML and OPC Unified Architecture” which will be published in December 2016 and includes an extended mapping concerning attributes and mapping details. For this version of the AMLBaseTypes, the NodeIDs changed. The newer version of the nodeset is not published yet as the DIN SPEC 16592 was not officially published until now, but includes additional Nodes. If you modelled you OPCUAforAutomationML.xml against this version, the described problem occurs if you use this in combination with the Companion Specification Nodeset.
Hello and thank you for the fast reply.
I’m using UAModeler 1.5.0, which is the latest version of the software. The modeler itself doesn’t include any AML specifications. So I downloaded 1457352183-AutomationML Whitepaper – OPCUAforAutomationML_Mar2016 directly from http://www.automationml.org and added Opc.Ua.NodeSet2.xml, Opc.Ua.AMLBaseTypes.NodeSet2.xml and Opc.Ua.AMLLibraries.NodeSet2.xml to my model. By adding these 3 namespaces I already get the errors or warnings as described in my last post.
Don’t understand me wrong, it is possible to work with that. Maybe the warnings can be ignored and at the end it has no influence on the resulting model. I was just wondering and want to get sure.
Most Users Ever Online: 95
Currently Browsing this Page:
Guest Posters: 1
Administrators: firstname.lastname@example.org, email@example.com, Randy Armstrong
Moderators: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, Jim.Luth@Schneider-Electric.com, Karl-Heinz Deiretsbacher, email@example.com, firstname.lastname@example.org, Karl Deiretsbacher