01044 - CONTROL MODULE INCORRECTLY CODED

CONTROL MODULE INCORRECTLY CODED

Since 1994 auto repairs has drastically changed, so much so that most cars cannot be repaired  without a diagnostic code tester. It is therefore advantages to invest in one of the hand held free standing devices or cable interfaces that plugs into a USB port of a laptop computer running the appropriate software to do the necessary. The best software to date for Vag cars is undoubtedly VCDS from Ross Tech. Their latest version is version 14. The software is absolutely free but the interface cable comes at a cost. It is a bit pricy but its a worthwhile investment since it entitles you to free updates for life. This interface cable has a built in PAL chip which doubles-up as a dongle containing the cable activation code. Even though there are several out-band 3rd party interface cables available on the market, none of them gives you the confidence that a VCDS HEX-CAN automotive diagnostic device, that is backed by a service company ready to help with any automotive queries, gives you. Bare in mind that this software has the ability to change the behaviour of the electronic control systems built into your car which can result resulting in catastrophic effects if not performed correctly. If you lack the competence or confidence to perform these operations, or even if you are unfamiliar with or the software, I urge you to refrain from changing anything and obtain an experts advice or assistance. Write down or print out all codes and settings so that it is easy to revert back to them.

Below are just a few of the faults that have popped-up on various vag cars over the past few years. Since the codes cover all Vag cars, the code "01044 - Control Module Incorrectly Coded" has occurred several thousand times in all makes and models of Vag cars, in all languages and countries throughout the world.

01044 - CONTROL MODULE INCORRECTLY CODED

01044 - Modul de comanda: codare incorecta
        35-00 -  -

01044 - Steuergerät falsch codiert
        35-00 -  -

01044 - Módulo de control codificadas incorrectamente
        35-00 -  -

01044 - Modul za kontrol Nepravilno Kodiran
        35-00 -  -

01044 - module de commande codées correctement
        35-00 -  -

01044 - Control Module ongecodeerde
        35-00 -  -

01044 - Beheer Module Verkeerd Gekodeerde
        35-00 -  -

01044 - Upravljački modul Pogrešno Coded
        35-00 -  -

01044 - Control Module Nepareizi Coded
        35-00 -  -

01044 - 控制模塊編碼不正確
        35-00 -  -

01044 - Kòngzhì mókuài biānmǎ bù zhèngquè
        35-00 -  -

01044 - Modul de control codificate incorect
        35-00 -  -

01044 - Kontrolli Module kodifikua Gabimisht
        35-00 -  -

01044 - وحدة التحكم الأكواد بشكل غير صحيح
        35-00 -  -

01044 - Řídicí modul nesprávný kód
        35-00 -  -

01044 - Modul Kawalan Salah Dikodkan
        35-00 -  -

01044 - Kontrol Modülü hatalı Kodlu
        35-00 -  -

01044 - Control Module Felaktigt Kodad
        35-00 -  -

Genuine VCDS cable and Software from Ross Tech.

What I find most intriguing is that for most DTC codes, VW offers some sort of help by using words like "intermittent" " implausible" "short circuit" "limit exceeded", etc.. like these faults below, but the 01044 faulty code featured above offers absolutely none. However, I have included some data below that may be of some help. Should you find these codes helpful, all I ask is for you to like my site on G+1 , Facebook, Twitter, Pinterest, etc.

00532 - Supply Voltage B+
07-10 - Signal too Low - Intermittent

01044 - Control Module Incorrectly Coded
35-00 -  -

01179 - Incorrect Key Programming
35-00 - -

01179 - Incorrect Key Programming
005 - No or Incorrect Basic Setting / Adaptation

00852 - Loudspeaker(s); Front
44-00 - Short Circuit

16795 - Secondary Air Injection System: Incorrect Flow Detected
P0411 - 35-00 -  -

01044 - Control Module Incorrectly Coded
35-00 - -

00933 - Electric Window Motor; Passenger Side (V148)
62-10 - No or Incorrect Adjustment - Intermittent

16795 - Secondary Air Injection System: Incorrect Flow Detected
P0411 - 002 - Lower Limit Exceeded

16825 - EVAP Emission Control Sys
P0441 - 35-10 - Incorrect Flow - Intermittent

