consultancynsa.blogg.se - Prosysopc uaclient to kepware

Of course you could just write the NodeSet2.xml file manually. It includes naming conventions and other helpful tips: The OPC Foundation released a Whitepaper describing best practices for information modelling. For a dog one can optionally also define a weight. For the sound we define a custom datatype which represents a structure with two fields: the sound verb as per the Wikipedia article and a URL to a sound file.

Every Mammal has a specific number of legs, and a sound.

In our simplified world, every Animal should have a name.

AnimalSoundType (Structure with Verb and URL to Audio file).

This includes defining our own animal types, and even defining instances of animals. In this tutorial we want to create our own (simplified) companion specification for animals.

3 Create your own Model.xml template fileīefore creating your own information model you should already have a rough idea what information this model should contain.

2.2 Beeond UMX Pro – UA Model eXcelerator ProfessionalUA Modeling eXcelerator (UMX).

2.1 Unified Automation UaModeler and Free OPC UA Modeler.

The following sections lead you through these steps.

Load the NodeSet2.xml file into an OPC UA Implementation which supports initialization by NodeSet2.xml files.

In addition to the NodeSet2.xml Format, the model compiler also outputs some more files which may be required by other tools.

Use the UA-ModelCompiler to convert the Model.xml file to especially the transportable NodeSet2.xml Format.

Then you need a tool or you manually write the Model.xml File.

The basic pipeline is sketched in the following diagram: That file can then be used to automatically initialize an OPC UA Server which supports loading that file format.Īll the files and tools used in this tutorial are also available here:Īn example OPC UA Server which is using this Information model is shown here:

The goal for this tutorial is to come from a mind-model to the final NodeSet2.xml format. This file contains all the nodes and references between the nodes inside this specific information model. A Tutorial on how to create your own custom information model is described in this chapter.Įvery custom information model or companion specification should be delivered as the official NodeSet2.xml format. This address space can be extended by custom information models. This post gives you a quick introduction into creating custom OPC UA Information Models.Ī more complete tutorial, including explanations how to configure your editor and the open62541 stack, and then compile your custom information model up to a fully running OPC UA server is given in:įrom modelling to execution – OPC UA Information Model TutorialĪs explained in my previous post, OPC UA organizes all the nodes inside an address space: