OBD I (ON BOARD DIAGNOSTICS VERSION ONE)

Discussion of STOCK TripMinderĀ®, audio, video, LED, capacitors, instrument clusters and controls, integrated circuitry and boards, low voltage, message center, resistors, speedometers, tachometers, transistors and systems.

OBD I (ON BOARD DIAGNOSTICS VERSION ONE)

Postby admin » Tue Sep 26, 2017 9:29 pm

OBD I (ON BOARD DIAGNOSTICS VERSION ONE)

Pertaining to our Lincoln Mark VIIs, as printed at Wikipedia (https://en.wikipedia.org/wiki/On-board_ ... cs#History)

History
1968: Volkswagen introduces the first on-board computer system with scanning capability, in their fuel-injected Type 3 models.
1978: Datsun 280Z On-board computers begin appearing on consumer vehicles, largely motivated by their need for real-time tuning of fuel injection systems. Simple OBD implementations appear, though there is no standardization in what is monitored or how it is reported.
1980: General Motors implements a proprietary interface and protocol for testing of the Engine Control Module (ECM) on the vehicle assembly line. The 'assembly line diagnostic link' (ALDL) protocol broadcasts at 160 bit/s Implemented on California vehicles for the 1980 model year, and the rest of the United States in 1981. Most owners can read DTCs (Diagnostic Trouble Code(s)) by commanding the ECM (Engine Control Module) to flash the CEL (Check Engine Lamp) or MIL (Malfunction Indicator Lamp) on and off. A PC based Software package called WinALDL will listen to the CLCC (Closed Loop Carburetor Control) and early CLC EFI datastreams over a fairly easy to construct interface cable that converts the 160 baud TTL serial data being transmitted by the ECM to RS232[1] or USB[2] serial data but there is not much information transmitted by these early ECMs.
1986: An upgraded version of the ALDL protocol appears which communicates at 8192 bit/s with half-duplex UART signaling. This protocol is defined in GM XDE-5024B.
1988: The Society of Automotive Engineers (SAE) recommends a standardized diagnostic connector and set of diagnostic test signals.
1991:[3] The California Air Resources Board (CARB) requires that all new vehicles sold in California in 1991 and newer vehicles have some basic OBD capability. These requirements are generally referred to as "OBD-I", though this name is not applied until the introduction of OBD-II. The data link connector and its position are not standardized, nor is the data protocol.
~1994: Motivated by a desire for a statewide emissions testing program, the CARB issues the OBD-II specification and mandates that it be adopted for all cars sold in California starting in model year 1996 (see CCR Title 13 Section 1968.1 and 40 CFR Part 86 Section 86.094). The DTCs and connector suggested by the SAE are incorporated into this specification.
1996: The OBD-II specification is made mandatory for all cars manufactured in the United States to be sold in the United States.
2001: The European Union makes EOBD mandatory for all gasoline (petrol) vehicles sold in the European Union, starting in MY2001 (see European emission standards Directive 98/69/EC[4]).
2003: The European Union makes EOBD mandatory for all diesel cars sold in the European Union
2008: All cars sold in the United States are required to use the ISO 15765-4[5] signaling standard (a variant of the Controller Area Network (CAN) bus).[6]
2008: Certain light vehicles in China are required by the Environmental Protection Administration Office to implement OBD (standard GB18352[7]) by July 1, 2008.[8][9] Some regional exemptions may apply.
2010: HDOBD (heavy duty) specification is made mandatory for selected commercial (non-passenger car) engines sold in the United States.
User avatar
admin
SITE ADMIN
 
Posts: 449
Joined: Sun May 17, 2009 9:14 pm

Return to Electronic

Who is online

Users browsing this forum: No registered users and 1 guest