Custom structure as InputArgument of method

[AndreyKl4]

Hi all!

I have faced such problem: I created a custom data type with help data type definitions. After that I used custom data type as InputArgument of method. I found out that it works only in case when I set up argument as an array:
arg.ValueRank = 0
arg.ArrayDimensions = [].
But, actually, i need to use my Argument as Scalar with ValueRank = -1. When i set up ValueRank = -1 it displays incorrectly.
Perhaps I understand smth incorrect, when we use data type definitions we get an array of fields and that is why i have to use ValueRank = 0 instead of ValueRank = -1 ?

Thanks in Advance!

Andrii Klimov

[AndreasHeine]

have you seen this? https://github.com/FreeOpcUa/opcua-asyncio/blob/master/examples/server-extension-object-as-method-argument.py

[AndreyKl4]

@AndreasHeine yes i have. It was first what i looked at. In my case it dispalys incorrectly ...

[AndreasHeine]

you wrote "...displays incorrectly."

could you tell me what you try to setup? MethodInArgs? MethodOutArgs? What is actually wrong or appears wrong?

[AndreyKl4]

I tried to set up MethodInArg in this case. Idea was to create a custom datatype(see screenshot 1 and 3) and use it as MethodInArg as Scalar(ValueRanks = -1) but not as an Array(ValueRank = 0) of such datatypes... When I try to set up it as Scalar a I get (see screenshot 2) but i want to get(see Screenshot 1) but not an Array... Perhaps, I do smth wrong...

[AndreasHeine]

MethodInArg is always an Array of Args even if it is only one

https://reference.opcfoundation.org/v104/Core/docs/Amendment3/5.7.3/

inputArguments []	BaseDataType	List of input argument values. An empty list indicates that there are no input arguments. The size and order of this list matches the size and order of the input arguments defined by the input InputArguments Property of the Method.The name, a description and the data type of each argument are defined by the Argument structure in each element of the method’s InputArguments Property.If a Method has optional input arguments, these optional input arguments are indicated by the Method’s DefaultInputValues Property. In this case fewer arguments than the total number of input arguments defined may be passed by the Client. The InputArguments and DefaultInputValues Property are defined in Part 3.

[AndreasHeine]

if you cant share the sourcecode send me an email!

[AndreyKl4]

@AndreasHeine thanks for your help. I have send u an email