UaModeler does not generate all code

Questions regarding the use of UaModeler

Moderator: uamodeler

Post Reply
elaukkan
Jr. Member
Jr. Member
Posts: 1
Joined: 21 Feb 2011, 09:23

UaModeler does not generate all code

Post by elaukkan »

Hello,

I'm trying to model a Metso valve with UaModeler. I've modeled the valve as a subtype of DeviceType, and added new BlockTypes (Transducer, AnalogOutput, Resource and PIDController) according to OPC UA DI Specification and the user guide of the valve. I've also added some parameters to the ParameterSet by using the Override-button in UaModeler.

Here is a picture of the type structure in UaModeler:

[img width=150]http://dl.dropbox.com/u/18898677/device-type.png[/img]

However, when I create an instance of the device to the UaModeler, ParameterSet-objects disappear from the BlockTypes. Also reference to the MetsoBlockType has disappeared from the SupportedTypes-object.

Here is a picture of the device instance in UaModeler:

[img width=150]http://dl.dropbox.com/u/18898677/device-instance.png[/img]

When I generate the code for Visual Studio 2010 with 1.3.0 template set for CPP Server, more information disappears. There are no blocks generated below Blocks-object.

Here is a picture of the device instance when viewed with UaExpert:

[img width=150]http://dl.dropbox.com/u/18898677/device-client.png[/img]

I've used the hello world example project from the C++ SDK as a base for the project, and edited the following lines to match our generated code:

Code: Select all

		// Add generator for node manager
		ms::NodeManagerMetso* pNodeManager = new ms::NodeManagerMetso(true);

		pServer->addNodeManager(pNodeManager);
UaModeler project files and generated code at http://dl.dropbox.com/u/18898677/metso-project.zip

User avatar
Support Team
Hero Member
Hero Member
Posts: 3068
Joined: 18 Mar 2011, 15:09

Re:UaModeler does not generate all code

Post by Support Team »

Hello elaukkan,

The UaModeler 1.1.0 does not support adding optional components to instances. Since ParameterSet is optional, it is not added to the instance. UaModeler 1.2.0 will support adding optional components.

Adding components to an instance of ConfigurableObjectType is not supported by the current templates of the UaModeler. As a workaround you can add a new subtype of ConfigurableObjectType and use this type in MetsoValveType with the chosen blocks as children for the Blocks element.
[img width=330]http://www.unified-automation.com/image ... kstype.png[/img]
The

Code: Select all

addSupportedType
has to be added in code, the UaModeler will not generate this.
Best regards
Unified Automation Support Team

UAIFT
Jr. Member
Jr. Member
Posts: 2
Joined: 10 Jan 2012, 09:42

Re:UaModeler does not generate all code

Post by UAIFT »

Hello,
do you know the release date of the new UaModeler?

regards

User avatar
Support Team
Hero Member
Hero Member
Posts: 3068
Joined: 18 Mar 2011, 15:09

Re:UaModeler does not generate all code

Post by Support Team »

It is planned to release the UaModeler 1.2 4-6 weeks after OPC UA 1.02 specification release together with the Cpp Server SDK. The OPC UA 1.02 specification is currently in the final voting with expected release date mid/end of April 2012.

Best Regards,
Support Team
Best regards
Unified Automation Support Team

Post Reply