車両診断通信 [CanTp] Vehicle Diagnostic Communication Part 39 [Simulation 27]
Click here for back issues. Introduction. Let's simulate ISO-TP. Series of.Continuation of the times to simulate.This ti...
Python
車両診断通信 
車両診断通信 [CanTp] Vehicle Diagnostic Communication Part 38 [Simulation 26]
Review of simulation configuration.
Code handling on the virtual ECU side.
Currently, it's private, give me a break.
Confirmation of communication logs of SF-SF, SF-MF, and MF-MF.
車両診断通信 [CanTp] Vehicle Diagnostic Communication Part 37 [Simulation 25]
Fixed the script for Python can-isotp requests.
The request is now ISO14229-1 compliant.
Implemented AUTOSAR-CanTp side.
The response is now SO14229-1 compliant as well.
The code has not been published yet for personal reasons.
車両診断通信 [CanTp] Vehicle Diagnostic Communication Part 26 [Simulation 14]
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.
車両診断通信 [CanTp] Vehicle Diagnostic Communication Part 25 [Simulation 13]
We experimented with can-isotp request-response.
SF-SF communication -> OK!
MF-MF communication -> OK!
車両診断通信 [CanTp] Vehicle Diagnostic Communication Part 24 [Simulation 12]
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.
車両診断通信 [CanTp] Vehicle Diagnostic Communication Part 23 [Simulation 11]
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.
車両診断通信 [CanTp] Vehicle Diagnostic Communication Part 22 [Simulation 10]
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.
車両診断通信 [CanTp] Vehicle Diagnostic Communication Part 21 [Simulation 9]
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.
車両診断通信 [CanTp] Vehicle Diagnostic Communication Part 20 [Simulation 8]
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.