Febi Bilstein leaderboard September 2020
NGK leaderboard Sept to Nov 2020
Walker Products leaderboard September 2020
Bosch leaderboard July 2020 on
House leaderboard ad for subscriptions Aug 20 on
Sealey secondary leaderboard Sept 2020
ZF secondary leaderboard Sept 2020 on
Philips secondary leaderboard September 2020

Deciphering the code

0

When a vehicle is presented with multiple faults it is difficult to know which one to tackle first, or which fault is going to relate to the customer concern. A classic example was an Audi Q5 which was here at Gotboost’s workshop recently.

The customer complaint was an intermittent lack of performance accompanied by warning lights on the dashboard. The fault started happening occasionally a few months ago but was now becoming more frequent and occurred on all trips lasting over 20 minutes. The customer had an EOBD code reader and was able to extract and clear the fault codes but was unable to determine the cause from the codes alone.

At the time the vehicle was presented, the fault had not occurred on that journey. So, a test drive was conducted until the symptoms became apparent. The following five codes were stored in the Engine Electronics Module:

  • 4698 (U1113-00) Functional impairment due to received fault value (Sporadic)
  • 4124 (P0651-00) Sender reference voltage ‘B’ open circuit (Sporadic)
  • 4881 (P1440-00) EGR Valve N18 open circuit (Sporadic)
  • 4087 (P0322-00) Engine speed sender G28 no signal
    (STATIC)
  • 5243 (P0191-00) Fuel pressure sender G247 implausible signal (Sporadic)

 

Some vehicles can store more than just the code and the fault description when a failure occurs, and this additional data is presented in a ‘freeze frame’. A bit like the black box on an airplane, it captures a snapshot of the operating conditions  at the time the fault code was triggered. The extent of the data captured varies but it can provide some useful additional information. This can be used in a number of ways and should always be saved before clearing the diagnostic data.

In this case, each code description was accompanied by the following information:

  • Time
  • Date
  • Odometer Reading
  • Fault Priority
  • Malfunction Frequency Counter
  • Unlearning Counter/Driving Cycle
  • Engine Speed
  • Calculated Load Valve
  • Vehicle Speed
  • Coolant Temp
  • Intake Air Temp
  • Ambient Air Pressure
  • Voltage Terminal 30

 

The date, time and mileage counters are useful for matching codes with a customer complaint, enabling the technician to select the codes that arose at the same time as the customer outlined during the diagnostic interview. The fault priority is a classification used by VAG to rank the fault on its influence on drivability as outlined in the table.

The date, time and mileage counters are useful for matching codes with a customer complaint, enabling the technician to select the codes that arose at the same time as the customer outlined during the diagnostic interview. The fault priority is a classification used by VAG to rank the fault on its influence on drivability as outlined in the table.

No.

Meaning

1

The fault has a strong influence on drivability, an immediate stop is required.

2

The fault requires an immediate service appointment.

3

The fault doesn’t require an immediate service appointment, but it should be corrected with the next service appointment.

4

The fault recommends an action to be taken, otherwise drivability might be affected.

5

The fault has no influence on drivability.

6

The fault has a long term influence on drivability.

7

The fault has an influence on the comfort functions but doesn’t influence the car’s drivability.

 

Figure 1

The malfunction frequency counter displays the number of times the fault has occurred since the diagnostic data was last cleared. The unlearning counter counts back from the number of drive cycles that must be completed before the fault clears itself (Maximum 255, but it can be less depending on the faultcode). Each time a drive cycle is completed without the fault occurring the counter counts back, a useful indicator of a faultthat is no longer present but has not been cleared using a scan tool. The rest of the data is self-explanatory and concerns itself with the operating conditions of the engine when the fault triggered the code.

The owner of the Q5 had unwittingly removed much of this additional evidence by clearing the codes, which also clears the freeze frame data. A useful piece of information is the fault status, Static or Sporadic in this case, is used to describe whether the fault is permanent or intermittent in nature.

Using the additional information presented we were able to build a picture of what was happening, see Figure 1.

Here’s a summary of what we know from just the fault codes, freeze frame data and a quick look at a wiring diagram:

  • All the codes are linked to the 5V reference circuit – this information was obtained from the wiring diagram.
  • The EGR valve is the component that has triggered the most faults (5).
  • The engine speed sensor fault is current.
  • The highest fault priority is 2, the fault requires an immediate service appointment, for all but the Functional impairment Code, which has a priority of 6
  • All the faults occurred on either the drive to the workshop or during the test drive – identified by the mileage, date and time stamps.
  • The operating condition reported via the freeze frame data snapshots proves that this fault ‘trips’ its monitors once the engine has warmed up, and when the vehicle is driven under light load. So, this condition must be matched after the repair to ensure that the fault will not reoccur when the vehicle is handed back to the customer. It also highlights the problem with the approach of clearing codes and only concerning yourself with the codes that return immediately as a diagnostic procedure.
  • Monitors only run under conditions when components/ systems are likely to pass, to prevent erroneous fault codes being generated. They monitor the operation of components, circuits and vehicle systems in a number of ways. Once ideal conditions are met, they operate either continuously or non-continuously, testing against fault enabling criterion. Understanding how monitors operate can explain how a vehicle can have an obvious fault but no code stored. 

 

Figure 2

Knowing this enables us to develop a test plan to prove what is causing the fault. The most likely suspect is the EGR Valve, followed by the engine speed sensor, based on the information provided by the freeze frame relating to the frequency and status of the monitor failures.
Using an oscilloscope, the 5V reference was measured on three of the circuits concerned and the engine speed signal hall output. After a short period of driving the Audi dropped into limp home mode, the 5V reference had been compromised as shown in the screen capture. Unplugging the EGR valve electrical connector restored the 5V reference voltage and restored the engine speed signal as shown in the screen capture, Figure 2. Removing the EGR Valve cover presented us with further evidence, if it was needed, for the cause of the failing 5V reference, see Figure 3. 

Figure 3

 

 

Tags: , , , , , ,

Share.

About Author

Leave A Reply