Diagnostic Tools

From PrecisionCodeWorks
Jump to: navigation, search


Diagnostic tools explained

When it comes to diagnostic tools, there are so many on the market that its hard to choose between them. There are a few things to bear in mind before purchasing a tool, So lets take a look.

  • We will start off with the flagship of diagnostic equipment, the AUTOLOGIC ASSISTPLUS [1]. This is the professionals choice of tool for european vehicles. With technology pushing the boundaries everyday, this tool can keep up with the pace. The autologic can take care of pretty much anything you throw at it, and completing various tasks where other fail. For a busy diagnostic/chip tuning workshop, this is the 1st tool of choice.
              01.jpg


Now for the other end of the spectrum.

  • Cheap ebay tools starting at around £10 will not cut it. At best, the only data they will recover are OBD compliant codes. All they can do is a basic read of the error memory. They may show some live data. The seller states that they can do much more, but for £10 what do you expect.
              Scanner.jpg


  • Carrying out checks in engine management for logged DTCs prior to calibration is where basic eobd code readers fail, they can only read generic codes that all manufacturers must use to relate to emissions related failures. Basic eobd code readers cannot usually read manufacturer specific codes. This is where a good scantool is required.


MID RANGE TOOLS

  • Mid range tools like the Autel maxidas, Snap-On Solus range and Delphi DS150e. These are the minimum requirement for chip-tuning and diagnostics. They can read both generic and manufacturer specific DTCs. They can display live PID data and carry out some resets and adaptions. Generally a good base level tool with some functionality.


HIGH LEVEL TOOLS

  • High level Tools such as Snap-On Verus pro, Bosch KTS range, Autel Maxisys have a wider range of applications and more functionality. These are a good choice for chip-tuning as they cover the majority of areas required. Full live data display, DTC read with good descriptor, the ability the clear faults fully from all memories and carry out adaptions/Resets as when required.


DEALER LEVEL TOOLS

  • VAG: VAS5054 or GENUINE VCDS
  • BMW: ISTA
  • MERCEDES: STAR
  • FORD: VCM2
  • JLR: SDD WITH COMPATIBLE J2534 INTERFACE. MOST COMMON IS MONGOOSE
  • PSA: Peugeot Citroen Diagbox Planet & Lexia
  • FGA: NOW USE WITECH, EXAMINERS ARE NO LONGER AVAILABLE. ALTHOUGH A GOOD ALTERNATIVE IS MULTIECUSCAN. 50e for license
  • OPEL: MDI TECH3. THIS IS A MUST FOR OPEL/VAUXHALL JOBS. THIS TOOL IS REQUIRED FOR VEHICLES 2010 ONWARDS. OPCOM IS USELESS
  • REANULT: RENAULT CAN CLIP
  • PORSCHE: PIWIS
  • NISSAN: NISSAN CONSULT
  • TOYOTA: TECHSTREAM
  • MITSUBISHI: MUT3



TOOL REQUIREMENTS FOR CHIPTUNING For DPF/EGR removal the following adaptations are required

  • DPF Regeneration
  • DPF Reset
  • DPF Replacement
  • Differential pressure sensor calibration/replacement
  • EGR Replacement
  • EGR Position calibration


THE FOLLOWING ADAPTATIONS MAYBE REQUIRED AFTER AN ECU FLASH

  • Lambda sensor replacement/calibration
  • Throttle body calibration/reset
  • Intake manifold swirl reset
  • Turbocharger/actuator replacement/calibration
  • over-boost counter reset
  • Airflow meter replacement/calibration
  • CAN network reset/Global error reset
  • Phonic wheel (crank position) reset
  • Neutral position sensor calibration and clutch pedal learn - usually for euro 5 stop start vehicles


Explanation of an EOBD / OBDII fault code (DTCs)

What is a Diagnostic Trouble Code (DTCs)?

  • Diagnostic trouble codes (or fault codes) are codes that are stored by the on-board computer diagnostic system.
  • These are stored in response to a problem found in the car by the system.
  • These codes are stored, for example, when a sensor in the car reports a reading that is outside a pre-defined range, e.g. fuel mixture too rich.
  • The codes identify a particular problem area and are intended to provide the technician with a guide as to where a fault might be occurring within a car.
  • The codes should be used in conjunction with the vehicle's service manual to ascertain which systems,

