Opened 5 years ago
Last modified 3 years ago
#5764 assigned defect
OPC UA seems to miss DataType at the nodes attributes
Reported by: | anonymous | Owned by: | Martin Sjölund |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | *unknown* | Version: | v.1.15.0-dev |
Keywords: | Cc: |
Description
Hi,
just played around with the OPC UA Server in OpenModelica and tried to connect with different clients (UA Expert, Beckhoff TwinCat PLC OPC IO, Android Suppanel) to a simple model (Just a sine source, a resistor and ground). Connection to the OPC-UA server works fine and in UA Expert I can set values and watch variables changing.
But there seems to be something broken between version 1.12 and 1.13+. The OPC clients can't reliably determine the datatype for the attributes presented by the OPC-UA server. UA Expert may work around that somehow, but the other clients I tested, reject using the variables - due to the missing variable information?
Please see the following screenshots:
Change History (10)
comment:1 by , 5 years ago
Milestone: | Future → 1.14.1 |
---|
comment:4 by , 5 years ago
Replying to casella:
@sjoelund.se, any chance to fix this in 1.14.1?
Thanks!
Thanks for taking care. Would love to test a hotfix as soon as it is available... As nightly?
follow-up: 6 comment:5 by , 5 years ago
Of course we could first get this into the latest 1.16.0-dev nightly, then cherry-pick it for 1.14.2 (1.14.1 has already been tagged)
comment:6 by , 5 years ago
Replying to casella:
Of course we could first get this into the latest 1.16.0-dev nightly, then cherry-pick it for 1.14.2 (1.14.1 has already been tagged)
If this is possible, I would appreciate. Just let me know when it's ready so I load it and test it with Beckhoff TwinCat...
comment:7 by , 5 years ago
Milestone: | 1.14.1 → 1.16.0 |
---|---|
Owner: | changed from | to
Status: | new → assigned |
@sjoelund.se, any chance to fix this for 1.16.0?
comment:9 by , 4 years ago
Milestone: | 1.17.0 → 1.18.0 |
---|
Retargeted to 1.18.0 because of 1.17.0 timed release.
@sjoelund.se, any chance to fix this in 1.14.1?
Thanks!