2023-01

車両診断通信

[Dcm] Vehicle Diagnostic Communication Part 67 [Simulation 6]

Dsl (Diagnostic Session Layer) is Session related sub-module. It manages P2 time, P2* time, S3 time, etc. It also contains the PudId of CanTp that is actually used.
車両診断通信

[Dcm] Vehicle Diagnostic Communication Part 66 [Simulation 5]

The content of AUTOSAR-Dcm structure consists of dsl, dsd, and dsp. Some are const defined and some are defined by variables for work. There are about 50 structures for configuration in total.
車両診断通信

[Dcm] Vehicle Diagnostic Communication Part 65 [Simulation 4]

Review of AUTOSAR-Dcm interface functions. I implemented the interface functions of AUTOSAR-Dcm.
車両診断通信

[Dcm] Vehicle Diagnostic Communication Part 64 [Simulation 3]

The interface specification of AUTOSAR-Dcm is figured out. The buffers for communication are managed by AUTOSAR-Dcm, which is a memory-saving and copy-saving design implementation. AUTOSAR-Dcm consists of three sub-modules. dsl: Diagnostic Session Layer. dsd: Diagnostic Service Dispatcher. dsp: Diagnostic Service Processing.
付加価値

【振り返り】ブログ開設三周年記念記事【技術ブログのPV数と収益】

祝3周年。 記事数は1000オーバー。 技術ブログとしてのアクセス数と収益の話。 ここにきて頭打ち。 一応、継続するが振り返りは今回を最後にする予定。
車両診断通信

[Dcm] Vehicle Diagnostic Communication Part 63 [Simulation 2]

Check AUTOSAR-Dcm specification (r3.3). Check AUTOSAR-Dcm interface. NRC$78 is just SingleFrame as AUTOSAR-CanTp.
車両診断通信

[Dcm] Vehicle Diagnostic Communication Part 62 [Simulation 1]

AUTOSAR-Dcm simulation configuration review. Review of services used in AUTOSAR-Dcm simulation. Listed specific items to be checked. Will also include confirmation of responsePendingCount, the number of times NRC$78 replies are received.
車両診断通信

[DoCAN] Vehicle Diagnostic Communication Part 61 [UDS 22]

The following is an example of a specific transmission/reception of the WriteDataByIdentifier service. I have explained examples of transmission/reception including NRC$78.
車両診断通信

[DoCAN] Vehicle Diagnostic Communication Part 60 [UDS 21]

Explanation of the request message for the WriteDataByIdentifier service. Unlike the ReadDataByIdentifier service, one DID is fixed. Explanation of the response message of the WriteDataByIdentifier service. In practice, NRC$78 may be interleaved.
車両診断通信

[DoCAN] Vehicle Diagnostic Communication Part 59 [UDS 20]

The WriteDataByIdentifier service has been explained. Usage scenarios. Communication characteristics tied to non-volatile memory.