circuits or components should be tested to fully diagnose the fault.


Reliance on codes alone

  • Parts or components should not be replaced with reference to only a DTC.
  • The vehicle service manual should be consulted for more information on possible causes of the fault, along with required testing.
  • For example, if a DTC reports a sensor fault, replacement of the sensor is unlikely to resolve the underlying problem.
  • The fault is most likely to be caused by the systems that the sensor is monitoring, but might even be caused by the wiring to the sensor itself.
  • DTCs may also be triggered by faults earlier down the line.
  • For example, a dirty MAF sensor might be causing the car to overcompensate in its fuel-trim adjustments.
  • As a result, oxygen sensors are likely to report fuel mixture problems.


Breakdown of a code

  • Diagnostic trouble codes are alphanumeric codes that are used to identify a problem that is present on any of the systems that are monitored

by the on-board computer (ECM or PCM).

  • EOBD and OBD II diagnostic codes are composed of five characters; one letter followed by 4 digits, e.g. P0101.
  • The first character is a letter. It identifies the "main system" where the fault originated. This will be one of the following systems:
  • B Body
  • C Chassis
  • P Powertrain
  • U Network
  • The second character is a numeric digit. This identifies the type of code.

Generic code P0xxx - The definition for the code is defined in the EOBD / OBD-II standard and will be the same for all manufacturers.


Manufacturer-specific P1xxx - These codes do not fall under european standards, so this enables manufacturers to define these codes themselves.

  • In general, codes that begin with P0 are Generic codes, whereas codes that begin with P1 are manufacturer-specific.
  • Additional code groups are however available to allow for expansion of these code lists.

The full breakdown of the code groups is shown below:

Powertrain codes

  • P0xxx - Generic
  • P1xxx - Manufacturer-specific
  • P2xxx - Generic
  • P30xx-P33xx - Manufacturer-specific
  • P34xx-P39xx - Generic
  • Chassis codes
  • C0xxx - Generic
  • C1xxx - Manufacturer-specific
  • C2xxx - Manufacturer-specific
  • C3xxx - Generic

Body codes

  • B0xxx - Generic
  • B1xxx - Manufacturer-specific
  • B2xxx - Manufacturer-specific
  • B3xxx - Generic

Network Communication codes

  • U0xxx - Generic
  • U1xxx - Manufacturer-specific
  • U2xxx - Manufacturer-specific
  • U3xxx - Generic


The third character defines the specific system or sub-system within the car where the problem is located:

  • 1 Fuel and Air Metering
  • 2 Fuel and Air Metering (injector circuit malfunction only)
  • 3 Ignition System or Misfire
  • 4 Auxiliary Emission Control System
  • 5 Vehicle Speed Control and Idle Control System
  • 6 Computer Output Circuits
  • 7 Transmission
  • 8 Transmission
  • It should be noted that manufacturers are not required to follow the generic numbering system above for their manufacturer-specific codes


  • The fourth and fifth characters identify the section of the system causing the fault.
  • There is no detailed list of the components indicated by these digits, as each system or sub-system will have many different components.


What Is CAN?

What is CAN (Controller Area Network)?

  • Controller Area Network (or CAN) is the latest communication system within the automotive world. At its simplest level, it can be thought of as a means of linking all of the electronic systems within a car together to allow them to communicate with each other.
  • As computerisation within a car increases, so to does the number of different electronic systems. The information recorded and processed by each one is often used by one or more others - hence the requirement for a standardised means of quickly passing information between them. This requirement led to the development of CAN.


Background

  • The CAN technology was first developed by Bosch for industrial use, but was quickly recognised as a powerful system for in-car use. Some manufacturers were actually using the technology within their cars from as early as 1992, e.g. Mercedes.


