[Dcm] Vehicle Diagnostic Communication Part 75 [Simulation 14]

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

Introduction.
Results of DiagnosticSessionControl simulation (message)
Results of DiagnosticSessionControl simulation (CAN line)
Consideration of the results of the DiagnosticSessionControl simulation.
Conclusion

Introduction.

Explanation of AUTOSAR-Dcm simulation.
In this article, we will check the simulation results of DiagnosticSessionControl.

Results of DiagnosticSessionControl simulation (message)

First, it may be a good idea to review DiagnosticSessionControl.
I will explain in the following.

The actual message log is in the following.
I’ve added a comment as well.

Send msg : 1001 // Transition to defaultSession
Recv msg : 50010010012c // P2 time=16[ms],P2*time=3000[ms]
Send msg : 1002 // transition to programmingSession
Recv msg : 5002002001f4 // P2 time=32[ms],P2*time=5000[ms]
Send msg : 1003 // Transition to extendDiagnosticSession
Recv msg : 5003003001f4 // P2 time=48[ms],P2*time=5000[ms].
Send msg : 1004 // transition to safetySystemSession
Recv msg : 5004003100c8 // P2 time=49[ms],P2*time=200[ms]
Send msg : 1005 // transition to nonexistent Session
Recv msg : 7f1012 // NRC$12(subFunctionNotSupported)
Send msg : 100102 // message length is abnormal
Recv msg : 7f1013 // NRC$13(incorrectMessageLengthOrInvalidFormat)
Exiting

Results of DiagnosticSessionControl simulation (CAN line)

And the log on the CAN line is in the following.

Begin Triggerblock
 0.000000 Start of measurement
 
 // Transition to defaultSession
 0.000000 1 18DA10F1x Rx d 8 02 10 01 CC CC CC CC
 0.001778 1 18DAF110x Rx d 8 06 50 01 00 10 01 2C 55
 
 // Transition to programmingSession
 0.208806 1 18DA10F1x Rx d 8 02 10 02 CC CC CC CC CC
 0.210887 1 18DAF110x Rx d 8 06 50 02 00 20 01 F4 55
 
 // Transition to extendDiagnosticSession
 0.409289 1 18DA10F1x Rx d 8 02 10 03 CC CC CC CC CC
 0.411329 1 18DAF110x Rx d 8 06 50 03 00 30 01 F4 55
 
 // Transition to safetySystemSession
 0.618988 1 18DA10F1x Rx d 8 02 10 04 CC CC CC CC CC
 0.620962 1 18DAF110x Rx d 8 06 50 04 00 31 00 C8 55
 
 // Transition to nonexistent Session
 0.818225 1 18DA10F1x Rx d 8 02 10 05 CC CC CC CC CC
 0.820298 1 18DAF110x Rx d 8 03 7F 10 12 55 55 55 55
 
 // Message length abnormal
 1.021387 1 18DA10F1x Rx d 8 03 10 01 02 CC CC CC CC
 1.023386 1 18DAF110x Rx d 8 03 7F 10 13 55 55 55 55
End TriggerBlock

Consideration of the results of the DiagnosticSessionControl simulation.

It seems to work well.

In this article, the NegativeResponse was determined by the AUTOSAR code, without any independent determination.
The non-existent Session and the abnormal message length are information that can be determined from the configuration.

A typical example of an original judgment is NRC$22 (conditionsNotCorrect).
This is a NegativeResponse that is returned when the vehicle condition is undesirable for performing the relevant service.
In this article, a transition to programmingSession while the vehicle is in motion may be undesirable.
In that case, conditionsNotCorrect may be returned.

Is there a case in which a session transition is inconvenient?
Sometimes, programmingSession is designed to enter reprogramming mode at the moment of transition, and control may not be guaranteed in that mode.
Therefore, it is often the case that programming session transitions are not allowed while the program is running.

Conclusion

Check the results of the DiagnosticSessionControl simulation.
- Confirmation of message level.
- Confirmation of CAN line level.
NegativeResponse can be automatically determined and returned by Dcm or by adding your own code.
- Message length and parameter abnormality are judged automatically.
- Rejections due to vehicle status are returned with an original code.

Click here for back issues.