Log In
Register
Topic RSS
20:16, EEST
December 6, 2017
Offline
Hi,
Environment:
– Prosys SDK: 4.0.2-808
– Prosys OPC UA Simulation Server (v3.2.0-214)
+ The simulation server is configured with several data nodes (for each numeric data type one variable).
+ Checkbox “Run Simulation” is switched off.
– data to write to the OPC UA server: UnsignedByte value = UnsignedByte.valueOf(28);
Test 1.
– For each data nodes on the server run “writeValue(…, value, false).
– Result:
+ Only the data node with type “UNSIGNED BYTE” succeeded. For the others I got a StatusException: Bad_TypeMismatch.
+ The value on the OPC UA server has changed.
=> Test OK.
Test 2.
– For each data nodes on the server run “writeValue(…, value, true).
– Result:
+ For each data node “writeValue(…, …, true) succeeded.
+ But non of the data nodes on the OPC UA server has changed. (The data node with the correct type hasn’t changed too !)
=> Test FAIL.
I would expect the value 28 could be changed into every other numeric type and written to the data nodes.
The behavior is reproducible with other OPC UA servers too.
12:33, EEST
April 3, 2012
Offline
Hi,
Thanks for reporting the issue. Would seem to be a bug.
This will happen at least if the UaNode for the DataType of the node to be written is not fetched via AddressSpace.getNode before the writeValue is called. 4.0.0 changed on how the AddressSpace is initialized to fix some other issues, but seems it caused this as a side effect and our tests didn’t catch exactly this scenario.
Will be fixed for future version, before that you could try the following as a workaround:
client.getAddressSpace().getType(dataTypeId);
client.writeValue(…)
(not including error handling)