00928 - Locking Module for Central Locking: Front Driver Side (F220)
27-00 - Implausible Signal

VW 9N CODES FOR:
CONTROL MODULE INCORRECTLY CODED

If  one of the following controllers is fitted in your car, try each of these codes individually  and you are guaranteed to solve your " Control Module incorrectly coded" problem, providing you have just changes the coding of one module or replaced only one module.  I need to stress as I have in a previous blog that every Control module that is fitted in your car has a prefered coding which is subject to the equipment it supervises. As such, its coding is stored as an onboard binary number, which in essence is the binary sum of the features for that specific module. Whereas the master ECU / Ctrl Head Dash  also stores an onboard binary number which in essence is the binary sum of all the Control Module's coding fitted in the car. This binary sum is called the checksum and any incorrectly coded  module will result in an erroneous checksum. If this is the case, the erroneous checksum is compared to a reference checksum also stored in the ECU module and any discrepancy could incapacitate your Volkswagen completely or present you with some peculiarities and error codes to match. Like the notorious 01044 control module incorrectly coded error. Checksum verification was adopted by BOSCH Motronic ECUs to validate its EPROM's stored data. So, it is wise not to change the coding or replace any control modules in your VW AUDI, SKODA or SEAT unless you are au fait with binary and hexadecimal number systems.

Address 09: Cent. Elect. [21343 login]
Component: 0009 BN-SG. 2S36

Controller: 6Q1 937 049 F
Coding: = 09870 / 09390 / 08332 / 25742 / 26030 /
26254 / 00004 / 09358 / 16396 / 08588 / 08204 /
00004 / 09646 / 24716 / 25743 / 24588 / 17422 /

Controller: 6Q1 937 049 D
Coding: = 00140 / 16524 / 09406 / 17422 / 25610 /
25614 / 25774 / 09358 / 25646 / 00012 / 01166 /
25774 / 25742 / 09870 / 09390 / 09646 /

Controller: 6Q1 937 049 C
Coding: = 09358 / 09390 / 00140 / 16396 / 25742 /
00012 / 25742 / 26046 / 25614 /

Controller: 6Q1 937 049 B
Coding: = 25754 / 09374 / 00140 / 17594 / 25758 /

Controller: 6Q1 937 049
Coding: = 00141 / 09234 / 09870 / 09362 / 09358 / 09394 / 09646 /

Address 09:  Cent. Elect.  [21343 login]
Component: 0000 BN-SG. 2S36
Address 09: Controller: 6Q1 937 049 F Coding: 09358
Address 09: Controller: 6Q1 937 049 F Coding: 25742
Address 09: Controller: 6Q1 937 049 F Coding: 25743

Address 09:  Cent. Elect.  [21343 login]
Component:  000B BN-SG. 2S36
Address 09: Controller: 6Q1 937 049 F Coding: 08588
Address 09: Controller: 6Q1 937 049 F Coding: 16524
Address 09: Controller: 6Q1 937 049 F Coding: 24716

NB! More component codes in the next blog ...

INSTRUMENT CLUSTER / IMMOBILIZER / KOMBI
6Q0 920 825

Component: KOMBIINSTRUMENT VDO V06
Address 17: Instruments Controller: 6Q0 920 825 E Coding: 01144

Component:  INSTRUMENT CLUSTER VDO V07
Address 17: Instruments Controller: 6Q0 920 825 E Coding: 01144

Component: KOMBIINSTRUMENT AGD V05
Address 17: Instruments Controller: 6Q0 920 825 F Coding: 01132

Component: KOMBIINSTRUMENT AGD V02
Address 17: Instruments Controller: 6Q0 920 825 F Coding: 01132

Component: KOMBIINSTRUMENT AGD V04
Address 17: Instruments Controller: 6Q0 920 825 F Coding: 01132

Component:  KOMBIINSTRUMENT VDO V06
Address 17: Instruments Controller: 6Q0 920 825 F Coding: 01132

Component: KOMBIINSTRUMENT VDO V03
Address 17: Instruments Controller: 6Q0 920 825 G Coding: 01132

