Negative response codes commonly used in UDS

Negative response codes commonly used in UDS

There are many negative response codes defined in UDS, but only the following are commonly used:

ServiceNotSupported/service not supported ($11)

When the service identifier in the request message sent by the diagnostic instrument is unrecognizable or not supported, the ECU should send this response code

SubFunctionNotSupported/Subfunction not supported ($12)

This response code indicates that the requested action cannot be performed because the ECU does not support the service-specific parameters in the request message. If the diagnostic instrument has sent a request message, and the request message contains a recognized and supported service identifier, but the sub-function is either not recognized or not supported, then the ECU shall send this response code

IncorrectMessageLengthOrInvalidFormat / Incorrect message length or invalid format ($13)

The response code indicates that the requested action cannot be executed because the length of the request message received by the ECU does not match the length specified by the specific service or the parameter format does not match the format specified by the specific service.

conditionsNotCorrect/conditions are incorrect ($22)

This response code indicates that the requested action cannot be executed because the status condition of the ECU is not allowed.

requestSequenceError/request sequence error ($24)

This response code indicates that the requested action cannot be performed because the ECU received an unexpected request message sequence or a message sent by the diagnostic tool.

requestOutOfRange / request out of range ($31)

This response code indicates that the requested action cannot be performed because the ECU has detected that the request message contains a parameter that exceeds the allowed range or does not support or activates access to a data identifier/routine identifier that is not supported in session mode. This response code shall be used by services that allow the diagnostic instrument to read data, write data, or pass data adjustment functions within the ECU.

securityAccessDenied / Security Access Denied ($33)

Used when secure access is required but not passed.

invalidKey/Invalid Key ($35)

This response code indicates that the reason the ECU is not allowing security access is that the key sent by the diagnostic tool does not match the key in the ECU's memory.

generalProgrammingFailure/General Programming Failure ($72)

This response code indicates that an error has been detected by the ECU when erasing or programming a non-erasable memory device.

requestCorrectlyReceived-ResponsePending / Correctly Received Request Message - Waiting for Response ($78)

This response code indicates that the message requested by the diagnostic instrument has been correctly received by the ECU and all parameters in the request message are valid, but the action to be performed has not been completed and the ECU is not ready to receive other requests. Once the requested service is completed, the ECU shall (shall) send a positive response message or a negative response message with a negative response code other than 78.

subFunctionNotSupportedInActiveSession/active session does not support this subservice ($7E)

This response code indicates that the requested action cannot be executed because the ECU does not support the requested sub-service in the current session mode.

serviceNotSupportedInActiveSession / active session does not support the service ($7F)

This response code indicates that the requested action cannot be executed because the ECU does not support the requested service in the current session mode.

General Catalog of "AUTOSAR Genealogy Decomposition (ETAS Toolchain)"