-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Method call with arguments #29
Comments
Hello, Always glad to see that my work has been useful. Perhaps the OPC UA documentation on method call modelling in the UA namespace has more information for semantic correctness but I've never needed it. On the client side, you have: On the server side, look at: I haven't implemented a standard way of handling these on the server side, but look at #23 as one way to do it. CallMethodRequest is defined as
So the parameters are just an array of objects encoded as UA variant types. You don't need to define them yourself. As a client, just populate them as you wish (i.e. array of integers boxed as objects), and as a server, decode them as an array of variant types. |
Dear @nauful, How would you return OutputArguments in this case? |
OutputArguments can be returned to the caller in this way (last part): #23 (comment) Off the top of my head, it should be similar to this:
|
Dear @nauful,
Thank you again for your freely available code!
Regarding the server implementation:
I'm currently trying to support InputArguments/OutputArguments for a NodeMethod, which I added successfully according to #23.
I was able to add the reference nodes to my NodeMethod "method":
However, I don't know how to add, for example, a string InputArgument to "method".
I just found the "Argument = 296" definition in Types.cs but I think I lack understanding how to add InputArguments here.
Any advice is very much appreciated.
Thank you very much!
The text was updated successfully, but these errors were encountered: