Hi,

Thanks for the note.

It wont work for arrays (autoConvert=true, I mean). It can be categorized as a bug, sort of (skipping details for now), and is probably fixed in a future version (i.e. there would have been nothing to convert in this case so it should not fail).

Is there a reason you need the autoConvert=true here? Basically you could just use false there or use the writeValue(NodeId nodeId, Object value).

Can you tell what is the ValueRank and DataType Attributes of that node? (And we might need to continue via email if you show them via screenshots etc.)

Basically if it is ValueRank of 1 i.e. 1-dim array, and the DataType is i=4 i.e. “Int16” i.e. in Java Short, the DataValue you read (as you said you read and then write it back) should contain a Variant that contains a Short[] (the boxed type, primitives are not used in the SDK in the value mappings), thus you would then write that same Short[] back and that should work. This is assuming there is not an error in the server that it would return wrong datatype’d Value.

Maybe I was a bit confused since you mentioned “Trying to write the same value back” so I assumed you would have already have the data in the correct type.

Technically you can get the type mapping at runtime via client.getAddressSpace().getDataType(DataTypeId here).getJavaClass() if you must make a new array dynamically. Though note that it is the scalar type (and that you must give it the node’s DataType Attribute’s value, i.e. the NodeId of the DataType, not the node to which you are writing) (basically this is the issue at the moment why the array conversions fail). Though, NOTE, we did release 4.9.0 last week https://downloads.prosysopc.com/opcua/Prosys_OPC_UA_SDK_for_Java_4_Release_Notes.html#version-4-9-0 and that functionality was made better, but requires changes if you looped supertypes before).

And I guess a Integer[] -> Short[] conversion could be useful in the future as using shorts in java code can be a bit clunky.