Papyrus OPCUA manuals/training

[alexmc1510]

Hello all,

I have been playing with Papyrus OPCUA plugin and it seems promising. After checking other tools like UA modeler or FreeOPCUA, I like the power of Papyrus for modelling my industrial assets in combination with existing CS. The thing is, as a newby in Papyrus and of course in OPCUA pluging it has been difficult to me to understand how everything works and evaluate the tool also for scalability purposes. I am not able to find any manual or tutorial in any website and I would like to ask to the community if someone could help me to understand the tool or if someone has a manual. Of course first coffee is on me.

Thanks in advance

[epsilon-0311]

Hi,

there isn't much of a tutorial or manual except what you can find in the wiki tab.
If you have questions or need help feel free to ask them here or in the discussions tab.

[alexmc1510]

Hello, thank you for the quick answer. To be honest I don't know how to start the process of creating a simple information model like the one in the picture...

When I try to start, I have the following questions:

1. How to import an existing xml nodeset
2. How to import CS to be used as base specification (UA + DI + ...)
3. Add new type of objet in my new namespace linked to an existing object in CS
4. Is there a kind of data dictionary for managing semantics in a tabular manner?

I would not mind to create a manual or tutorial with the answers to be shared in the community. I think a lot of people would appreciate it.

Regards

[epsilon-0311]

1. An existing NodeSet model can be imported as described here: https://github.com/model-UA/papyrus-opcua-plugin/wiki/first_steps#importing-nodeset

2. and 3. I'm currently not familiar with the abbreviation CS you use. Could you explain what you mean with it.

3. There is not such a view implemented, only the graphical view is available

The creation of further manual/tutorial entries would be really nice of you.

[alexmc1510]

Hello, thank you for your answer.
CS means companion specification. Here you have some examples: https://github.com/OPCFoundation/UA-Nodeset
An for importing an existing nodeset, I was looking for importing the xml, not the UML.

Thanks in advance

[epsilon-0311]

Ah yes Companion Specifications, I should have thought of this.
Companions specifications typically get distributed via the plugin itself, but we only added the safety extension until now. What you can do is to create a new model and use the update nodeset functionality. The resulting model can be imported in other models then.

This is the same process we use to add new Companions Specifications.