KEI

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.

Explanation of the messages of the TesterPresent service. Explanation of suppressPosRspMsgIndicationBit. PositiveResponse suppression. NegativeResponse is returned. PositiveResponse after NRC$78 is also returned.

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.

Explain the basic flow of the SecurityAccess service. Explain the actual messages in the basic flow of the SecurityAccess service. Security is applied to resources. Service. DID.

The SecurityAccess service is purposely troublesome procedure, which is the security strength. Must transition to non-defaultSession in advance. Must wait 10 seconds after IGon. If you make a mistake unlocking, you have to IGoff once.

The SecurityAccess service has two major message patterns. requestSeed. Odd sub-functions. sendKey. Even sub-functions.

Review of P2 time. P2 time is 1 second Explanation of P2* time P2* time is 5 seconds. When the off-board tester receives NRC$78, it switches from P2 time to P2* time. When the off-board tester receives NRC$78 again, it extends P2* time from there.

Click here for back issues.Introduction.Explanation of ISO 14229, UDS.I will explain PositiveResponse and NegativeRespon...

Explains the session as defined in the ISO for DiagnosticSessionControl Request message of DiagnosticSessionControl. Response message of DiagnosticSessionControl. P2 time and P2* time of the relevant session can be obtained.

There are five services to be realized by UDS simulation DiagnosticSessionControl. SecurityAccess. TesterPresent. ReadDataByIdentifier. WriteDataByIdentifier. When explaining the request and response messages, the CAN frame is not explained. I will only explain the ISO 14229-1 layer and not the ISO 15765-2 layer.