Component: KOMBIINSTRUMENT VDO V06
Address 17: Instruments Controller: 6Q0 920 825 G Coding: 01132

COMPONENT KOMBIINSTRUMENT VDO V06
Address 17: Instruments Controller: 6Q0 920 825 H Coding: 01141

Component: KOMBIINSTRUMENT VDO V06
Address 17:  Instruments Controller: 6Q0 920 825 J Coding: 01142

Component: KOMBIINSTRUMENT VDO V05
Address 17:  Instruments Controller: 6Q0 920 825 K Coding: 01148

Component:  KOMBIINSTRUMENT VDO V02
Address 17:  Instruments Controller: 6Q0 920 825 L Coding: 01148

CENTRAL CONVENIENCE

Address 46:
Controller:Central Conv.

06 Komfortgerát 0002 6Q0 959 433 C Coding: 00067
07 Komfortgerát 0002 6Q0 959 433 C Coding: 00259

63 Komfortgerát 0002 6Q0 959 433 E Coding: 00016
3  Komfortgerát 0002 6Q0 959 433 E Coding: 00016
5F Komfortgerát 0002 6Q0 959 433 E Coding: 00017
   Komfortgerát 0002 6Q0 959 433 E Coding: 00018
63 Komfortgerát 0002 6Q0 959 433 E Coding: 00016
64 Komfortgerát 0002 6Q0 959 433 E Coding: 00019
65 Komfortgerát 0002 6Q0 959 433 E Coding: 00018
67 Komfortgerát 0002 6Q0 959 433 E Coding: 00018
3F Komfortgerát 0002 6Q0 959 433 E Coding: 00018
3F Komfortgerát 0002 6Q0 959 433 E Coding: 00019
2F Komfortgerát 0002 6Q0 959 433 E Coding: 00064
4y Komfortgerát 0002 6Q0 959 433 E Coding: 00065
4z Komfortgerát 0002 6Q0 959 433 E Coding: 00065
6K Komfortgerát 0002 6Q0 959 433 E Coding: 00065
4U Komfortgerát 0002 6Q0 959 433 E Coding: 00066
4M Komfortgerát 0002 6Q0 959 433 E Coding: 00064
31 Komfortgerát 0002 6Q0 959 433 E Coding: 00067
4T Komfortgerát 0002 6Q0 959 433 E Coding: 00258

   Komfortgerát 0002 6Q0 959 433 F Coding: 00018
   Komfortgerát 0002 6Q0 959 433 Coding: 00021

J2 Komfortgerát 0002 6Q0 959 433 G Coding: 00064
20 Komfortgerát 0002 6Q0 959 433 G Coding: 00065
41 Komfortgerát 0002 6Q0 959 433 G Coding: 00017

1N Komfortgerát 0002 6Q0 959 433 H Coding: 00018
2Y Komfortgerát 0002 6Q0 959 433 H Coding: 00018
1N Komfortgerát 0002 6Q0 959 433 H Coding: 00019  
1R Komfortgerát 0002 6Q0 959 433 H Coding: 00067
0H Komfortgerát 0002 6Q0 959 433 H Coding: 00067

CONTROL ARM RUBBERS

VW POLO CONTROL ARM & TIE-RODS

A couple of weeks ago to my surprise,  I discovered that my car's front tyres were running  smooth on the inside.  It was that bad that I needed to replace them but somehow I never noticed until from a distance, I saw something white stuck to the right side front tyres. I was thinking it may be a sticky sweet wrapper that got stuck to the thread, so I went to remove it. That’s when I saw it was a patch of shining wire protruding through the rubber. I was dismayed. The outer edge up to the middle of the tyre had perfect thread, at least 4mm or more but the inside was bald as an egg. 

My VW Polo getting the full treatment.

Thats where the control arm rubbers sits, 

There was no way I was going to fit brand new tyres and allow the same to happen to them. I suspected that the alignment went awry so I drove my car in that condition to determine whether I was right or wrong. I released the steering on a straight road a few times and every time the car veered to the left, towards the pavement. Convinced that it was alignment, I fitted my spare wheel and took my VW Polo Highline for wheel alignment to get it sorted before replacing the tyres.

New VW control arm rubbers / cleaned-up VW control arms

