BadTimeout Error connecting to Frako PQM-1588 OPC-UA DA Server about opcua-asyncio HOT 10 CLOSED

you will need to record a session with wireshark both a working one (with uaexpert) and a not working one from python and compare them to try to catch any difference...

from opcua-asyncio.

Ok, I will try it with wireshark, but it is not so easy, because it's a customer system and I have not full admin rights on their system.
That output.dump file is generated with tcpdump from our gateway at the customer side.
I'll keep you posted.
Another try with your client_minimal.py example file was successfull. Not every time, but sometimes. So I think, may be, it is also a problem with the OPC-UA Server implementation on the PQM device.

from opcua-asyncio.

I thing tcpdump can dump in a Wireshark friendly format. But you need a session from uaexpert to compare

from opcua-asyncio.

I know, but I need the admin rights on their system to install and use wireshark for capture the UaExpert.

In my output.dump file I found out that everything runs good as far as time 0.833268 and the timeout comes 10 seconds later at time 10.835665.
The reason seems to be a UA Secure Conversation problem.

from opcua-asyncio.

OK. I did not see you attached the tcpdump already. That stuff looks strange. It is a simple read request and the server does not answer.... Can it be some network issue?
I think if it was a session timeout we would get an error messgae from server. Here it just stops sending things. looks like a network or server issue.... it looks like you will need to contact the supplier

from opcua-asyncio.

you can still record an uaexpert session and try to stop a difference if uaexpert works

from opcua-asyncio.

I will contact the supplier, because we can exclude a network issue.
Also interesting is that UaExpert, just the same, have also problem's very often.

from opcua-asyncio.

That's the Trace-Log from UaExpert
UaExpertTrace.log

from opcua-asyncio.

@elka0711 Any Progress on this issue? Did you hear back from the vendor/maker?

from opcua-asyncio.

I am assuming this problem was resolved or is caused by the server you were using. Feel free to open a new issue otherwise.

from opcua-asyncio.