Which cars use the CAN protocol for diagnostics?

  • Within the car diagnostics world, on certain 2003 and newer cars, it is possible to access the CAN network (and communicate with various onboard systems) through the 16-pin OBDII/EOBD diagnostics port. Prior to 2003, manufacturers were required to provide non-CAN interfaces under the OBDII/EOBD legislation, e.g. PWM, ISO etc.
  • Many of these newer cars, e.g. Ford's latest range, Mazda RX-8, the latest Vauxhall Vectra, offer only the CAN protocol/interface as a means of communicating with the engine-management system. This will actually be mandatory on all cars by 2008.
  • Whilst many of these cars might still be under the manufacturer warranty, anyone investing in diagnostic tools for the long term should ensure that their tools support the CAN protocol.
  • The CAN protocol now forms part of the OBDII and EOBD standards. Manufacturers could begin implementing CAN for engine/emissions diagnostic purposes in 2003 and must implement it by 2008.


What are the benefits of CAN-based diagnostics?

  • The CAN protocols and interface run at roughly fifty times the speed of the earlier OBDII/EOBD protocols. This speed improvement, combined with the addition of new diagnostic parameters, will give technicians the ability to see data faster and gain more information from newer cars than is currently available.
  • The original OBDII/EOBD protocols (J1850-PWM, J1850-VPW, ISO-9141 and ISO-14230) did help reduce the number of tools required for engine/emissions fault diagnosis, but by allowing 4 protocols there was still a great deal of confusion, and over-complexity of tools.
  • Simplifying this to a single protocol can only lead to reduce this confusion, and the cost of diagnostic tools.


Which diagnostic port pins are required for CAN?

  • The CAN system uses pins 6 and 14 in the 16-pin diagnostic socket:


Diagnostic connector

  • The car will also need to have pins 4 and 5 (ground pins) and pin 16 (12 Volt supply).


Which cars currently support CAN?

  • A few examples of 2003/4 model cars that require CAN-enabled tools are:
  • Ford Fiesta
  • Ford Focus
  • Ford Fusion
  • Ford Mondeo
  • Mazda 3
  • Mazda 6
  • Mazda RX-8
  • Porsche Cayenne
  • SAAB 9-3
  • Vauxhall Vectra
  • Most new models from all manufacturers from approx. 2004 - CAN must be used for EOBD engine diagnostics by all manufacturers by 2008.

J2534

What is J2534

  • For our American users this subject maybe something that you are already familiar with. SAE J2534 is a standard for communications between a computer and a vehicle. Government regulations require all automakers provide a J2534 service to EVERYONE in the U.S. for re-flashing emissions related controllers. If you own a SAE J2534 Pass-Thru device, you can re-flash and, in some cases, diagnose vehicles with factory functionality.

J2534 diagram.jpg


  • In recent years the EPA, CARB, and European Union have required automotive companies to allow for emissions-related modules (ECM/TCM) to be reprogrammable without use of special and often very expensive factory tools, in an effort to reduce harmful emissions. Because of the success and ease of J2534 some manufacturers have now begun to offer factory diagnostics as well as reprogramming capabilities.


Why do you need J2534

  • Since the introduction of OBD2 and leading up to modern Hybrids and EV's, computers and software in cars have been expanding at an exponential rate. In-car software is becoming one of the leading needs for service, and updating software may be the only way to fix some of these issues:
  • Drivability
  • Fuel efficiency
  • Power loss
  • Fault codes
  • Durability of mechanical parts


What can J2534 do for me?

  • ECU re-flashing aside, Some OE Manufactures offer dealer level support and dignostics without the requirement for expensive Dealer level or tooling. *A well spec'd J2534 pass-thru interface with a comprehensive level of communication protocols, will be compatible with most OEM's.
  • Below is a list of current manufacturers that offer independent shops dealer level support.

Oemlist.PNG


  • As an example from the list above, BMW allows full diagnostic and re-flash capabilities from their website. Some particular vehicles require a 20-pin BMW diagnostic connector.
  • Most BMW’s after 2000 are OBDII vehicles. All BMW’s with the OBD connector require a 7-8 pin adapter to be used with pass-thru diagnostics and re-flashing.
  • Pass-Thru is available on MINI vehicles 2002 and newer.

