[
https://issues.apache.org/jira/browse/PLC4X-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126051#comment-17126051
]
Matthias Milan Strljic commented on PLC4X-202:
----------------------------------------------
I agree with you. But i am also from the opc front so there would be some
additional input required.
The OPC UA driver implicitly uses the transferred type as node type. For the S7
and Modbus protocols the type is declared explicitly within the address. The
most elegant solution would probably be to achieve compatibility between the
next larger type, such as with ushort --> int and with uint --> long. This way,
the current examples of the other protocols could continue to be used and
fluently establish the new own plc4x-utypes?
What do you think [~cdutz] [~jfeinauer] ?
> OPC-UA Driver cannot write Unsigned Types
> -----------------------------------------
>
> Key: PLC4X-202
> URL: https://issues.apache.org/jira/browse/PLC4X-202
> Project: Apache PLC4X
> Issue Type: Bug
> Components: Driver-OPC-UA
> Affects Versions: 0.7.0
> Reporter: Alessandro Rossignoli
> Priority: Major
>
> Currently, unsigned types are not supported in writing direction from the
> driver although they are fully supported by Eclipse Milo and in reading.
> Actually I have applied a modification and tested it to be able to support
> these types. It is kind of the same patch applied for BigIntegers but done
> introducing UShort and UInteger from Eclipse Milo.
> The downside is that every driver will use the Eclipse Milo types, being the
> JVM missing unsigned types. I don't know if you have a better solution or if
> using Milo types in all the drivers is acceptable for you.
> I am open for suggestions :)
>
> (PS. when I will complete all the testing I will create 3 separate PR for
> issue #200, #201 and this one)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
