[CAN-FD] Vehicle Diagnostic Communication Part 88 [python-can 2]

Click here for back issues.
https://www.simulationroom999.com/blog/diagnostic-communication-en-back-issue/

Introduction.
can.player and can.logger
Asc files for replay in CAN-FD and CAN Mixed
Conclusion

Introduction.

Explanation of CAN-FD simulation in python-can.
This article will explain how to create an asc file for can.player.

can.player and can.logger

You may want to review can.player and can.logger in the following article.

Asc files for replay in CAN-FD and CAN Mixed

Let’s use the following asc file for replay in can.player.

Begin Triggerblock
 0.000000 Start of measurement
 0.000000 CANFD   1 Rx 111 1 1 d 8 11 22 33 44 55 66 77 88
 0.001000 CANFD   1 Rx 222 1 1 d 64 21 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79
 0.002000 CANFD   1 Rx 333 1 1 d 64 22 7A 7B 7C 7D 7E 7F 01 0A 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36
 0.010000 1  111    Rx         d 8 11 22 33 44 55 66 77 88
 0.011000 1  222    Rx         d 8 11 22 33 44 55 66 77 88
 0.012000 1  333    Rx         d 8 11 22 33 44 55 66 77 88
 0.020000 CANFD   1 Rx 111 1 1 d 8 11 22 33 44 55 66 77 88
 0.021000 CANFD   1 Rx 222 1 1 d 64 21 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79
 0.022000 CANFD   1 Rx 333 1 1 d 64 22 7A 7B 7C 7D 7E 7F 01 0A 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36
 0.030000 1  111    Rx         d 8 11 22 33 44 55 66 77 88
 0.031000 1  222    Rx         d 8 11 22 33 44 55 66 77 88
 0.032000 1  333    Rx         d 8 11 22 33 44 55 66 77 88
End TriggerBlock

As you can see, I have mixed CANFD and CAN formats.
The reason I’m mixing CAN is for detecting patterns that are not connected to the line.

I plan to determine the following feeling.

If there is no CAN, it is not well connected.
If there is no CAN-FD and only CAN is obtained, the line is connected, but the CAN-FD is not being transmitted or not being received.

I’ve never done this before, so I’ll have to put in a lot of tricks to determine if there is a problem.
Last time it was easy to check with BusMaster, which has a proven track record of working, but this time I don’t have a system I can rely on.
The more tricks we have, the better.
(I’m very wary.)

Conclusion

Review can.player and can.logger.
Created asc file for CAN-FD and CAN mixed replay.
- Mixed CAN is for identifying the affected area in case of an anomaly.

Click here for back issues.