Overview of the BMW Group Online Service System

1. ISTA Diagnosis Application

  • Automated diagnostic application with vehicle communication with the BMW ICOM or with an SAE J2534 pass-thru tool (from model year 1996)
  • Display of technical information:
  • Automated Test Plans
  • Service Information (SI)
  • Repair Instructions (E30 or higher)
  • Technical Data
  • Tightening torques
  • Inspection Sheets
  • SI Consumables
  • SI Technology
  • SI Diagnostics coding
  • SI Special tools/devices
  • Special tools
  • Wiring diagrams
  • Pin assignments
  • Installation locations
  • Connector views
  • Functional descriptions
  • You can search using document title, document number and subject areas as the search criteria. The desired information is displayed by means of graphics and explanatory text.


2. Web ISTA Information Application Web-based application for quick retrieval of the following:

  • Repair Instructions (E30 or higher)
  • Technical Data • Tightening torques
  • SI Consumables
  • SI Technology
  • Special tools
  • Wiring diagrams
  • Pin assignments
  • Installation locations
  • Connector views
  • Functional descriptions
  • You can search using document title, document number and subject areas as the search criteria. The desired information is displayed by means of graphics and explanatory text.


3. Web KSD Labor Time Guide

  • With Web KSD, you can view the number of flat rate units corresponding to each repair. Based on the vehicle identification number or by selecting the series and model, you can view the flat rate unit data for defined scopes of repair work for each BMW Group vehicle.
  • You can call up information about approved wheel/tire combinations for models from E36 or later.
  • Approved wheel/tire combinations
  • Summer and winter tire recommendations
  • Styling presentation of the wheels
  • Snow chain recommendations


4. ISTA/P Online - Control Module Reprogramming With ISTA/P you can reprogram the onboard control modules that are capable of software reprogramming.

  • For ISTA/P, a data interface, a power supply and an Internet connection are required.
  • The data interface can be an ICOM or the "Pass-Thru Tool (PTT)" that fulfills the requirements of the SAE J2534 standard.
  • Only one vehicle at a time can be handled with ISTA/P.5. P code Lookup Application
  • The P code module allows you to search for standard SAE P codes and BMW-specific P codes, which you can read out from the engine control unit using a generic scan tool. The P code module is especially helpful for users who do not own BMW-specific diagnosis systems, but read out fault codes using a generic scan tool. The corresponding P code can be read out via the vehicle identification number.

Summary

  • So as you can see from the above, a BMW independent specialist can offer full dealer level customer service. No longer having to send vehicles back to the main dealer for system updates, new control unit configuration or simple technical service bulletins.
  • Keep more jobs and profit in house
  • Gain control over the quality of repair
  • Increase shop capabilities = more business

Common car diagnostic acronyms

  • Below is a list of common car diagnostic acronyms:
  • Acronym Explanation
  • AMFR Air Mass Flow Rate
  • CAN Car Area Network / Controller Area Network
  • CTP Closed Throttle Position
  • DTC Diagnostic Trouble Code, see also DTCs
  • ECM Engine / Electronic Control Module
  • ECT Engine Coolant Temperature
  • EGR Exhaust Gas Recirculation
  • ELC Electronic Level Control
  • EOBD European On-Board Diagnostics
  • FMFR Fuel Mass Flow Rate
  • IAC Idle Air Control
  • IAT Input Air Temperature
  • IDM Ignition Discharge Module
  • KOEO Key On Engine Off
  • KOER Key On Engine Running
  • MAF Mass Air Flow
  • MAP Manifold Absolute Pressure
  • MIL Malfunction Indicator Lamp
  • MOP Metering Oil Pump
  • OBD On-Board Diagnostics
  • OBD-II On-Board Diagnostics Second Generation
  • PCM Powertrain Control Module
  • PRC Pressure Regulator Control
  • TCM Transaxle Control Module
  • TFT Transmission Fluid Temperature
  • TPS Throttle Position Sensor
  • WOT Wide Open Throttle