On-board Diagnostic（OBD）

转载：http://www.obddiag.net/adapter.html

OBD-II
If your car manufactured for sale in the U.S. after 1996, it is equipped with on-board diagnostics (OBD-II) and has OBD connector somewhere in the passenger compartment. The OBD-II connector enables a scan tool to read diagnostic data from the engine computer. By law, the OBD diagnostic should supply a number of key parameters relating to the on-board monitoring of emissions from vehicles, including data such as engine speed, coolant temperature, and oxygen sensor readings. EOBD is a version of OBD-II required in Europe starting year 2004 for diesel vehicles and 2001 for gasoline vehicles. The table below shows the kinds of real-time data that you can read from your car’s engine computer using OBD-II Mode 0x01 PIDs. This is a small subset of the data that is available from your vehicle’s OBD-II bus.

The Data Link Connector (DLC) for connecting the diagnostic equipment is standard as well. The pinout of DLC connector is shown below as defined by SAE J1962 spec.

The OBD-II standard, ISO 15031-5/SAE J1979 provides five distinct electrical interfaces:
SAE J1850 VPW
SAE J1850 PWM
ISO 9141-2
ISO 14230-2 KWP2000
ISO 15765-4 CAN
All cars manufactured after year 2008 should use only CAN (ISO 15765-4) protocol. However, that is rather wishful thinking as some manufactured were using the legacy OBD protocols even after year 2008. Tables below show the protocols that used for OBD services.

ISO 9141-2
ISO 9141-2 was the most used protocol by vehicle manufactures before the introduction of CAN. The original ISO document goes back to year 1994 with bidirectional serial communication on a single wire called the K-line. In addition, there is an optional L-line for connection initialization. The communication started by sending the distinct signal pattern on K-line and L-line and the all communication is performed over K-line. According to the specification, the L-line is only used to initiate the communication and remains inactive (high-level) afterward, seldom being used for diagnostic purposes. The maximum data length is limited to 255 bytes.

ISO 14230-2
The ISO 14230-2 protocol is similar to ISO 9141-2, with the initialization mechanism can use either slow signal pattern 5 bit/s like ISO9141 or fast init (short 50us pulse).

SAE J1850
It is a Class B Data Communication Network Interface employs media access layer (MAC) based on priority. The J1850 bus takes two forms, 41.6Kbps Pulse Width Modulated (PWM) two wires differential approach, or a 10.4Kbps Variable Pulse Width (VPW) single wire approach. The PWM flavor was used in Ford vehicles when VPW attributed to Chrysler/GM. Both variants are CSMA/CR protocols with collisions handled by arbitration. This contention bus is inherited from an open architecture that lets node be added or removed from a network without much impact on the rest of the system, which is called non-destructive contention resolution. The latest protocol revision, SAE J1850_201510 includes High Speed Mode (83.3 Kbps) for PWM as well as 4x Speed Mode (41.6 Kbps) and Block Mode (unlimited data length) for VPW.

ISO 15765-4
The Controller Area Network (CAN) was introduced by Bosch at the SAE Congress in Detroit In February 1996. It based on a non-destructive arbitration mechanism, which grants bus access to the message with the highest priority without any delays. There was no central bus master. The CAN standard is capable of sending data frames containing between 1 and 8 bytes of data. The standard defines a method for segmenting data consisting of up to 4095 bytes and 4 different types of frames: SingleFrame, FirstFrame, ConsecutiveFrame and FlowControl. The type of frame encoded in the first 4 bits (the high nibble) of the first data byte in each frame. Each frame contains Protocol Control Information (PCI) data.

CAN-FD
CAN with Flexible Data Rate (CAN-FD) is the latest variant of CAN. In CAN 2.0 the maximum achievable bit rate is 1 Mbps, a limit that is largely imposed by the arbitration method. Because arbitration is not needed during the transmission of other parts of a frame, it is possible to increase the bit rate during the control, payload and CRC sections. CAN-FD maintains the 1 Mbps speed during arbitration, and then sends these other parts of the frame at up to 8 Mbps. Another limitation of original CAN is its 8-byte frame size, which is not adequate for modern networks. Bosch reformulated the CRC calculation so that the payload can increase from 8 bytes to 64 while maintaining CAN 2.0’s error detection robustness.

