[
https://issues.apache.org/jira/browse/PLC4X-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126066#comment-17126066
]
Matthias Milan Strljic edited comment on PLC4X-202 at 6/4/20, 4:49 PM:
-----------------------------------------------------------------------
[~itaross] you right i also see there the same issue. That is just because i
tried to stick with the OPC naming string with --
{code:java}
"ns=2, [identifier]=[value]{code}
wihtout any type informations. This was fine for just reading the values and
write the basic types. But ofc we have then the issue of identify the unsigned
types. For that we have just the options to stick with the implicit definition
over the type like milo does it or add it into the address string pattern. At
the moment it would be more consistent in the plc4x collection to add it to the
address string which would conflict in the way opc ua usually declares the
nodes via the id-string
was (Author: nalim2):
[~itaross] you right i also see there the same issue. That is just because i
tried to stick with the OPC naming string with --
{code:java}
"ns=2, [identifier]=[value]{code}
> 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)