Busted rubber boots on both and left tie-rod ends, due for replacement.

 After waiting for more than an hour at the wheel alignment centre, it was eventually my turn to get service. My car was hoisted about hip high on the lift. The technicians then jacked-up the front wheels placed metal pad of sorts under each of the front wheels which was part of the wheel alignment sensor equipment that they later fitted to all four wheels. They then centred the steering wheel, locked it in place with a mechanical device and fired up the diagnostic computer/programme to check my car's wheel alignment. A good 15 minutes later they discovered that their version of the diagnostic software did not have the settings for a VW Polo 2.0 litre Highline. In fact there wasn't even a 2.0 litre Polo category listed.

Front and back view of new tie-rod ends.

There is absolutely no difference between the original ans pirate part other than the VW logo

The technician scrolled through the entire list a couple of times before he gave up and told me that they are stuck without the correct setting and therefore cannot do the alignment. I asked, what about trying the software for one of the other VW Polo models. Considering all the Polo's are the same shape and size and that it’s only the engine capacity that vary, perhaps it may work.  So he tried the 1.8 litre setting which showed my Polo's alignment was perfect and that there was no error. He then tried the 1.6 and the 1.9TDi software, both with the same results -no problem. I protested “How can that be? Look at my front tyres! Now that the car's tyres were eye-level the left tyre was almost just as bad as the right one. The technicians agreed that there is a problem and started speculating that if both my swing arm rubbers were uniformly perished the alignment would  technically still be in but the car would veer off the road and the tyres would run bald on either the inner or outer edge. They lifted the car higher and pushed a tyre lever into the control arm rubbers and convincingly said the one side is definitely broken.  Thank you very much and off I went.

Left image shows left Control arm Rubber, Right image shows right side.

Left and Right Control Arm Rubbers

Back at the VW service agents, 2 x control arm rubbers please. Yes, we have stock, R1200 (+/-$120) please. What! For two pieces of rubber? But since I needed it, I paid. Back home I jacked-up the car, placed it on car stands and stripped the front suspension until I removed said rubbers. By the way, I found the boots on tie-rod ends torn so back to the agents I went. "Sorry out of stock, expecting stock to arrive in 40 days". This was unacceptable so off to the local motor spares I went in search of tie-rod ends. I found them sold together with the control arm rubbers at R180 each, tie-rod ends R120 each. Everything together cost me R600 ($60), exactly half of what I already spent on rubbers alone. So after I fitted them to my Polo, I returned the Control arm rubbers to the VW agents for a full refund.  Amazingly the car now drives normal, no veering to the left or right and the alignment centre still says my alignment is normal, even though they or none of the other service centres they phoned have the software alignment settings for my 2.0L Polo highline. I now realise that she's an oddball.

EPC DEMYSTIFIED CONTINUED 2

Continued from EPC DEMYSTIFIED CONTINUED 1.

  ...  I only became aware of this when my EPC light went on due to the knock sensor. See picture blog.  More...

 PART 3

BREAKING THE CODE

What needs to be mentioned as a basis of understanding, is that OBD (on-Board Diagnostics) was introduced in the 70's along with CDI (capacitive discharge ignition systems) as DIY kits. Few cars had fuel injectors, points and coils were fast being taken over by electronic modules. During this time some standards were introduced but they were not very well defined and as such manufacturers developed their own and applied their specific systems and developed their own code descriptions which later became known as OBD1. This was considered undesirable and counterproductive since none franchised service, and general mechanical repair centers had to purchase different scan tools, interface cables and connectors, skills and manuals for each make and model of car they specialized in. This resulted in vehicle diagnostics becoming unwieldy expensive. In February of 1986, Robert Bosch founder of Bosch, introduced the CAN (Controller Area Network) serial bus system to  the Society of Automotive  Engineers (SAE) in motor town of Detroit.

