Vehicle Diagnostic Communication back issue
Introduction This is a back-issue of a series that discusses various aspects of vehicle diagnostic communications.Th...
[Dcm] Vehicle Diagnostic Communication Part 78 [Simulation 17]
I wrote a Python code to simulate TesterPresents. Considering the main purpose of TesterPresents, SessionControl and SecurityAccess are also implemented. The main purpose is to suppress S3 timeouts.
[Dcm] Vehicle Diagnostic Communication Part 77 [Simulation 16]
Check the results of the SecurityAccess simulation. Check the message level. Check the CAN line level. SecurityAccess behavior depends on session state and security state. SecurityAccess behavior depends on session state, security state, and S3 timeout.
[Dcm] Vehicle Diagnostic Communication Part 76 [Simulation 15]
I wrote Python code for the SecurityAccess simulation. There is a large amount of work to be done to make sure SecurityAccess works. Support sessions. Sequence. Seed in security unlocked state. Transition to locked state on session transition. Session transitions due to S3 timeouts.
[Dcm] Vehicle Diagnostic Communication Part 75 [Simulation 14]
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.
[Dcm] Vehicle Diagnostic Communication Part 74 [Simulation 13]
I wrote a Python code for simulation of DiagnosticSessionControl. Communication patterns include error patterns. Non-existent session. Wrong message length for a DiagnosticSessionControl request.
[Dcm] Vehicle Diagnostic Communication Part 73 [Simulation 12]
Review of AUTOSAR Dcm simulation configuration The Python code on the off-board tester side is the same as we have used so far. Modifications will be made as needed. The order in which the simulations are run is as follows. DiagnosticSessionControl. SecurityAccess. TesterPresent. ReadDataByIdentifier. WriteDataByIdentifier.
[Dcm] Vehicle Diagnostic Communication Part 72 [Simulation 11]
I wrote the configuration code for Dsp. Mostly security, session definition and association with DID.
[Dcm] Vehicle Diagnostic Communication Part 71 [Simulation 10]
Dsp is the application layer. It is divided into ISO14229-1 dependent and manufacturer dependent, and manufacturer dependent is handled by callback functions. The DID-related part of Dsp is the most complicated. Once you know DID, other configurations are relatively easy.
[Dcm] Vehicle Diagnostic Communication Part 70 [Simulation 9]
I wrote the configuration code for Dsd. The corresponding security level and session entity are in Dsp and only referenced from Dsd.