Understand diagnostic trouble codes of your car

Purpose:

本專題利用ESP32+MCP2515 CAN Bus module搭配CANHacker軟體和Torque APP去分析接收到ECU Simulator的診斷錯誤碼的PID資料.
This topic uses the ESP32+MCP2515 CAN Bus module with CANHacker software and Torque APP to analyze the PID data of the diagnostic trouble codes received from the ECU Simulator.

Fundamental:

Reference https://en.wikipedia.org/wiki/OBD-II_PIDs#Service_03

Diagnostic Trouble Codes (DTC) or Fault Codes

Under OBDII / EOBD systems, all manufacturers must use a universal 5 digits code system.

These universal 5 digits codes are made up of:

• The 1st character in the DTC indicates a letter which identifies the “main

system” where the fault occurred (Power train, Body, Chassis or

Network)

• The 2nd character is a numerical digit which identifies “Generic or

Manufacturer Specific”

• The 3rd character is also a numerical digit which identifies the specific

systems or sub-systems where the problem is located.

• The 4th and 5th characters are also numerical digits which identifies the

section of the system that is malfunctioning.

CAN Hacker module (ESP32+MCP2515)

Reference the previous article link on blog:

ESP32 + MCP2515 use CanHacker on CAN Bus system 

ECU Simulator

模擬器提供下列模式：

系統狀態、即時資料：MODE ０１

故障診斷：MODE ０３，０７，０Ａ

故障清除：MODE ０４

凍結資料：MODE ０２

氧感測器測試：MODE ０５

監測結果：MODE ０６

車輛資訊：MODE ０９ 

模擬器提供六組模擬訊號調整旋鈕。由左至右編號為１～６。

預設模擬訊號源為：空氣流量、冷卻液溫度、轉速、車速、進氣溫度、節氣門位置

Reference the previous article link on blog:

ECU Simulator CAN Bus Data with ESP32+MCP2515

ESP32+MCP2515 CAN Bus Scanner with ELM327 and ECU simulator

YouTube Demo:

ECU fault code analysis
Understand diagnostic trouble code of your car

Car DTC analysis via ESP32 CAN Bus module