in my opcua driver i use the datatype ubyte (i think this this was new introduced in 7.5).
Now i updated my testsystem to 7.5.4beta1 and get the following error when i try to add a opc tag with this datatype:
java.lang.ClassCastException: Cannot coerce value '[Ljava.lang.Byte;@1e190e2' into type: class java.lang.Byte
I’m sure this worked in one of the previous 7.5 versions. Is the 7.5.4 api incompatible with 7.5.3 or is this a bug?
Can you give me a little more context? What does the surrounding code look like? I know there were a few attributes like AccessLevel on UA nodes that were modified to require unsigned byte instead of byte’s as per the spec.
The error you’re showing me looks like an error casting a Byte into a Byte, which seems a little unrelated.
Thank you very much, this was an error on my side. The byte was the clue. I dragged an opc array item from the OPCBrowser to the SQLTags Browser, and did not remember that it was an array .
Is my memory wrong, or did Ignition automatically create a string tag for arrays in earlier versions?
At some point it may have created a useless string tag that had the contents “[Ljava.lang.Byte;@1e190e2” or something like that… I can’t remember exactly.
Adding support for arrays has been on our list forever, it just hasn’t ever been a high enough priority to actually get done.
When i manually change the datatype of the created tag to string, it works perfect. The string then contains the comma seperated values and can be evaluated with a split expression, so it actually is usefull.
Thanks again for your fast help.