Hello,
are the xml files that can be generated with your modeler compatible with the ModelCompiler of the Opc foundation?
Is it possible to generate for example .cs files for the foundations .NET Stack with their ModelCompiler using UaModeler generated xml files?
Thanks in advance!
Best regards.
Compatibility with Opc foundations ModelCompiler
Moderator: uamodeler
-
jul
- Jr. Member
- Posts: 3
- Joined: 30 Sep 2015, 12:19
-
Support Team
- Hero Member
- Posts: 3068
- Joined: 18 Mar 2011, 15:09
Re: Compatibility with Opc foundations ModelCompiler
Hello,
we don't know which import format the OPC Foundation supports. But our UaModeler supports the NodeSet2XML format that is specified. The UaModeler can import such models and the UaModeler can export such Models in same NodeSet2XML format (license required), even though we recomend using the UaModelers project file binary format for storing and loading the Model, because it is much faster.
The code generated by UaModeler will only work in our Unified Automation SDK (C, C++ or .NET), but not in the .NET SDK of the OPC Foundation nor any other company's code base. There is no reason to use the ModelCompiler of the OPC Foundation, if you decide for the sophisticated SDKs and tools from Unified Automation.
Best Regards
Support Team
we don't know which import format the OPC Foundation supports. But our UaModeler supports the NodeSet2XML format that is specified. The UaModeler can import such models and the UaModeler can export such Models in same NodeSet2XML format (license required), even though we recomend using the UaModelers project file binary format for storing and loading the Model, because it is much faster.
The code generated by UaModeler will only work in our Unified Automation SDK (C, C++ or .NET), but not in the .NET SDK of the OPC Foundation nor any other company's code base. There is no reason to use the ModelCompiler of the OPC Foundation, if you decide for the sophisticated SDKs and tools from Unified Automation.
Best Regards
Support Team