Abstract
An automobile as we know it was not invented in a single day by a single inventor. It is more than an engine and a body; it is a complex machine that has undergone over a century of evolution. Over the years we have seen a constant stream of innovations and improvements in engine design. We have seen the advent of 4 wheel brakes, fuel injection and the automatic transmission.
Detecting a failure in this complex machine would be a tedious task. However, most of the vehicles today include computers (Electronic Control Unit (ECU)), which monitors several sensors, located throughout the engine, fuel and exhaust systems. When the computer system of the car detects a fault, two things are supposed to happen/monitored. First, a warning light on the dashboard is set, to inform the driver that a problem exists. Second the code is recorded in the computer’s memory (Electrically Erasable Programmable Read-Only Memory) so that it can later be retrieved by a technician for diagnosis and repair….
Funding Statement
1Introduction
An automobile as we know it was not invented in a single day by a single inventor. It is more than an engine and a body; it is a complex machine that has undergone over a century of evolution. Over the years we have seen a constant stream of innovations and improvements in engine design. We have seen the advent of 4 wheel brakes, fuel injection and the automatic transmission.
Detecting a failure in this complex machine would be a tedious task. However, most of the vehicles today include computers (Electronic Control Unit (ECU)), which monitors several sensors, located throughout the engine, fuel and exhaust systems. When the computer system of the car detects a fault, two things are supposed to happen/monitored. First, a warning light on the dashboard is set, to inform the driver that a problem exists. Second the code is recorded in the computer’s memory (ElectricallyErasableProgrammableRead-OnlyMemory) so that it can later be retrieved by a technician for diagnosis and repair.
The key to good auto repair lies in troubleshooting the problem. Problem in cars could be caused due to number of reasons. Proper troubleshooting will eliminate the potential issues that aren’t the real problem and point you in the right direction. This can be achieved through ‘Diagnostics’.
Did you notice when a problem happens in a car or a vehicle? Ok!! Let me say one situation.
There is a Check Engine Light(warning Lamp) present in our car’s dashboard, which alerts us when a problem occurs in the engine control system. Depending on the nature of the problem, the Check Engine Light may come on and go off, remain on continuously or flash. Some intermittent problems will make the Check Engine Light come on only when the fault is occurring. When the problem goes away, the Check Engine Light goes off. So, When the Check Engine Light comes on, a diagnostic trouble code (DTC) is recorded in the on-board computer memory that corresponds to the fault. Some problems can generate more than one trouble code, and some vehicles may have multiple problems that set multiple trouble codes.
2Overview of Diagnostics
2.1Diagnostics
Diagnostics, as the word suggests, is to identify the cause of a problem or a situation. Whenever the ECU finds a problem, it stores that problem as a Diagnostics Trouble Code (DTC) in the ElectricallyErasableProgrammableRead-OnlyMemory (EEPROM) for later retrieval. Diagnostic Tools are used to read data (DTC’s) from the EEPROM to analyze the cause of failure.
2.2Diagnostics Protocol
Protocol refers to a set of rules for communication. Here the communication happens between two ECUs which follow the same rule and able to exchange the information. The protocols which are used for Diagnostics purposes are known as Diagnostics Protocol.
The automotive industry has come up with Diagnostics protocols which are used for diagnostics purposes like, CAN (Control Area Network), K-Line, UDS (Unified Diagnostics Services), and KWP (Keyword Protocol) and so on. Here (in this document) we will study/know about UDS.
2.3Diagnostics Session
Diagnostic session is the basis for/of communication between the ECU and the diagnostic tool. During ‘Diagnostics’ the ECU being analyzed is in a particular session. Basically there are different types of diagnostics sessions like Default Session, Extended Diagnostic Session and ECU Programming Session.
After Ignition on, ECU will be switched to a Default Diagnostic Session and after receiving the request from Diagnostic Tool, the ECU will be switched to the Extended Diagnostic Session. Further, after receiving the ECU Programming Session start request from Diagnostic tool, it will switch to the ECU Programming Session.
2.4Automotive Diagnostic Service
Automotive diagnostic service is the way to discover, what’s wrong with the vehicle if it is not running / behaving properly. Diagnosing a vehicles problem in order to fix or repair a car can be done through a professional automobile diagnostic center. Diagnostic Service uses the read command for retrieving the information/data from ECU and the write command to write/program the data to the ECU.
Some of the services are given below as,
Ø Diagnostic Session Control
Ø ECU Reset
Ø Clear Diagnostic Information
Ø Read DTC Information
Ø Read Data By Identifier
Ø Read Memory By Address
Ø Security Access
Ø Communication Control
Ø Write Data By Identifier
Ø Input Output Control By Identifier
Ø Write Memory By Address
Ø Tester Present
Ø Control DTC Setting
For communicating with the ECU, the diagnostic tool uses either Physical addressing or Functional addressing method. Physical addressing is the kind of addressing where the Diagnostics tool communicates with a single ECU. Functional addressing is where the Diagnostics tool communicates with multiple ECUs.
3DetailedDiagnostic Services
The services supported by the UDS protocol are described in the table below:
Service Name | Description |
Diagnostic Session Control | Used to enable different diagnostic sessions in one ECU or a group of ECUs. |
ECU Reset | Used by the external diagnostic tool to request an ECU reset based on content of the reset type parameter included in the ECU Reset request message. |
Clear Diagnostic Information | Used by the external diagnostic tool to clear diagnostic information in one or multiple ECU’s memory. |
Read DTC Information | Allows a diagnostic tool to read the status of ECU resident Diagnostic Trouble Code (DTC) information from any ECU, or group of ECU’s within a vehicle. |
Read Data By Identifier | Allows the diagnostic tool to request data record values from the ECU identified by Record data identifier. |
Read Memory By Address | Allows the diagnostic tool to request memory data from the ECU via provided starting address and size of memory to be read. |
Security Access | Provides a means to access data and/or diagnostic services, which have restricted access for security, emissions, or safety reasons. |
Communication Control | Switches on and off the transmission of certain ECU messages |
Write Data By Identifier | Allows the diagnostic tool to write information into the ECU at an internal location specified by the provided data identifier. |
Input Output Control By Identifier | Used by the diagnostic tool to substitute a value for an input signal, internal ECU function and/or control an output (actuator) of an electronic system. |
Write Memory By Address | Allows the external diagnostic tool to write information into the ECU at one or more contiguous memory locations. |
Tester Present | Used to indicate to an ECU or a group of ECU’s that a diagnostic tool is still connected to the vehicle. |
Control DTC Setting | Used by diagnostics tool to stop or resume the setting of DTCs in ECU. |
3.1Diagnostic Session Control
The “Diagnostic Session Control” service shall be used to enable different diagnostic sessions in one ECU or a group of ECU’s. If no diagnostic session has been requested by the client after start communication a default session shall be automatically enabled in the server. The default session shall support at least the following services stop Communication service and tester Present service.
If a diagnostic session has been requested by the client which is already running, the server shall send a positive response message.
The Diagnostic Session Control request message shall meet the format defined in the Table below:
Data Byte No. | Parameter Name | Data Value |
1 | Diagnostic Session Control Service Id | 10 |
2 | sub Function | |
Default Session | 01 | |
Programming Session | 02 | |
Extended Session | 03 |
Request Message Definition – Diagnostic Session Control
Diagnostic Session Control Responses
Once ECU receives the request message from Tester, it has to send the response message to Tester.
If the response message is positive, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Diagnostics Session Control Response Service Id | 50 |
2 | sub Function | 00-FF |
3 | Session Parameter Record | 00-FF |
Positive Response
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | Diagnostics Session Control | 10 |
3 | sub function | 00-FF |
Sub function Not supported | 12 | |
Incorrect Message Length or Invalid Format | 13 | |
Conditions are not correct | 22 |
Negative Response
3.2ECU Reset
The ECU Reset service is used by the external diagnostic tool to request an ECU reset based on content of the reset type parameter included in the ECU Reset request message.
Basically there are two different types of ECU resets.
Hard Reset Soft Reset
Hard Reset:
This type identifies a “hard reset” condition which simulates the power-on/start-up sequences typically performed after an ECU has been previously disconnected from its power supply (i.e Battery). This implies the memory (Volatile or Non-volatile) as well as electronic sub-components directly connected to the ECU are initialized upon request of this reset type which are also initialized during the power-up sequence.
Soft Reset:
This type identifies a “soft reset” condition, which causes the ECU to immediately restart the application program if applicable. Before restarting the application the ECU saves any data in non-volatile memory that might be lost during the startup sequence.
The ECU Reset request message shall meet the format defined in the Table below,
Data Byte No. | Parameter Name | Data Value |
1 | ECU Reset Request Service Id | 11 |
2 | sub Function | |
Hard Reset – Positive response required | 01 | |
Key On-Off Reset – Positive Response Required | 02 | |
Soft Reset – Positive Response Required | 03 |
Request Message Definition – ECU Reset
ECU Reset Responses
If the response message is positive, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | ECU Reset Response Service Id | 51 |
2 | sub Function | 00-FF |
3 | Power Down Time | 00-FF |
Positive Response
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | ECU Reset | 11 |
3 | sub Function | 00-FF |
Sub function Not supported | 12 | |
Incorrect Message Length or Invalid Format | 13 | |
Conditions are not correct | 22 |
Negative Response
3.3Clear Diagnostic Information
The “Clear Diagnostic Information” service is used by the external diagnostic tool to clear diagnostic information in one or multiple ECUs’ memory.
A “Clear DTC information” request shall reset/erase all DTC information including the following:
a) DTC
b) DTC status byte
c) Other DTC related data such as first/most recent DTC, flags, counters, timers, etc. specific to DTC
Data Byte No. | Parameter Name | Data Value |
1 | Clear Diagnostic Information Request Service Id | 14 |
2 | Group Of DTC [2] = [Group Of DTC High Byte Group Of DTC Low Byte ] | 00-FF |
3 | Emission Related Systems | 000000 |
Request Message Definition – Clear DTC Information
Clear Diagnostic Information Responses
If the response message is positive, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Clear Diagnostic Information Positive Response Service Id | 54 |
Positive Response
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | Clear Diagnostic Information Request Service Id | 14 |
3 | sub-function | 00-FF |
Incorrect Message Length – Invalid Format | 13 | |
Conditions Not Correct | 22 | |
Request Out Of Range | 31 |
Negative Response
3.4Read DTC Information
This service allows a diagnostic tool to read the status of ECU resident Diagnostic Trouble Code (DTC) information from any ECU, or group of ECU’s within a vehicle.
Requesting the ECU to report Most Recent Confirmed DTC or all Supported DTCs the diagnostic tool shall use the format defined in the Table below.
Data Byte No. | Parameter Name | Data Value |
1 | Read DTC Information request Service Id | 19 |
2 | sub-function | 00-FF |
Report Supported DTCs -Positive Response Required | 0A | |
Report Most Recent Confirmed DTC – Positive Response Required | 0E |
Request Message Definition – Read DTC Information
Read DTC Information Responses
If the response message is positive, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Read DTC Information response Service Id | 59 |
2 | Report Type | 00-FF |
Report Number Of DTC By Status Mask | 01 | |
Report Number Of Mirror Memory DTC By Status Mask | 11 | |
Report Number Of DTC By Severity Mask Record | 07 | |
3 | DTC Status Availability Mask | 00-FF |
4 | DTC Format Identifier | 00-FF |
5 | DTC Count [ 2] = [DTC Count High ByteDTC Count Low Byte ] | 00-FF |
Positive Response
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | Read DTC Information | 19 |
3 | sub-function | 00-FF |
Sub Function Not Supported | 12 | |
Incorrect Message Length – Invalid Format | 13 | |
Request Out Of Range | 31 |
Negative Response
3.5Read Data By Identifier
The “Read Data By Identifier” service allows the diagnostic tool to request data record values from the ECU identified by Record Data identifiers.
Data Byte No. | Parameter Name | Data Value |
1 | Read Data By Identifier Request Service Id | 22 |
2 | Data Identifier[2] | 00-FF |
Request Message Definition – Read Data By Identifier
Read Data By Identifier Responses
If the response message is positive, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Read Data By Identifier Response Service Id | 62 |
2 | Data Identifier[2] | 00-FF |
4 | Data Record [2] | 00-FF |
Positive Response
If an ECU responds positively to a “Read Data By Identifier” request, the response message Data Identifier parameter value shall be an echo of the value provided in the request message by the diagnostics tool
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | Read Data By Identifier | 22 |
3 | sub-function | 00-FF |
Incorrect Message Length- Invalid Format | 13 | |
Conditions Not Correct | 22 | |
Request Out of Range | 31 | |
Security Access Denied | 33 |
Negative Response
3.6Read Memory By Address
The “Read Memory By Address” services allows the diagnostics tool to request memory data from the ECU via provided starting address and size of memory to be read.
Read / Write Memory ByAddress Parameter | Description |
Address And Length Format Identifier | This parameter is a onebyte value with eachnibble encoded separately:bit 3 – 0: Length(number of bytes) of the MemoryAddress parameterbit 7 – 4: Length(number of bytes) of theMemory Size parameter |
Memory Address | The parameter MemoryAddressis the starting addressof ECU’s memory wherethe data is to be writtenor from which thedata is to be read. |
Memory Size | The parameter MemorySize in the Read / Write MemoryBy Address request messagespecifies the numberof bytes to be read orwritten starting at theaddress specified byMemory Address inthe ECU’s memory.The number of bytesused for this size isdefined by the highnibble (bit 7 – 4) of theAddress And LengthFormat Identifier. |
Data Record | This parameter is usedby the Read MemoryBy Address positiveresponse messageto provide the requesteddata record values tothe diagnostic tool.The content of theData Record is notdefined in this documentand is vehiclemanufacturer specific. |
Read / Write Memory By Address Request Parameters
The “Read Memory By Address” request message shall meet the format defined in table below.
Data Byte No. | Parameter Name | Data Value |
1 | Read Memory by Address Request Service ID | 23 |
2 | Address And Length Format Identifier | 00-FF |
3 | Memory Address[2] | 00-FF |
4 | Memory Size[2] | 00-FF |
Request Message Definition – Read Memory By Address
Read Memory By Address Responses
If the response message is positive, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Read Memory By Address Response Service Id | 63 |
2 | Data Record [2] = [data number 1,data number 2] | 00-FF |
Positive Response
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | Read Data By Identifier | 23 |
3 | sub-function | 00-FF |
Incorrect Message Length- Invalid Format | 13 | |
Conditions Not Correct | 22 | |
Request Out of Range | 31 | |
Security Access Denied | 33 |
Negative Response
3.7Security Access
The purpose of this service is to provide a means to access data and/or diagnostic services, which have restricted access for security, emissions, or safety reasons. The security concept uses a seed and key relationship.
Security Access Request Type Description
Security Access type | Description |
Request Seed | This type specifies thatthe ECU shall transmitto the test device theso called seed valuewith a defined securitylevel for calculating anappropriate key value tounlock the ECU. |
Send Key | This type signalizes tothe ECU that thediagnostic tool transmitsnow the appropriate keyvalue associated with theseed requested before. |
The Security Access request message shall meet the format defined in table below.
Data Byte No. | Parameter Name | Data Value |
1 | Security Access Request Service ID | 27 |
2 | sub Function = [Security Access type] | 00-FF |
Request Seed – Positive Response Required | 01 | |
Send Key – Positive Response Required | 02 | |
3 | Security key[1] | 00-FF |
Request Message Definition – Security Access
Security Access Responses
If the response message is positive, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Security Access Response Service Id | 67 |
2 | Security Access Type | 00-FF |
3 | Security Seed [2] | 00-FF |
Positive Response
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | SecurityAccess | 27 |
3 | sub-function | 00-FF |
Sub-Function Not Supported | 12 | |
Incorrect Message Length | 13 | |
Conditions Not Correct | 22 | |
Request Sequence Error | 24 | |
Invalid Key | 35 | |
Exceeded Number Of Attempts | 36 | |
Required Time Delay Not Expired | 37 |
Negative Response
3.8Communication Control
The purpose of this service is to switch on and off the transmission of certain ECU messages.
Control Type description
Some possible Communication Control types are,
Control Type | Description |
Enable Rx And Tx | This type indicates thatthe ECU shall enablereception andtransmission of messages. |
Enable Rx And Disable Tx | This type indicatesthat the ECU shallenable receptionof messages and disabletransmission of messages. |
Communication Type description
Some possible Communication types are,
Control Type | Description |
Normal Communication Messages | This type referencesall application-relatedcommunication |
Network Management Communication Messages | This type referencesall network managementrelated communication. |
The ECU shall perform the requested communication type control after sending the Communication Control positive response message to the diagnostic tool if a positive response is requested (Suppress Position Response Message Indication Bit = FALSE).
In case no response is requested from the diagnostic tool (Suppress Position Response Message Indication Bit = TRUE) then the ECU shall perform the requested communication type control immediately after the successful evaluation of the request message.
The Communication Control request message shall meet the format defined in the Table below.
Data Byte No. | Parameter Name | Data Value |
1 | Communication Control Request Service Id | 28 |
2 | Security Function / Sub function | 00-FF |
Enable Rx And Tx – Positive Response Required | 01 | |
Enable Rx And Disable Tx – Positive Response Required | 11 | |
Vehicle Manufacturer Specific – Positive Response Required | 40-5F | |
System Supplier Specific – Positive Response Required | 60-7E | |
3 | Communication Type | 00-FF |
Normal Communication Messages | 01 | |
Network Management Communication Messages | 02 |
Request Message Definition – Communication Control
Communication Control Responses
If the response message is positive, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Communication Control Response Service Id | 28 |
2 | Control Type | 00-FF |
Positive Response
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | Communication Control | 28 |
3 | sub-function | 00-FF |
Sub-Function Not Supported | 12 | |
Incorrect Message Length | 13 | |
Conditions Not Correct | 22 | |
Request Sequence Error | 31 |
Negative Response
3.9Write Data By Identifier
The “Write Data By Identifier” service allows the diagnostic tool to write information into the ECU at an internal location specified by the provided data identifier.
Following table defines the possible request and response parameter types,
Data Identifier | This parameter identifiesthe ECU’s data record that, the diagnostic tool isrequesting to write to. |
Data Record | This parameter providesthe data record associatedwith the Data Identifierthat the diagnostic toolis requesting to write to. |
The Write Data By Identifier request message shall meet the format defined in the Table below,
Data Byte No. | Parameter Name | Data Value |
1 | Write Data By Identifier Request Service Id | 2E |
2 | Data Identifier[2] | 00-FF |
3 | Data Record [2] | 00-FF |
Request Message Definition – Write Data By Identifier
Write Data By Identifier Responses
If the response message is positive, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Write Data By Identifier Response Service Id | 6E |
2 | Data Identifier[2] | 00-FF |
Positive Response
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | Write Data By Identifier | 2E |
3 | sub-function | 00-FF |
Security Access Denied | 33 | |
Incorrect Message Length | 13 | |
Conditions Not Correct | 22 | |
Request Out Of Range | 31 |
Negative Response
3.10Input Output Control By Identifier
The “Input Output Control By Identifier” service is used by the diagnostic tool to substitute a value for an input signal, internal ECU function and/or control an output (actuator) of an electronic system.
The “Input Output Control By Identifier” request message shall meet the format defined in the Table below.
Data Byte No. | Parameter Name | Data Value |
1 | Input Output Control By Identifier Request Service Id | 2F |
2 | Data Identifier[2] | 00-FF |
3 | Input Output Control Type | 00-FF |
Return Control To ECU | 00 | |
Reset To Default | 01 | |
FreezeCurrent State | 02 | |
Short Term Adjustment | 03 |
Request Message Definition – Input Output Control By Identifier
Input Output Control By Identifier Responses
The ECU shall send a positive response message if the requested control operation was successfully executed. After an ECU returns a positive response to this service, the diagnostic tool shall assume control over the inputs/outputs specified by the Input Output Data Identifier.
If the response message is positive, then the expected response is as given in the table below.
Data Byte No. | Parameter Name | Data Value |
1 | Input Output Control By Identifier Response Service Id | 6F |
2 | Data Identifier[2] | 00-FF |
3 | Input Output Control Type | 00-03 |
Positive response
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | Input Output Control By Identifier | 2F |
3 | sub-function | 00-FF |
Incorrect Message Length – Invalid Format | 13 | |
Conditions Not Correct | 22 | |
Request Out Of Range | 31 | |
Security Access denied | 33 |
Negative response
3.11Write Memory By Address
The “Write Memory By Address” service allows the external diagnostic tool to write information into the ECU at one or more contiguous memory locations.
The “Write Memory By Address” request message shall meet the format defined in the Table below.
Data Byte No. | Parameter Name | Data Value |
1 | Write Memory By Address Request Service Id | 3D |
2 | Address And Length Format Identifier | 00-FF |
3 | Memory Address[2] | 00-FF |
4 | Memory Size[2] | 00-FF |
5 | Data Record[2] | 00-FF |
Request Message Definition – Write Memory By Address
Write Memory By Address Responses
If the response message is positive, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Write Memory By Address Response Service Id | 7D |
2 | Address And Length Format Identifier | 00-FF |
3 | Memory Address[2] | 00-FF |
4 | Memory Size[2] | 00-FF |
Positive Response
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | Write Memory By Address | 3D |
3 | sub-function | 00-FF |
Incorrect Message Length – Invalid Format | 13 | |
Conditions Not Correct | 22 | |
Request Out Of Range | 31 | |
Security Access denied | 33 | |
General Programming Failure | 72 |
Negative Response
3.12Tester Present
This service is used to indicate to an ECU or a group of ECU’s that a diagnostic tool is still connected to the vehicle and that certain diagnostic services and/or communication that have been previously activated are to remain active.
The “Tester Present” request message shall meet the format defined in the Table below.
Data Byte No. | Parameter Name | Data Value |
1 | Tester Present Request Service Id | 3E |
2 | sub Function | XX |
Positive Response Required | 00 | |
No Positive Response Required | 80 |
Request Message Definition – Tester Present
Tester Present Responses
If the response message is positive, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Tester Present Response Service Id | 7E |
2 | sub Function | 00 |
Positive Response
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | Tester Present | 3E |
3 | sub-function | 00-FF |
Sub Function Not Supported | 12 | |
Incorrect Message Length – Invalid Format | 13 |
Negative Response
3.13Control DTC Setting
The “Control DTCsetting” service is used by a diagnostictool to stop or resume the setting of DTCs in the ECU.
DTC setting type description
The below table defines the possible DTC Setting types,
DTC Setting Type | Description |
On | This type requires theECU to enable settingof DTCs. |
Off | This type requires theECU to disable settingof DTCs. |
The “Control DTC Setting” request message shall meet the format defined in the Table below.
Data Byte No. | Parameter Name | Data Value |
1 | Control DTC Setting Request Service Id | 85 |
2 | Sub Function | 00-FF |
On – Positive Response Required | 01 | |
Off – Positive Response Required | 02 |
Request Message Definition – Control DTC Setting
Control DTC Setting Responses
If an ECU responds positively to a “Control DTC Setting” request, the DTC Setting type in the response shall match the DTC Setting sent in the request
If the response message is positive, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Control DTC Setting Positive Response Service Id | C5 |
2 | sub Function | XX |
Positive Response
And if the response message is negative, then response should meet the format, given in below table.
Data Byte No. | Parameter Name | Data Value |
1 | Negative Response | 7F |
2 | Control DTC Setting | 85 |
3 | sub-function | 00-FF |
Sub Function Not Supported | 12 | |
Incorrect Message Length – Invalid Format | 13 | |
Conditions Not Correct | 22 | |
Request Out Of Range | 31 |
Negative Response
4Conclusion
Due to much technological advancement, today’s cars are more complex than ever before and so the troubleshooting of car’s problem has even become more complex and tedious job. Thanks to advanced diagnostic facilities within the car which assist in pin-pointing the exact cause of trouble in a car.
5Reference
Øwww.auto-diagnostics.info
Øwww.obddiagnostics.com
Anonymous
bundle of thx .. — it helped me in understanding the ISO 15765 ………. thx