Closed stanislavZemek closed 3 months ago
There's a parameter for a global timeout that overrides all the other. It just make sure that the client does not block indefinetely, you can set it to None
. The error message does not mention P2 nor P2*, but Global request timeout time has expired
You either set it here : https://udsoncan.readthedocs.io/en/latest/udsoncan/client.html#request_timeout Or you pass it to the client constructor.
Hello Pylessard,
thank you for your help. I've overlooked parameter in client configuration... There was a parameter left from the example I used and I forgot about it. :facepalm: Now it works properly. :ok_hand: Have a nice day!
Standa.
Hello Pylessard,
sorry to bother you again. I don't know what I am doing wrong, but I have another issue with timing of messages. :facepalm: :smile: When I have sent a routine request to erase memory on my server, my server had started erasing. During memory erasing, the server sent NRC with code 0x78. Firstly it is sent within P2max and another one is sent within P2time. Despite sending NRC 0x78, the server only accepts this message a few times or not at all (it depends on the length of P2time) and the udsoncan is stopping accept NRC 0x78 after 1.658 seconds which have elapsed from the request. Below you can find two examples of communication. Thank you for your time.
*Example of P2time == 1.0s:**
PHYSICAL COMMUNICATION:
*Example of P2time == 3.0s:** DEBUG:
PHYSICAL COMMUNICATION: