車両診断通信 [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.
KEI
車両診断通信 
車両診断通信 [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.
車両診断通信 [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.
車両診断通信 [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.
車両診断通信 [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.
車両診断通信 [DoCAN] Vehicle Diagnostic Communication Part 55 [UDS 16]
Explanation of the messages of the TesterPresent service.Explanation of suppressPosRspMsgIndicationBit.PositiveResponse suppression.NegativeResponse is returned.PositiveResponse after NRC$78 is also returned.
車両診断通信 [DoCAN] Vehicle Diagnostic Communication Part 54 [UDS 15]
There is a service called TesterPresent service that does nothing.The TesterPresent service has the following usage scenarios.Checking for communication.Node presence/absence check.Session maintenance.The TesterPresent service is a service that must be supported.