You are on page 1of 2
Electronic diagnosis systems have be Jong as digital engine management unite — soma twanty years now. Ia order to monitor vehicle exhaust emissions more effectively, OBD (on- board diagnosis) systems have been mandatory in the USA since 1988. In 1896 the more highly-developed OBD- 2 stendard was introduced. This uni- fled diagnostic interface, standard- ised across manufacturers, was used by the EU Commission as the basis for an EU directive, the effect of Which is to oblige European manutae- turers to incorporate a unified, acces- sible diagnostic interface, to make major parts of their existing diagno. sis systems compatible with one another, and to publish information about them, The EOBD (European on- board diagnosis) system has been mandatory in the EU on all newly- developed models since 2000 for petrol engines and since 2003 for diesel engines. One year later, EOBD became mandatory on first registra- tion for all vehicles (from 1 January 2001 for petrol engines, 1 January 2004 for diesel engines), used in vehicles for almost as OBD-2 Diagnostics connector The requirements for EOBD are mostly included in the ISO standards listed in Table 1. ISO 15031-3 mandates a 16- pin socket which, in contrast to eatlior systems, must now be fitted near the river's seat rather than in the engine compartment. It may be located, for example, below the dashboard, behind a flap in the central console, or even lunder the ashtray. Since this type of connector was already used by some ‘manufacturers for the diagnostics sys- tem (for example, by VW and Audi since 1993), the presence of the con- nector by itselfis no guarantee that the interface conforms to the EOBD stan- 2 published a do- Elektor Electronics back in October and Novem! it turned out to be! Since then, the interface has bi the name EOBD, and is mandatory on all newly-regi At the same time, the number of different proto One connector; many protocols dard. Ifthe vehicle was first registered before the deadlines mentioned abave, itmay be necessary to make enquiries of the manufacturer or look on the Tntemet Some of the pins of the EOBD socket (Figure 1) may not he present, The actual number of pins depends on ‘which protocols are used (see the next section). That is not to say, however, that pins not listed in the pinout charts (Table 2) will necessarily be absent. It can happen that a manufacturer will has risen from three to five, with the CAl more and more succes ‘use these pins for dedicated functions which do not form part of the EOBD standard. Protocols ‘The electronics in a modern car con- sists of a network of microcomputer systems connected together over a bus, called, in automotive engineering circles, ‘electronic control units’, or ECUs. More complex systems such as ‘engine management, ABS, ESP and airbags, each have their own ECU. Of eh eres 74/005, ely PROTOCOLS ‘roller with firmware developed by zen Flektronik from Turkey (5] which is currently the nec plus ultra in ite field: it supports all five protocols (soo ‘Table 3)! This OBD-2 analyser is thus ‘the first EOBD interface using a micro- controller that also supports the CAN protocol. In view of the migration of manufacturers to tho CAN protocol, ‘this support is essential for a future~ proof system. tn most cases using the OBD-2 analyser in conjunction with a note- book will be the most povrerful as well as the most cost-effective and appro- priate solution. A stand-alone OBD analyser with built-in LOD has the advantage that it can easily be used ‘while on the move, and it can even be inetallad permanently Commercial hand-held OBD analysers are, how- ‘ever, stil rather costly, although some hobbyists have built their own, Functions available In recent years OBD-2 has evolved in ‘more than just the protocol used. The range of diagnostic facilities available over the standardised interface has {increased considerably. It is certainly no longer the case (if t has really ever been the case) that OBD-2 can only be used for reading out data related to ‘exhaust gases. Legislators have 50 far only required an OBD-2 or EOED con- nection for control units associated with the power train. Other systems such as ABS, climate control etc., are left to the whim of the manufacturer: they can offer diagnostics over OBD-2 for they can use their own protocols 09 - vehicle data request: information instead, and tako advantage of pins of such as software version and VIN Yhe OBD-2 socket which are not (vehicle identification number) srosorved in the standard. Some manu- facturers already make vehicles where ‘Many further test modes are spscified all the control units are on an OBD-2 _in the standardised extension (secord- ‘compatible network. The extended ing to SAE J2190). Provision is also OBD-2 standard covers all currently- made for future expansion and for ‘used control units as well as those © manufacturer-specific uses. The num- ‘expected in future, so in principle the ber of standardised fault codes has

You might also like