Click here for back issues.
https://www.simulationroom999.com/blog/diagnostic-communication-en-back-issue/
Introduction.
AUTOSAR-Dcm Configuration Explained.
This article will explain the following: the role of Dsp, class diagram, etc.
- Positioning of Dsp.
- How to separate and combine ISO14229-1 dependent parts and complete vehicle manufacturer dependent parts.
- Which is the most complex structural part of Dsp.
And so on.
Role of AUTOSAR-Dcm Dsp
In this article, I will explain AUTOSAR-Dcm and the last sub-module, Dsp.
Dsp stands for Diagnostic Service Processing.
Dsp is the top level layer and corresponds to the application layer, and is the part that defines the actual behavior of each service.
There are two parts to the behavior: the part specified in ISO14229-1 and the part that depends on the manufacturer.
The part specified in ISO 14229-1 is Dsp handling.
The manufacturer-dependent part is handled by registering a callback function and embedding the manufacturer-dependent code in the function.
This is the basic idea.
The callback function will be called back when necessary, so the necessary code should be written by each user.
AUTOSAR-Dcm Dsp configuration structure
The Dsp configuration structure is then shown as follows.
It is better than Dsl, but quite complicated.
The actual structure is more complicated than this.
AUTOSAR-Dcm Dsp configuration structure in brief
The scope of this explanation is the part related to DID.
In reality, there are also configuration sets for ECU Reset, route control, etc., but they are not used in the simulation, so they are omitted.
This omitted part should be simpler than DID.
In the case of DID, it is used for three types of read/write/IO control, which is complicated, but the other resources can be called back as they are and left to the application.
So, once you understand the DID-related information, the other resources should be fairly easy to use.
Conclusion.
- 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.
Click here for back issues.
コメント