Type of issue

• Bug
• Enhancement
• Compliance
• Question
• Help wanted

Current Behavior

In case a method call returns any other status than Good the default implementation of MethodState will not assign the outputArguments values. This behavior is not conforming to the specification as defined in OPC Reference - Part 4 - StatusCodes. In the case of a return value of Uncertain the output arguments should get assigned as well, since the application specific return values need to be evaluated on the client side.

The cause can be found at: MethodState.cs - Line 709. This should also include Uncertain as a return value.

A related issue can be found at CustomNodeManager2 - Line 3088. Here should not a general Good be returned since the Uncertain case cannot be addressed this way.

Expected Behavior

The output arguments values should be assigned in the Uncertain case as well as for the Good case.

Steps To Reproduce

1. Define a nodeset with a method call which returns values through the outputArguments
2. Create a server with the nodes defined in the nodeset
3. Issue a method call, assing the outputArguments and return StatusCode.Uncertain from that call as a return value.
4. Expect the client to receive the output arguments if the StatusCode.Uncertain was returned.

Environment

- OS: win, linux
- Environment:
- Runtime:
- Nuget Version:
- Component:
- Server:
- Client:

Anything else?

No response