[CAN-FD] Vehicle Diagnostic Communication Part 98 [AUTOSAR 3]

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

Introduction.
CAN-FD simulation results for AUTOSAR-CanTp and AUTOSAR-Dcm
CAN-FD simulation results for AUTOSAR-CanTp and AUTOSAR-Dcm (CAN line log)
Considerations for AUTOSAR-CanTp and AUTOSAR-Dcm CAN-FD simulation results
Conclusion.

Introduction.

The following explains the execution and results of the CAN-FD simulation in AUTOSAR.

CAN-FD simulation results for AUTOSAR-CanTp and AUTOSAR-Dcm

Simulation results are shown as follows.

Send msg : 225678
Recv msg : 62567801020300000000000000000000000000
Send msg : 225678567856785678
Recv msg : 62567801020300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Send msg : 221234123412341234123412341234123412341234123412341234123412341234123412341234123412341234123412341234123412341234123412341234123412341234123412341234123412341234
Recv msg : 62120000000000 /*Omitted*/  00000000000
Exiting

There is no change in the message.
As for AUTOSAR-Dcm, the only change is that the maximum message length has been extended.

CAN-FD simulation results for AUTOSAR-CanTp and AUTOSAR-Dcm (CAN line log)

And logs on the CAN line.

Begin Triggerblock Thu Oct 10 04:09:32.051 PM 2020
 0.000000 Start of measurement
 
 // DID=5678 Request
 0.000000 1 18DA10F1x Rx d 8 03 22 56 78 CC CC CC CC
 
 // Response in SingleFrame over 8
 0.002015 1 18DAF110x Rx d 24 00 13 62 56 78 01 02 03 00 00 00 00 00 00 00 00 00 00
 
 // DID=5678 Multi-DID request
 0.202719 1 18DA10F1x Rx d 12 00 09 22 56 78 56 78 56 78 56 78 CC
 
 // FirstFrame as follows 4095 bytes
 0.204562 1 18DAF110x Rx d 64 10 49 62 56 78 01 02 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0.205603 1 18DA
 0.205603 1 18DA10F1x Rx d 8 30 00 00 CC CC CC CC
 0.206635 1 18DAF110x Rx d 12 21 00 00 00 00 00 00 00 00 00
 
 // DID=1234 Multi-DID request
 0.404644 1 18DA10F1x Rx d 64 10 51 22 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34
 0.405381 1 18DAF110x Rx d 8 30 00 00 55 55 55 55
 0.407486 1 18DA10F1x Rx d 20 21 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34 12 34
 
 // FirstFrame when 4096 bytes or more
 0.452805 1 18DAF110x Rx d 64 10 00 00 00 14 51 62 12
 0.455410 1 18DA10F1x Rx d 8 30 00 00 CC CC CC CC
 0.456245 1 18DAF110x Rx d 64 21 37 38 39 3A 3B 3C 3D 0.457245 1 18DA
 0.457245 1 18DAF110x Rx d 64 22 76 77 78 79 7A 7B 7C 00 00 00 00 00 00 00 00 00 00 00 00 00

/* omitted */

 0.535036 1 18DAF110x Rx d 64 20 5C 5D 5E 5F 60 61 62 0.536019 1 18
 0.536019 1 18DAF110x Rx d 64 21 19 1A 1B 1C 1D 1E 1F 0.537018 1 18 18
 0.537018 1 18DAF110x Rx d 48 22 58 59 5A 5B 5C 5D 5E
End TriggerBlock

Considerations for AUTOSAR-CanTp and AUTOSAR-Dcm CAN-FD simulation results

AUTOSAR-CanTp also receives requests in accordance with the rules for CAN-FD and responds in accordance with the rules for CAN-FD.
In fact, it is possible to make one frame a message as follows: 64 bytes or less, but it might be a good idea to play with various parameters to try it out.

CAN-FD frames have some variations such as 8,12,…48,64.
There are corresponding can-isotp and CanTp parameters, so you should be able to try them out.

Conclusion.

Simulation of AUTOSAR-Dcm was executed.
- Simulation of AUTOSAR-Dcm, the basic principle is the same, except for the maximum message length.
Simulation of AUTOSAR-CanTp.
- Both request and response behaved according to CAN-FD rules.

Click here for back issues.