Hi, Kevin,
Thanks for the quick reply. Here is the response from the server captured by Wireshark. Seems like, as you mentioned it, it is returning a bunch of extra characters, this was tested both in a real
and a simulated SIMOTION, obtaining the same results.

From: milo-dev <milo-dev-bounces@xxxxxxxxxxx>
On Behalf Of Kevin Herron
Sent: Thursday, September 23, 2021 3:57 PM
To: milo developer discussions <milo-dev@xxxxxxxxxxx>
Subject: Re: [milo-dev] Wrong value when reading a String
I do wonder if it's as simple as UaExpert deciding to stop displaying after the first null 0x00 byte it encounters, though. It certainly looks like this server is just returning a bunch of extra crap in the String value.
That's pretty strange.
Can you get a Wireshark capture that contains the Read request/response? You'll have to connect without encryption for the capture to be usable.
I'm going to be gone and without phone or internet service for a few days so I likely won't be able to look at this right away.
Hi everybody,
I’m having some issues when reading a variable from a SIMOTION device, it’s a String that can be correctly read using UaExpert:

However, when I read it using milo I get a byte array with 510 positions that contains the original value, but also some random bytes that cause the String to
come with some wrong ASCII values:

What could be the cause of it? It happens only with the factory set values of the SIMOTION, with custom ones I have no issue at all.
Thank you in advance for your help and support.
Daniel Moreno
_______________________________________________
milo-dev mailing list
milo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/milo-dev
|