This influenced the  Society of Automotive  Engineers (SAE) who subsequently drafted a list of standards and practices that aught to be implemented by all automobile  manufacturers and recommended them to the Environmental Protection Agency (EPA). The EPA weighed-up these standards and recommendations, acknowledged their benefits, and adopted them. The standards criteria included a precisely defined diagnostic connector for each auto manufacturer, a standard scan tool and a common electrical communications protocol and a common data format, and the ability to monitor other
vehicle parameters. Lastly that the standard scan tool should interface with vehicles of all manufacturer. It also included mandatory definitions and descriptions for certain emission control system  defects which was labeled the ‘P0’ Codes. Manufacturers were allowed to generate and use their own ‘manufacturer specific code descriptions’ known as ‘P1’ Codes. This collaboration of standards became known as OBDII, (OBD2) and was adopted for implementation by January of 1996. Two types of scanner codes, namely manufacturers codes like VAG codes and SEA Codes are now the standard practice.

OBD-II  

As mentioned above, Powertrain Control Module (PCM) error codes are assigned the prefix P and pertain to the, Engine management, Transmission management, Fuel Pump and Gasoline Management, Automatic Transmission – Hydraulic Control, Emission control system, evaporative emission purge control (HVAC), Auxiliary module management and other some 0n-board Hybrid application.  For example P1340  suggests that the Powertrain triggered a DTC and describes it as an "Crankshaft-/Camshaft Position Sensor Signals Out of Sequence"

From the above example it would thus be easy to interpret the DTC below relating to EPC (Electronic Power Control)

DTC (VAG)   DTC (SAE)  Society of Automotive  Engineers

16504 P0120 Throttle Position Sensor A - Circuit Malfunction
16505 P0121 Throttle Position Sensor A - Circuit - Performance Problem - Out of Range
16506 P0122 Throttle Position Sensor A Circuit - Low Voltage Input
16507 P0123 Throttle Position Sensor A Circuit - High Voltage Input
16894 P0510 Throttle Position Sensor - Closed Switch- idle micro-switches -F60 malfunctioning
17951 P1543 Throttle Actuation Potentiometer - Signal too Low
17952 P1544 Throttle Actuation Potentiometer - Signal too High
17913 P1505 Throttle idle micro-switches -F60 not/short-circuit opens
17914 P1506 Throttle idle micro-switches - Switch Does Not Open/Short to Ground
17988 P1580 Throttle Actuator (B1) Fault - May be caused by low battery if found with 16487 (P0103)

18038 P1630 Accelerator Pedal Position -G79 signal too small  (low)
18039 P1631 Accelerator Pedal Position -G79 signal too largely (high)
18040 P1632 Accelerator Pedal Position -G79 supply voltage malfunction
18041 P1633 Accelerator Pedal Position -G185 signal too small
18042 P1634 Accelerator Pedal Position -G185 signal too largely
18047 P1639 Accelerator Pedal Position 1+2 Range/Performance -G79 and -G185 implausible signal
18048 P1640 Internal Controller Module defective (EEPROM) Error

EPC Circuit.

The EPC  circuit consists of a number of disparate components that control and supervise, regulate and determine the throttle valve position at all times. They include;

1) the accelerator pedal position sender (TP sensor G69)
2) the accelerator pedal position sender -2, (G185)
3) Black 6-pin plug with 6-pin with Gold plated contacts

NB! The above three components are part of the accelerator pedal.

4) the throttle valve control module (unit),
5) the K132 EPC fault lamp, (electronic throttle control fault indicator)
6) the engine control module (unit).

Firstly we going to do a test on components 1, 2 and 3 above. To do this test, you need a Fluke multimeter or similar for a voltage and continuity / resistance test. Unplug the 6-pin plug from the accelerator pedal and switch on the ignition. Connect the multimeter and check for a 4.5 volt reading between;-

pin 1 and ground, then between pin 1 and pin 5
Pin 2 and ground, then between pin 2 and 3.
If tests prove to be "OK", switch ignition off.
Do additional checks for short circuits between one another and ground and if this checks "OK",

Locate the ECU, normally inside cowl. Disconnect the ECU from its socket, identify pins 34 & 34, 35 & 36, and 72 & 73 on the socket. Disconnect the 6-pin plug from the accelerator pedal once again and check for continuity between this plug and the ECU socket. There should be continuity between pins:-

1 of the 6-pin plug and pin 72 of the ECU socket.
2 of the 6-pin plug and pin 73 of the ECU socket.
3 of the 6-pin plug and pin 36 of the ECU socket.
4 of the 6-pin plug and pin 35 of the ECU socket.
5 of the 6-pin plug and pin 33 of the ECU socket.
6 of the 6-pin plug and pin 34 of the ECU socket.

