Thanks for the note. We'll try to fix that in the future.

I just installed Prosys OPC UA Client 2.9.1 on a Motorola G8 (Android 11). Google play refused to install it, so I downloaded the apk manually and forced the installation.

AFAICT, the program works fine. The only issue I had is a bug when calling a method with two arguments.

In my server I have the method "ForceDigital" that takes "channel" (a String) and "value" (a Boolean) as arguments. From the logs it seems the client always overrides the first argument with the second. For example, if I set "channel" to "My channel" and "value" to 1, it passes "1" and 1 to the server. Similarly, when using "Another channel" and 0 the server receives "0" and 0.

Thank you in advance.
--
Nicola

That works perfectly! Thank you for your assistance and passing on your knowledge.

Prosys OPC UA Client for Android can be configured to send its certificate by checking the "Secure connection" checkbox when creating new or editing existing connections. When the checkbox is checked, the Client will attempt to connect using MessageSecurityMode Sign&Encrypt and SecurityPolicy Basic128Rsa15.

Note, that Basic128Rsa15 has been deprecated in OPC UA Specification version 1.04 and the Kepware KEPServerEX might not support it. This was the common SecurityPolicy when the application was created.

You might also have to configure the Kepware KEPServerEX to trust the Andoid Client's certificate before you connect using it.

I have managed to figure this out now. I'm a bit embarrassed that i didn't figure it out earlier!

So within Wireshark, there was nothing when trying to connect using the hostname, however when i changed the hostname to the IP address and tried to connect i could see the connection attempt. I could then see in the opensecurechannel message that android device wasn't sending a certificate, which the opc server is requesting. As the android app doesn't send a certificate i set the OPC UA Configuration server endpoint to allow no certificates and the app now connects.

Thank you for your assistance on this issue.

A follow up question - Do you know of a way for the android app to send a certificate to make the connection secure?

Have you tried to "ping" the TCP port of device running the Kepware KEPServerEX from the device running Prosys OPC UA Client for Android? There seems to be a tool for this, though we haven't tested it personally: https://play.google.com/store/.....#038;gl=US

You could also try to enter the hostname and the port of the Server to a web browser on your Android device in the following form: "hostname:port". If you see a TCP error message, it means that the port replied. Otherwise, you would just see a generic unable to connect error message.

Being able to regularly ping the the device but not connect to the Server would suggest that there is a firewall between the devices that is blocking the TCP ports used to connect to the Server. Have you checked the firewall settings on the devices running the applications and verified that the TCP ports they would use have not been blocked?

Thank you for the replies.

Using the PingTools app i can ping the server from the android device.

The Prosys OPC UA Browser is on a different machine to the KEPServerEX and as mentioned does connect fine.

I have installed Wireshark onto the server and the only device i can see connecting through the OPC port is the machine with the Prosys OPC UA Browser installed. Nothing from the android device.

You could also use Wireshark on the device running the KEPServerEX to capture traffic between it and the Client applications and check if the Server is receiving any messages from the Clients. See https://www.prosysopc.com/blog.....wireshark/ for instructions on how to capture OPC UA communication with Wireshark.

Have you confirmed that the devices running the applications are connected to each other? Have you tried pinging the device running the KEPServerEX from the device running the Prosys OPC UA Client for Android?

For example, you could try pinging with the following application: https://play.google.com/store/.....#038;pli=1

Thank you for the reply.

Apologies for the confusion, no they are not on the same host. I incorrectly typed localhost rather than hostname, which is in the form machine.domain.local. I have tried both the hostname and the IP on the app but neither work.

The error message i get on the app is 'Connection failed, check your network connection'.

Are you running the Kepware KEPServerEX and the Prosys OPC UA Client for Android on the same host? Since you mentioned that you're using "opc.tcp://localhost:49320" as the connection address, this would imply that you're attempting to connect to a Server that is running on the same host as the Client. Otherwise, you would have to replace the "localhost" part of the connection address with the hostname or the IP of the device running the Kepware KEPServerEX.

If you are running them on the same host or have modified the connection address appropriately, can you provide more information on the connection problem, e.g. error messages from the Prosys OPC UA Client for Android or the Kepware KEPServerEX?

I have a Kepware KEPServerEX which i can connect to through the Windows Prosys OPC UA Browser using opc.tcp://localhost:49320, however i cannot connect to it using the OPC UA Client for android using the same Uri. The app connects fine to the Prosys OPCUA Demo Server.

Does anyone use the app to connect to a Kepware KEPServerEX? Or have any suggestions on what to try?

Thanks.

If DataType is Double, it should in fact accept all values. If it requires Double, it should use DataType=Double. As you have noticed, UA Browser is clever enough to allow you to choose the actual datatype that is being written. I am afraid that the Android Client at the moment simply writes the value as string, expecting that it's valid as well.

AccessLevel should also be configured with CurrentWrite bit set, if it allows writes, but it seems that the server does not really care about that. It just gives wrong information.

As far as I can tell, the DataType is simply showing as "BaseDataType"--from this, should I assume that means that the server is not properly identifying it? I am able to read the values correctly/accurately, if that counts for anything (though I suspect...not particularly). The variable I am writing to should be able to accept a double and is a valid input, but any value I attempt to write ("0", "1", "0.0", "1.5", etc.) simply give the same error.

I can't see a way to attach a picture, so to describe two screens by text:
When I try to write to a variable, I get the "Write value" popup, which prompts me for "New value:" and then has a field I can type into, followed by "Cancel" and "Write" buttons. I am not sure how to verify if it has a "proper value when I am writing", as I'm not certain how to verify if my value is "proper"--it definitely is a valid value for the variable to take, and when I try to write to it, the variable is showing a reasonable value at that time, too.

When I view the attributes of the variable, it shows:

AccessLevel-------------CurrentRead
ArrayDimensions-------Null
BrowseName------------{A value, I believe not relevant}
DataType-----------------BaseDataType
Description---------------
DisplayName------------{A value, I believe not relevant}
Historizing----------------false
Min.SamplingInterval--0.0
NodeClass----------------Variable
NodeId---------------------ns=2;s={A value, I believe not relevant}
UserAccessLevel-------CurrentRead
UserWriteMask----------
Value-----------------------{The correct value, currently an integer}
ValueRank----------------Any
WriteMask-----------------

(Dashes added for clarity. No values show as "negative"/start with dashes, and a few lines do not seem to show a response)

The two things that jump out at me are the "BaseDataType" (which may be incorrect/might need to return Double?) and the AccessLevel/UserAccessLevel of "CurrentRead" (which might imply that it is not intended to be written to? Though again, the same variable can be written to from the desktop app if I specify write as double).

In general, the client writes the values in the DataType defined by the server. if you need to specify the DataType in Browser, it means typically that the server is not doing that right. And I am afraid that the Android Client does not enable custom data type definition when writing values to overcome this.