Dear Support Team,
Does UaNodeSetXmlParserUaNode support parsing the NodeSet2.xml file provided by the OPC Foundation?
I want to know if it is possible to parse Opc.Ua.MTConnect.NodeSet2.xml with SDK 1.43.
regards,
Sun
UaNodeSetXmlParserUaNode read NodeSet2.xml
Moderator: uasdkcpp
- Support Team
- Hero Member
- Posts: 3072
- Joined: 18 Mar 2011, 15:09
Re: UaNodeSetXmlParserUaNode read NodeSet2.xml
Hi,
if the NodeSet contains (and uses) Nodes that were defined in the later specification (e.g. 1.05.x) than the Modeler/SDK from 2015 (e.g. 1.04.y) is using internally, you will most probably have no luck.
Generally you should look into the change.log of SDK and Modeler, it states which Specification/Nodeset version the software supports. Furthermore you should not use different modeling tools, but instead stay within the tool set environment we provide for our SDKs. Reason is that we can not help and not support you when using different tools from other manufacturers including from OPC Foundation.
The working groups doing the companion specifications typically use our UaModeler for finally testing if the model is correct and working and implementable with the market leader SDKs (it is in their own interest when raising adoption). In early (specially not yet released) stages of the companion specification they sometimes contain bugs and glitches, which for prototyping is fine, but for creating real products is problematic.
if the NodeSet contains (and uses) Nodes that were defined in the later specification (e.g. 1.05.x) than the Modeler/SDK from 2015 (e.g. 1.04.y) is using internally, you will most probably have no luck.
Generally you should look into the change.log of SDK and Modeler, it states which Specification/Nodeset version the software supports. Furthermore you should not use different modeling tools, but instead stay within the tool set environment we provide for our SDKs. Reason is that we can not help and not support you when using different tools from other manufacturers including from OPC Foundation.
The working groups doing the companion specifications typically use our UaModeler for finally testing if the model is correct and working and implementable with the market leader SDKs (it is in their own interest when raising adoption). In early (specially not yet released) stages of the companion specification they sometimes contain bugs and glitches, which for prototyping is fine, but for creating real products is problematic.
Best regards
Unified Automation Support Team
Unified Automation Support Team