-
Notifications
You must be signed in to change notification settings - Fork 13
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
Writing to write-only variables fails #141
Comments
Interesting. I have never seen a write-only variable before. That will need some effort... Things I see in your configuration:
How should we get the right definition of the OPC UA data type, if the node is not readable? Does a client like UA Expert still show the type? |
I know these are the defaults - just saying that these defaults will not work for write-only variables, as they configure the client to read at connection-up and set up a monitor. Ok. |
The only things uaexpert logs for this are:
|
"Read attributes" - sounds good. |
Found it. I need to use the browse (introspection) interface of the server to do that. That gets me access to all the attributes of a node without reading the value. Up to now I was just reading the value, which also gets me the data type. |
Maybe do that only if initialRead fails because of BadNotReadable? |
Yes. Otherwise I would have to always add a lot of OPC UA traffic just to cover that rare case. |
We have an OPC UA server with some write-only variables.
Writing to them causes the error message:
unsupported conversion for outgoing data
The data type is Null. This type is deduced from
incomingData
, which of course had not been set during startup, because the variable is not readable. See also:status=BadNotReadable.
The text was updated successfully, but these errors were encountered: