#uds |P2 and P2* timer in UDS | P2 Timer in UDS | P2 star in UDS | P2 and P2* Timer in UDS Protocol

p2 Timer
P2 star timer
Negative response code,
NRC - 78 - Pending
NRC - 10 - General Reject.

#UDS #unifieddiagnosticsservices #diagnostics #Automotive

[vlbvinoth]

Thank you so much....
Oru naalukulla full UDS concepts uh details uh understand pannirukaen...
It's all because of you...
very precise...
to the pin point explanation...

[curiousworld]

some correction is needed here. After p2 timer timeout, p2* will start and sends nrc 78. And after p2* timeout again it will send nrc78 and p2* will restart and wait for the response. If no response received, the same procedure will repeat for max number of nrc78 configured.

After maximum nrc78 sent, the ecu will send nrc10

[guthaneelima]

Why we will get NRC 10 if time exceeded more than 5sec

[ashishbhardwaj]

@HandsOnLab Thanks for this very informative video, was looking for something like this. Consider a scenario, Server sends 03 7F 10 78 at the end of P2. Now imagine that Server fails to produce a positive response until the very end of P2*. It manages to send a positive response just before the end of P2*. My question is now how many negative responses will the Server send to Client in-between the first negative response at the end of P2 and the positive response just before the end of P2*? And at what intervals will they come?
Is it that Server will send a negative response every 50ms (P2) until a positive response, this way sending 100 negative responses (100*50ms=5000ms) after first negative response. Or is it that randomly Server will send some 'n' number of negative response at uniform/non-uniform intervals?