ISO15765

We experimented with changing FC parameters in can-isotp. can-isotp is highly complete. At least, it is much better than those vehicle diagnostic communication whose structure is broken.

We experimented with can-isotp request-response. SF-SF communication -> OK! MF-MF communication -> OK!

Most vehicle diagnostic communication is a single request-response communication. There are some exceptions such as request-only and response-only communication, but they are quite rare. Both the request and response sides are script fatted by the receive thread mechanism.

I changed the FC equivalent to change the behavior of can-isotp multi-frame requests. The behavior is now compliant with the specified STmin. The time parameters for communication are wide enough to allow for synchronization between systems. If it is more than 10[ms], we aim for 11[ms] to ensure that it meets 10[ms] or more.

In the default state of can-isotp, the DLC optimization specification is adopted. If you set padding and MIN_DLC in the parameters passed to CanStack, it switches to the padding specification.

The FC's add up in python-can. Supported by inserting CAN frames with a bit of timing in python-can. This allowed the multi-frame request to go through for now.

The Python package can-isotp can communicate ISO15765-2, or ISO-TP. However, python-can must also be installed due to dependencies. For now, SF (SingleFrame) transmission is possible. The multi-frame transmission stopped at FF (FirstFrame) and ended in an error. The protocol specification is that the next sequence cannot proceed unless FC is received after FF.