ISO 13400-3
The ISO 13400-3 - diagnostic communication over Internet Protocol (DoIP). Note, that standart is not part of OBD (ISO 15031-5/SAE J1979) but WWH-OBD. The intent of ISO 13400 is to describe a standardized vehicle interface which:

Separates in-vehicle network technology from the external test equipment Utilizes existing industry standards to define a long-term stable state-of-the-art communication standard usable for legislated diagnostic communication as well as for manufacturer-specific use cases Can easily be adapted to new Physical and Data Link Layers, including wired and wireless connections, by using existing adaptation layers.
To achieve this goals, the standard is based on the Open Systems Interconnection (OSI) Basic Reference Model specified in ISO/IEC 7498-1 and ISO/IEC 10731, which structures communication systems into seven layers. When mapped on this model, the services specified by ISO 14229-1, ISO 14229-2 and ISO 14229-5 are divided into：

ISO 14229 – Unified diagnostic services (UDS)
The ISO 14229 standard defines the actual diagnostic services used in automotive ECUs. These services can be used to upload and download software and data to the ECU, read and erase the fault codes and etc. Note, that the standard does not depend on a specific type of data link, but rather rely on application layer protocol functionality to send and receive the data. In reality, the underlying communication protocol imposes the actual limitation on the maximum data length. The ISO14229 standard consists of the following parts:

On-board Diagnostic（OBD）相关推荐

物联网细分领域-车联网（OBD）市场分析
前言: 这段时间在跟一个车联网的项目,所以做了一些研究. OBD概述 OBD是英文On-Board Diagnostic的缩写,中文翻译为"车载诊断系统".这个系统随时监控发动机的 ...
POJ 1691 - Painting A Board + Python （DFS）
题目链接:1691 -- Painting A Board 参考资料:POJ 1691 - Painting A Board | 眈眈探求特别注意:注意本文的升序排列语句. 一题目描述: 给定一个 ...
（一）Bentley（OBD）二次开发-建筑对象的构件结构
一.前言说明 OBD是Bentley的BIM平台,基于建筑领域的再次包装.前身的版本是ABD(32位的软件系统),由于跟不上时代的发展,在2019年升级发展为64位的OBD软件平台. 二.墙.梁等建筑 ...
汽车UDS诊断详解及Vector相关工具链使用说明——2.3.1 故障码（DTC）格式详解
1. 概述存储数据传输功能单元其实就是读取故障码信息和清除故障码两个服务.我们本文先来看一下我们一直在说的故障码的格式是怎样的. 我们通常把诊断分成两种,我们之前一直在讲的UDS诊断属于增强型诊断, ...
pspice介绍1（转载）
PSpice的主要功能及特点: OrCAD软件的主要组成包括:OrCAD/Capture CIS.OrCAD/Layout Plus.OrCAD/Express及OrCAD/PSpice.它们分别是: ...
汽车电磁兼容（EMC）问题的研究
一.汽车电磁兼容的问题概述为满足人们对汽车的安全.环保.节能以及舒适等性能日益增高的要求,装备电子.电器设备,应用电子技术是最有效的手段 .制动防抱死系统(ABS).车身控制模块(BCM).电子防盗 ...
常见外贸英文缩写（中）
从事外贸行业给国外客户打电话用哪种方式最好,很多人会说用Skype.WhatsApp.IntBell.RingCentral等等.打住!我们今天不是来讨论哪个App比较好用,也不是来讨论你在用哪个Ap ...
基于OBD的量产车评估（PVE）测试方法
目录 1. OBD系统 1.1 概述 1.2 OBD系统模式/服务 1.3 OBD系统监测要求案例 2. PVE测试方法及故障分类 2.1 PVE测试方法 2.1.1 J1标准化验证 2.1.2 J2 ...
关于汽车诊断OBD的理解（ISO15031-5）(转发)
1.OBD用来做什么 2.OBD和UDS的区别 3.OBD硬件接口简介 4.OBD的9大模式介绍 OBD(On-Board Diagnostic)指的是在线诊断系统,是汽车上的一种用于监控车辆状况以及 ...
Board Moves CodeForces - 1353C（数学）
题意: 有一个 n×n 的矩阵(n 为奇数),每个矩阵单元有一个物品,每次操作你可将一个单元里的一个物品移动到该单元周围的八个单元里,问最后只有一个单元有物品的情况下,最少要多少次操作? 题目: Yo ...

On-board Diagnostic（OBD）

On-board Diagnostic（OBD）相关推荐

最新文章

热门文章