KEI

車両診断通信

[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.
2023.01.18
車両診断通信
付加価値

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

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

[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.
2023.01.16
車両診断通信
車両診断通信

[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.
2023.01.15
車両診断通信
車両診断通信

[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.
2023.01.14
車両診断通信
車両診断通信

[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.
2023.01.13
車両診断通信
車両診断通信

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

The WriteDataByIdentifier service has been explained.Usage scenarios.Communication characteristics tied to non-volatile memory.
2023.01.12
車両診断通信
車両診断通信

[DoCAN] Vehicle Diagnostic Communication Part 58 [UDS 19]

Confirmed single DID transmitted and received.Confirmed transmitting and receiving multi-DIDs.Confirmed some DIDs are undefined patterns.
2023.01.11
車両診断通信
車両診断通信

[DoCAN] Vehicle Diagnostic Communication Part 57 [UDS 18]

Explanation of the request message for the ReadDataByIdentifier service.Multiple DIDs can be set.There may be a limit on the number of DIDs that can be set, and it is an error if the number is exceeded.It is also an error if the response message exceeds 4095 bytes.Explanation of the ReadDataByIdentifier service response messageCombination of DID and dataRecord.In case of multiple DIDs, the above combination is placed in one message.
2023.01.10
車両診断通信
車両診断通信

[DoCAN] Vehicle Diagnostic Communication Part 56 [UDS 17]

Explanation of the usage scenario of the ReadDataByIdentifier service.Vehicle status monitoring (verification during development, failure analysis after market release).Forced operation status monitoring during vehicle assembly.Freeze data acquisition at the time of failure detection.
2023.01.09
車両診断通信
次のページ