Pier-Yves Lessard

you're not having the same issue here. You server requires a timeout of 50ms, and the lib follows it. But 50ms is very tight for something that runs in pure...

This PR has been open for over a year. I guess we should close it?

Just to let you know that timing is being investigated right now. Most likely will be possible to achieve better timing from the pure python implementation of the isotp protocol

Hi @ziyangfu. Is it possible to try the latest isotp v2.x + udsoncan with branch support-isotp-v2 ? Use the isotp.NotifierBasedCanStack, like this ```python bus = VectorBus(channel=0, bitrate=500000) # Link Layer...

- isotp v2.x is release - udsoncan v1.21 is released These 2 should have better performances. I suggest to use a [NotifierBasedCanStack](https://can-isotp.readthedocs.io/en/v2.0.1/isotp/implementation.html#isotp.NotifierBasedCanStack). Will close as I believe it is fixed....

Should I close that?

Nice! I'm focusing on another project right now and have little time to dedicate to this one. I would gladly accept a PR (given that it is well made :)...

I think we should close this issue. broadcast is handled at the isotp level. ISO-14229 is not designed for multi-server support (as far as I understood from it).

Just to let you know that the pure python TransportLayer object now supports ``listen_mode`` which never sends flow controls. Will be available with v2.x release.

I'm looking into this now. Will be possible in v2.0