Any resistance above 1.5ohms should be investigated for corrosion. This often causes the engine to surge (idle unevenly or rather breaths) However, if this test proves "OK" and no wiring malfunction is detected, replace G69 and G185 (single unit) on the accelerator pedal. NB! these components are non adjustable and needs to be replaced as a whole.

When the ignition is turned on, the ECU checks all EPC components necessary for the proper  functioning of the Electronic Power Control. If a malfunction is detected in the EPC (Electronic Power Control) system whilst the engine is running, the ECM will simultaneously activate the EPC (Electronic Power Control) warning light and make an entry of this malfunction in  the ECU (electronic Control unit) DTC (Diagnostic Trouble Codes non-volatile memory.  By a process of eliminate the EPC fault can be fixed.

The list below categorises VW and Audi manufacturer predetermined data groups which varies depending on the vehicle, year, engine, engine code and management system on board.

Group Number / Group Category

1–9     General engine activity data
10–19 Ignition data
20–29 Knock control data
30–39 02 sensor control system data
40–49 Three-way CAT data
50–59 Engine speed control data
60–69 Throttle drive data
70–79 Emissions reduction data
80–89 Special function data
90–97 Power increase data
98–100 Compatibility data
101–109 Fuel Ignition data
110–119 Boost pressure control data
120–129 Control unit communication data
130–150 Special info data

Based on the data from the above table EPC problems are associated with group 60-69. However, on Expert Systems Diagnostics Group 60, holds the EPC Adaptation data, group 61 holds EPC-system 1 data and group 62 holds the EPC system 2 data. Group 66 holds the speed-o-cruise data.

NB! If you found this information useful, please link to this page.

EPC DEMYSTIFIED CONTINUED 1

Continued from EPC DEMYSTIFIED.  

  ....But it’s not that simple. There is a lot more to it than meets the eye.....

 PART 2

But it’s not that simple. There is a lot more to it than meets the eye. Cars exclusively use embedded microcontrollers (µContollers) with embedded firmware in preference to microprocessors with loadable software. In order for a microprocessor to function properly in any device, it must contain dedicated internal circuitry and firmware specific to its function, have inputs and outputs and an oscillator circuit among other circuitry and an OS (Operating system). A DVR (Digital Video recorder), or a PVR (personal Video recorder) or a set-top-box or embedded network appliance or data router are just a few examples of such systems. µControllers  are less significant and less sophisticated than microprocessors, more dedicated to its specific need, often cheaper, faster, safer and smaller. Embedded µControllers are therefore the natural choice for car manufacturers. And there are several manufactures that produce µControllers families specifically for the motor trade.

So it should be understood that companies like Bosch, Digifant, Delco  and other engine management ECU manufacturers and electronic module manufacturers uses the same microcontroller chip families or similar microcontroller chip families, designed and manufactured for them by a selected few silicon chip manufacturers.  In the same vein, computer manufacturers like IBM, Dell, Sony, Toshiba and Lenovo, etc. all use microprocessors manufactured by Intel Corporation or AMD in their laptops and computers, whereas Apple uses microprocessors manufactured by Motorola.

Baring in mind, that much like Motorola, Intel Corporation and AMD produces different featured microprocessor chips with different instruction sets,  along with their auxiliary support chips for low-end and high-end computers; such as 4 bit, 8bit, 16bit, 8086 family of chips, 32bit Pentiums, I5, I7, 64bit, XEON, 128bit big Endian and small Endian microprocessors etc; so does Infineon, Altera, Freescale, Atmel and ARM etc, manufacture different featured microcontroller chips for both low-end cars and high-end cars which are specifically chosen for their internal features and software by the various ECU and electronic module manufacturers like  Bosch,  LUCAS, DENSO, Delco, DELPHI, FENIX, HITACHI, HELLA,  MARELLI, Siemens, etc. These microcontroller chip families can roughly be categorized into four sub sectors, those specific to Powertrain functions (P), those specific to the Body and Safety functions (B), those with specific functions for Chassis (C) and those specific to Internal Convenience & communication(U).

In a nutshell all the sub systems in your vehicle are controlled by these on-board computer chips, each at the heart of an electronic module flanked by associated components and sensors. Each of these modules are in fact a fully fledged computer in its own right, situated in various positions throughout the car and linked together by a wired networked called a network bus and all are accessible through the Databus diagnostic interface for adaptation.

When the ignition is switched on, several dashboard warning lamps light-up and stays lit for the duration of the internal test cycle (<30 seconds). Should all tests check OK, all lights goes however if all systems does not check out OK, the relevant light will stay on and a fault will be logged in memory . After the car is started, the ECU monitors all sensors  and continually takes readings from the complete range of powertrain modules and sensors. These readings are then compared with default readings stored in the operational logic of the  system. Should the sensor reading coincide and agree with the stored program value or values, the microcontroller will send the  required outputs to the relevant actuators, for example the injectors. If the sensor readings differ and are out of specification,   "not within the required limits",  it will take another and if this sensor reading continues to be ‘out of limits’ a DTC will be triggered and sent to non-volatile memory. Depending on the nature of the fault, the embedded program may or may not instruct the microcontroller to make internal changes, thus operate on different criteria until a repair is effected, or until the fault has been cleared.

So whenever a mechanical or electronic problem arises in either the Powertrain (P), the Body (B), the Chassis (C) or the internal Conveniences & Communication (U) areas, the relevant module or modules triggers the on-board self diagnostics program and generates a DTC (Diagnostic Trouble Code) which is then stored in the non-volatile memory of the ECU for later retrieval by mechanical technicians. At the point When a DTC code is logged in memory, the system self-diagnosis system also alerts the driver with a visible indication  of trouble by turning on a warning light on the dashboard like the "EPC light", or the "Malfunction Indicator Lamp" (MIL) which on European cars is known as the "Check Engine Light". This doesn't tell you  the nature of the problem, even though it could be something serious, or not. After the necessary repairs are completed, a diagnostic scan tool should be used to clear the DTC errors  and to turn the malfunction indicator light (MIL) or EPC light off. Thereafter the car should be taken on a short test dive to ascertain that the previous drive issue or issues are resolved. Then the car should be hooked up to the diagnostic scan tool once again in order  to confirms that the DTC or DTCs is also no longer present.

The nature of such mechanical problem may  prevent the engine from starting or it may idle erratically, switch off immediately after starting, refuse to rev higher than 1500 rpm and impede driveability (limp mode), difficult cold starting, misfire, lazy acceleration, high idling speed, fluctuating rev counter, excessive fuel consumption, difficult warm starting, excessive black smoke, poor engine response or emits blue/grey smoke,  etc ... Each of these faults and so many others each produce individualized codes.   In most cases it would be expedient to engage the services of a roll-back to get your car to a VW service center so that diagnostics can be run on the car.

With sufficient knowledge and an appropriate diagnostic apparatus (Autoboss, Pico Scope, Range, VCDS, AutoEnginuity,  ScanXLpro), code reader or scanner, plugged into the car's 16 pin diagnostic plug, mechanical minded persons can read these faults, print then or save them to an SD card or harddrive, send signals and communicate with the ECUs, read the measured values and interrogate the actuators. The DTC in memory however do not identify the part that has gone faulty but rather provides you  with a general idea to its area of origin. Often long before a DTC code is generated the fault may already have existed so when the you view the DTC it could show that the fault occurred twice of thrice or even six times before. The ECU software is designed to monitor the frequency of error and if it is an isolated occurrence the ECU clears the fault after a certain distance is traveled but that dependent on the severity of the fault. For arguement's sake lets say 300kms. If it happens once in 300kms it could automatically clears the fault but should it happen four times during the same distance a DTC will be registered, the car could go into limp mode since it may be unsafe to drive the car if it's a breaking or steering issue, or shut the engine off if the O2 sensor went faulty and can't regulate the smoke pollution, or disable starting if the knock sensor triggered the DTC as there may be no oil in sump which could amount to a very expensive engine repair. In the case of the latter, the oil light should have illuminated long before the knock sensor shuts the engine off. However I have encountered a problem with the wires that plug into the oil sensor that became brittle due to engine heat and  subsequently broke off. As a result the sender  sent the low oil condition but it never arrived at the the ECU hence did not turn-on the oil-low light. I only became aware of this when my EPC light went on due to the knock sensor. See picture in blog.   More ...

EPC DEMYSTIFIED

EPC DEMYSTIFIED IN THREE PARTS

PART 1

In a global village where defined lines between languages and nationalities, technologies and terminologies have become completely blurred, it is important to create terms of reference in discussions, so that we are all on the same page but pronunciation can at times offend the ear. To elaborate, some people say "tomarto" (tomato) some say "tomayto", some say micro computer and some say microprocessor, some say Electronic power control (EPC) some say Electronic Pedal control (EPC). But that's just semantics, the bottom line remains, that it establishes a common ground for people of different geographical spaces to discuss common topics.

In response to the hoards of queries I recently received and the abundance of confusion there is out there about EPC (Electronic Power Control); and in reply to the thousands of e-mails I received regarding EPC (Electronic Power Control) that I haven’t been able to reply to as yet nor will ever be able to, I decided to dedicate the next few episodes of my blog to explaining the EPC (Electronic Power Control) problem many VW drivers and VW owners are having with their cars as if they were two year olds. (Not that two year olds can relate the subject at hand).

I have explained EPC in previous blogs, namely EPC light revisited explained and EPC why-engine-light-comes-on, however, I am going to elaborate on the EPC (Electronic Power Control)  concept and demystify it for the benefit of all these people mentioned above and all those destined to encounter this problem at some time or the other. The question is not if you will encounter an EPC problem but rather when you going to encounter an EPC problem, its just a matter of time. Be that as it may, for the sake of simplicity, and by analogy, I'm going to compare the workings of the EPC (Electronic Power Control) in a car to that of a PC (personal Computer) which in my humble opinion will aid understanding.  So here goes....

Electronics as a whole has intrinsically influenced human life globally, especially since the advent of the silicon chip. Through the evolution of said silicon chip, Microprocessors have become so common place, that it finds itself in virtually every modern day technological advancement from computers to televisions, cell phones to cameras, medical equipment to the very cars we drive, to mention but a few. As a result virtually everyone out-there, has heard of, or are familiar with the terms microprocessor, microcomputer or just computer, and as such, it establishes a basis to discuss familiar concepts. Most people in the "Secular World" either owns a computer or uses computers and accordingly have some understanding of its hardware and its software, and how well these complement each other and seamlessly work together. I mentioned this purely in preparation to my assertion that  follows. However, all those non-technical and all-thumbs people and those  who say "you don't have to know how an engine works in order to drive a car", are totally excused.

EPC for Hands-on Dudes, Savvy Ladies and other pragmatic people.
Computers can roughly be subdivided into building blocks, each of which is responsible for a specific function or a collection of functions. As such a combination of these specific functions gives rise to the correct and proper functionality of the computer or computer based device. For instance, the computer hard drive functions as the storage unit that holds the operating system, application programs and user data. The DVD Rom, serial port, keyboard and mouse acts as input devices. Whereas and the speakers, printer & screen act as output devices, doubling-up as the interfaces of information interchange between man and machine (computer). The motherboard houses the CPU (central Processing Unit / Microprocessor chip) it ancillary / auxiliary timing chips, control and data buses, RAM and sub circuitry for  AGP, PCI, MR1, PCMCIA, USB, Ethernet, Fire wire, parallel connectivity, etc. When all these specific components play together nicely, we are guaranteed a fully functional computer and a happy computer user.

Likewise the car can be subdivided into building blocks each responsible for a specific function. In this instance, the engine is the source of propulsion which delivers it to the rest of the drive train. The instrument panel, the steering wheel, the transmission and the braking system constitute some of the input and output devices, also   doubling-up as the interfaces of information interchange between man and machine (car). The electrical system; the ECU (Motronic control unit), Control unit within the dash,  along with its auxiliary modules, oversees the overall timing, sensor, actuator, control and data bus, as well as block components like the Radio, air conditioner and central locking etc. Once again, when all these discrete components play nicely together, we have a perfectly functional car and a happy driver / owner. More...