Hello,

The printing “org.opcfoundation.ua.builtintypes.ExtensionObject” means that the client received an unknown structure from the server. So, it seems like the client is trying to access structure values that it doesn’t know how to decode.

Main question now is: what is the datatype of these values?

Also, when you read the history successfully with Prosys Android Client, are you reading the exactly same node? It’s interesting if the Android Client knows how to decode the values but your own client made with the same SDK doesn’t.

P.s. The NodeId definition new NodeId(0, 60057) looks strange as the namespace index 0 is the standardised OPC UA namespace and there should not be a node with NodeId 60057 in it.

P.p.s The “result” variable should always be DataValue[] and printing out result.toString() shows something like [Lorg.opcfoundation.ua.builtintypes.DataValue;@5d20e46. If you want to print out the DataValue Array in a human readable format, use

It seems I slightly misunderstood your first post. I missed the fact that you’re actually receiving an Exception.

To understand the situation better, we’ll need to see the full Exception message. Seeing the Exception.toString() output would be helpful, but actually the best information including a full stack trace is available if you do

and provide the stack trace to us.

The new error BAD_AUTHENTICATION seems pretty clear: there’s some authentication error which is probably not even related to OPC UA. However, the history read issue probably will persist after the authentication is sorted out.

Both UaExpert and Prosys OPC UA Android Client should make similar HistoryReadRequests with similar kind of ReadRawModifiedDetails parameter. There’s some minor differences in the parameters such as UaExpert using NumValuesPerNode=10000 by default. However, it’s interesting to note that using the ‘now’ timestamp causes the server to crash. This is pretty clearly a server side issue.

As a summary, there’s now multiple different issues in question which may or may not be linked together:

1) You currently receive some kind of Exception with message “BAD_AUTHENTICATION” when trying to call the UaClient.historyReadRaw method. Please check any authentication settings that the server in question requires.

2) In your original message, you mentioned that you receive an Exception (probably a DecodingException) when calling UaClient.historyReadRaw. Please provide the stack trace of this Exception so we can inspect further.

3) The server crashes if a certain kind of HistoryReadRequests is made with our Prosys OPC UA Android Client. According to my understaing, this is quite clearly a server issue and you should report this to the server vendor so that they can fix the implementation.