Pier-Yves Lessard
Pier-Yves Lessard
@jagauthier : I think the flow control timing is not the issue here. You seem to be missing data for real. The data ends at 57 which is W not...
Hi, it is not possible to do so right now. A quick workaround would be to convert the 29 bits ID to an arbitrary 11bits ID that the stack will...
Hi, there seems to be no graceful solution to this that won't break the interfaces. I will come up with something, but it may take some time. Sorry if there's...
What is the issue? You posted a solution with no problem
It's a common problem. There are several similar issues. I do not know the can.notifier object, but it must be consuming the data, leaving nothing for the TransportLayer If the...
So I read about notifiers and they seem to do exactly that. The CanStack object should register a Listener instead of reading directly the bus object and consuming the buffer...
It's a mistake. It should be didconfig. Will fix soon
Hi, Your integration with python-can is wrong. IT has multiple problem. First, the txfn,rxfn parameter of the TransportLayer have a signature requirement that is not directly compatible with PythonCan. Also,...
Just to let you know that isotp v2.x will be released soon and the possibility of doing a blocking send has been added. This will allow starting the timer at...
isotp v2.x has been released. and udsoncan 1.21 supports it. using the new parameter from isotp v2.x `blocking_send=True`, this issue should be resolved. I am still wondering if I should...