Unified Automation Forum

Hello,

In the new high performance Beta SDK,

The connection to server running on Raspberry Pi fails with
"Receive failed with 0x FFFFFFFD".

Could anyone help ?

My apologies if this is not the right forum group,

Thanks in Advance,
Praveen

Hi Praveen,

we need some more information on your system configuration.
1) can you ping the RPI (with name and with IP)?
2) are you running the host system in a virtual machine?
3) is the Server started correctly?
4) can you telnet the server's port?
5) have you changed the settings in server's config as described in getting started?

Best Regards
Support Team

Hi Support-Team,

I have the same problem and will answer your questions.
1) Yes, ping to IP and hostname works.
2) No, it's a RPi. I've tried to put it into my Domain Network and a private network (192.168.10.x) connected with my USB-Ethernet-Adapter (which works well for other applications)
3) The Server has started, but I'm not sure what you mean with correctly. It displays the message "Evaluation version: Running in demo mode (60 minutes)
4) I haven't tried telnet, since in Wireshark I can see that the server responds to a Hello message. On the server side there's the message "**** uatcpmsg_peer_recv_complete: Receive failed with 0xFFFFFFFD, Message 0x6922b8
In UAExpert shows the message: Could not connect to server: BadInvalidArgument
5) I've been following the instructions in tutorial_raspi.pdf (2016-03-21 Commit: e363d69). Can you guide me to the section where the changes in server config are described, I couldn't find them.

Hello,

due to another customer report with a Wireshark trace we could reproduce the issue.
This problem happens only when using an old UaExpert version (1.3), which expects a minimum revised Liftetime of 600000.
The server is revising a smaller value which leads the problem described above.
This was the missing information in the original post.

Simply update to the latest version 1.4.2 of UaExpert and the problem should go away.
The current version of UaExpert uses a smaller default limit of 300000 and you can configure the limit also via Settings->Configure UaExpert.
Filter: Lifetime

hint: you can better analyse such issues by increasing the trace level in Settings->Configure UaExpert...
Filter: Trace

Trace.StackTraceEnabled=true
Trace.StackTraceLevel=ALL
Trace.SDKTraceEneabled=true
Trace.SDKTraceLevel=Data

Then you should see the reason why UaExpert denies the connection.

Attached you find the Wireshark capture I sent to Unified Automation.
I was using UaExpert V1.3.1 206.