Showing posts with label Diagnostics. Show all posts
Showing posts with label Diagnostics. Show all posts

Friday, March 4, 2016

AUTEL D900 SCAN TOOL

AUTEL D900 SCAN TOOL

The modern day car in its current incarnation has increasingly become more and more electrotechnical than mechanical and technological advancements are constantly on the incline.  It is therefore  quite appropriate to say that vehicle owners need to become electromechanical savvy. In my opinion, the way forward is to invest in a scan tool for your particular make and model car. Since most people are familiar with Cell Phones, Decoders, Set Top Boxes, PVR, DVR and Televisions with various menus, or computers, access points and routers  with various wizards, navigating a scan tool would be relatively easy. A scan tool is an indispensable device for modern car diagnostics and is a technological marvel that's going to save you time and money, but only if you are willing to embrace the technology. 



In a previous blog I discussed VCDS which I think is a really fantastic piece of software with its hardware interface combination specific to VAG vehicles. The amount of Onboard information that is accessible with VCDS is astounding and it is literally beter than the factory  VAS Scan Tool used by VW /AUDI /SKODA / SEAT agents. In fact, in some cases VCDS  will even retrieve more faults than the VAS tools.  Be that as it may, as fantastic as VCDS is, it has major shortcomings for vehicle owners in general. Since VCDS is VAG specific, all other vehicle owners are at a loss to its technical capabilities and would have to look at other scan tools from  companies like  Auto Boss, Launch X431, Autel Maxidas DS708, Pro-Link iQ,  Mentor Touch ET6500, OTC Pegisys, Craftsman - 20899, G-Scan Oceania, Bosch 3824, etc, who produce commercial multivehicle scan tools. These companies cater for the automotive service industry since their scan tools are quite pricey and far beyond the budget of the average car owner.  If VCDS was multivehicle, it would be as good if not better than most commercial scan tools. However, since this is not the case,  Autel has come to their aid of the average car owner. Autel has a low cost handheld scan tool that is multivehicle compatible that supports the following list of vehicles.

Acura, Audi, BMW, Buick, Cadillac, Chevrolet, Chrysler, Daewoo, Dodge, Eagle, Ford, Geo, GMC, Honda, Hummer, Hyundai, Infiniti, Isuzu, Jaguar, Jeep, Kia, Land Rover, Lexus, Lincoln, Mazda, Mercedes Benz, Mercury, Mitsubishi, Nissan, Oldsmobile, Pontiac, Porsche, Plymouth, Saab, Saturn, Scion, Suzuki, Toyota, Volkswagen, Volvo.  

I acquired the 2015 version because of its versatility because it supports several models of each of the above mentioned vehicles. I wanted it to diagnose my Renault but discovered that it unfortunately does't support Renault and even more surprisingly it doesn't support my  VW Polo  2.0L Highline (9N) either but it does support the the following list of VAG vehicles.

Audi A3
Audi A4
Audi A6
Audi A8
Audi A8L
Audi All road
Audi Cabriolet
Audi S4
Audi S6
Audi S8
Audi TT

Volkswagen Beetle
Volkswagen Bora
Volkswagen Eurovan L5
Volkswagen Eurovan VR6
Volkswagen Golf A3
Volkswagen Golf A4
Volkswagen GTI
Volkswagen Jetta A3
Volkswagen Jetta A4
Volkswagen Passat
Volkswagen Touareg

I don't know if the previous years version (Autel D900 2012) supports older vehicles like 2002-2010, but am of the opinion that all newer scan tools are backward compatible though I may be wrong. Anyway, the Autel scan tool is really cool, it comes with a mini CD containing a pdf file of all supported vehicles. I would have thought they would include a list of generic DTCs for Chassis / Powertrain (P-codes), Body (B-codes)  and Network (U-codes) for easy of identification. What this implies is that you will have to either find these lists online, save them as pdfs or print them or access the internet resources to identify the codes every time you car throws you a DTC.

CONTINUED

Wednesday, July 22, 2015

EXCESSIVE COMMS ERRORS

EXCESSIVE COMMS ERRORS

Looking at the partial scans from several different vehicle platforms listed below, it is quite obvious to see that they all suffer from the same ailment commonly known as--Excessive Comm Errors--from Audi to SEAT, from VW to SKODA. Many VAG car owners have attached their own prefixes to it, like "vag com excessive comm errors", "vcds excessive comm errors", " note excessive comm errors", "vcds lite excessive comm errors", "auto hvac excessive comm errors", "address 08 excessive comm errors", but they all mean the same thing. It says that the scan tool could not communicate with said module because of some obstacle . Perhaps its conflicting with an after market Radio installation on Address 56 or  a combination of VCDS software/protocol/cable. The reason could also be that some other module on the network had been incorrectly configured (module coding) causing the scan tool to struggle to identify said module and after several times attempts fail (timeout) and presents a "Note: Excessive Comm Errors" and perhaps flag a 01044- control module incorrectly coded DTC as well.  However this isn't always the case, because it could also be caused by a setting on the scan tool software--flow control, start and stop bits, etc. The HVAC-address-08, ABS Address-03, Airbag Address-5 etc.. speak protocol KWP-1281 or protocol KWP-2000 and if the incorrect protocol has been selected, the  "Note: Excessive Comm Errors" does pops up. Some HVAC module will also generate a U0324  DTC  meaning that the scanner software is incompatible with the HVAC Control Module or the module concerned. If VCDS doesn't work, try the older VW Tool software or Commander 5,  which I have found has better HVAC and engine fan control settings than VCDS with a VAG-K-CAN cable or KKL-VAGCOM cable. I think the most common reason for excessive comm errors is using the incorrect interface cable because a KII-USB  (K2-USB) cable will not work on cars manufactured after 2005 and a Micro-CAN cable will only work on cars built prior to 1996. So it you have a later vehicle, get the right cable or invest in a Auto Boss V30 or a Launch X31 scan tool because they tend not give  Excessive Comm Errors that the VCDS software/protocol/cable combination is so notorious for. 


Address 01: Engine ---------------------
Chassis Type: 6K - Seat Ibiza / Cordoba
Controller: 6K0 906 032 AC
Component: ME7.5.10 4192
Coding: 00001
Shop #: WSC 06402
Note: Excessive Comm Errors

Address 01: Engine ---------------------
Chassis Type: 6L - Seat Ibiza/Cordoba
Note: Excessive Comm Errors

Address 01: Engine
Chassis Type: 70 (7D - VW Transporter)
Part No: 022 906 032 AF
Component: MOTRONIC ME7.1 G 0003
Coding: 00003
Shop #: WSC 27441
Note: Excessive Comm Errors


Address 02: Auto Trans
Chassis Type: 70 (7D - VW Transporter)
Part No: 01P 927 733 CG
Component: AG4 Getriebe 01P 4893
Coding: 00000
Shop #: WSC 00000
Note: Excessive Comm Errors

Address 03 ---------------------
Controller: 6Q0 907 379 L
Component: FRONT ABS MK60 0101
Coding: 0001097
Shop #: WSC 31414
Note: Excessive Comm Errors

Address 03: ABS Brakes
Chassis Type: 70 (7D - VW Transporter)
Part No: 7D0 614 111 B
Component: ABS/EDS 5.3 D00
Shop #: BB 24258
Note: Excessive Comm Errors

Address 08 ---------------------
Chassis Type: 1M - Seat Leon/Toledo
Controller: 1M0 820 043 D
Note: Excessive Comm Errors
Skipping Address 15-Airbags

Address 08 --------------------
Chassis Type: 4B - Audi A6 C5
Controller: 4B0 820 043 P
Coding: 00063
Shop #: WSC 02325
Note: Excessive Comm Errors

Address 08 --------------------
Chassis Type: 1M - Seat Leon/Toledo
Controller: 1M0 820 043 E
Component: 1M-CLIMATRON
Coding: 00043
Shop #: WSC 06402
Note: Excessive Comm Errors

Address 08: Auto HVAC
Chassis Type: 8D - Audi A4 B5
Controller: 8L0 820 043 D
Component: A4 KLIMAVOLLAUTOMAT_D75
Coding: 04144
Shop #: WSC 06325
Note: Excessive Comm Errors

Address 08 --------------------
Chassis Type: 1M - Seat Leon/Toledo
Controller: 1M0 820 043 D
Component: 1M-CLIMATRONIC X0605
Coding: 00043
Shop #: WSC 06441
Note: Excessive Comm Errors

Address 09: Cent. Elect. -----------
Chassis Type: 9N - VW Polo
Part No: 6Q1 937 049 D
Component: 0000 BN-SG. 1S34
Coding: 00012
Shop #: WSC 06402
Note: Excessive Comm Errors

Address 09: Cent. Elect.  -----------
Part No: 6Q1 937 049 D
Component: 00BP BN-SG. 1S34
Coding: 09358
Shop #: WSC 31414
Note: Excessive Comm Errors

Address 15: Airbags ------------------
Chassis Type: 6Y - Skoda Fabia I
Controller:
Note: Excessive Comm Errors

Address 15: Airbags
Chassis Type: 70 (7D - VW Transporter)
Part No: 1J0 909 603 BM
Component: AIRBAG VW3 - V04
Coding: 16973
Shop #: WSC 02743

Note: Excessive Comm Errors

Address 17: Instruments  -------------
Part No: 6L0 920 801 A
Component: KOMBI+WEGFAHRSP VDO V13
Coding: 00145
Shop #: WSC 00000
Note: Excessive Comm Errors

Address 17: Instruments ---------------
Chassis Type: 6L - Seat Ibiza/Cordoba
Part No: 6L0 920 801 A
Component: KOMBI+WEGFAHRSP VDO V13
Coding: 00145
Shop #: WSC 00000
Note: Excessive Comm Errors

Address 17: Instruments
Chassis Type: 70 (7D - VW Transporter)
Part No: 7D0 920 902 T
Component: T4-KOMBIINSTR. VDO V01
Coding: 03235
Shop #: WSC 02743
Note: Excessive Comm Errors

Address 19: CAN Gateway ---------------
Chassis Type: 6L - Seat Ibiza/Cordoba
Note: Excessive Comm Errors

Address 19: CAN Gateway
Chassis Type: 70 (7D - VW Transporter)
Part No: 6N0 909 901
Component: Gateway K<->CAN 0001
Coding: 00001
Shop #: WSC 02743
Note: Excessive Comm Errors

Address 25: Immobilizer  --------------
Chassis Type: 9N - VW Polo
Note: Excessive Comm Errors

Address 25: Immobilizer
Chassis Type: 70 (7D - VW Transporter)
Part No: 6X0 953 257
Component: IMMO 0008
Coding: 00001
Shop #: WSC 20309
Note: Excessive Comm Errors

Address 35: Centr. Locks
Chassis Type: 70 (7D - VW Transporter)
Part No: 7D0 959 800 C
Component: Funksteuergerát 0001
Coding: 00001
Shop #: WSC 02743
Note: Excessive Comm Errors

Address 44: Steering Assist ------------
Chassis Type: 6Y - Skoda Fabia I
VCID: 55AA04A28569
Note: Excessive Comm Errors

Address 56: Radio ---------------------
Chassis Type: 17 - VW Golf Citi
Controller: 17S 035 186
Note: Excessive Comm Errors

Address 7E: Ctrl Head Dash -------------
Chassis Type Audi TT
Protocol: KWP2000
Controller:
Note: Excessive Comm Errors


Tuesday, October 21, 2014

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


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...


Friday, May 10, 2013

VW ABS CODING



VOLKSWAGEN ABS DIAGNOSTICS

Using a code reader or  diagnostic tester to view your VW Polo ECU data is quite a treat and is also really cool. A view of the data just exudes the growth of motor vehicle technology in general and it is quite humbling if you are electronically minded and quite intimidating if you are mechanically minded.  However there is often the temptation to change a number or something, just to see what happens to your Volkswagen. If you are one of those people who just did that, I bet you have a wistful regret, wishing that you never did so in the first place because you got yourself a "01044 control module incorrectly coded error." Or perhaps you  swapped a 1996 VR6 engine into a 2007 MkV GTI chassis and got a "01044 control module incorrectly coded error." Or you had your car serviced and the ABS and ESP light stays on in the instrument panel and showing up as a "01044 control module incorrectly coded error."  Or you cleared that nagging airbag light on your VW Beetle, only to get a "01044 control module incorrectly coded error."

Control modules codings are normally NOT interchangeable since virtually every model among the numerous versions of  VW's  each have a different ABS/ESP modulePower Assisted Steerin Module, Climate control ModuleInstrument Module, Immobilizer Module and Engine Control Module and so many other modules. Taking this into consideration,  it is more than  obvious that one should NEVER copy coding from a different model VW, AUDI, SKODA or SEAT and paste it into your own VolkswagenAUDI, SKODA or SEAT, unless you write down your original modules original coding so that you can revert back to it later, should things appear to go pear shaped. 

However if the two VW, AUDI, SKODA, or SEAT are the same in every respect, then  their module codings will be identical and therefore perfectly fine to use. Be particular about the module suffix since different suffixes signify different software versions which may not be compatible to your VAG car. Virtually each module that appears identical but has different letter suffixes will invariable have a different coding. So the rule is same car, same module, same module number, same module suffice, same coding. Disregarding this could incapacitate your car and cost you a huge amount of money.

Every Control module coding is stored as an onboard binary number, which in essence is the binary sum of the features for that specific module. Whereas the ECU also stores an onboard binary number which is the binary sum of all the Control Modules 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 notorius 01044 control module incorrectly coded Checksum verification was adopted by BOSCH Motronic ECUs to validate its EPROM's stored data. Having said that, 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

Below, is a list of VW ABS controllers and their respective coding which vary from  'ABS FRONT MK60 0101' to  'ABS 8.0 front H03 0002' to 'ABS 8.0 front H05 0002' to 'ABS 5.7 FRONT V20' to 'ABS 5.7 FRONT V30 ' to 'ABS/ASR 5.7 FRONT V20' to 'ABS 5.7 FRONT V00' to 'ESP 8.0 front H03 0001' to 'MABS 8.0 front  H04 0002' to 'ESP 8.0 front H03 0001' to 'ABS 8.0 front H03 0002' to mention but a few. Several VW, AUDI, SKODA and SEAT owners and mechanics are constantly searching the Internet for ABS module coding and hopefully this information may help them to get their Volkswagens, Skodas, Seats,  Audis and other VAG cars up and running once again.

VW POLO 6Q0 907 379 AC ABS Pump

VW Polo 9N
Address 03: ABS Brakes
Controller: 6Q0 907 379 AC
Component: ABS 8.0 front H03 0002
Coding: 0000145

ALTERNATIVE ABS MODULE CODING
NB! These are the codings I currently have but are certainly not the only ones use by Volkswagen, SEAT, Skoda and Audi. As I get them I will update this list.

6Q0 907 379    - Coding:  00036 or 00044
6Q0 907 379 AA - Coding: 0000005 or 0000008
6Q0 907 379 AB - Coding: 0000005 or 0000008
6Q0 907 379 AC - Coding: 0000145 or 0000142

6Q0 907 379 AF - Coding: 0002061 or 0002079 or 0002082 or 0002085 or 0002103 or 0002115 or 0002118 or 0002122 or 0002136 or 0002145 or 0002175 or 0002181 or 0002190 or 0002193 or 0002199 or 0002202
As can be seen above, AF suffix has the whole gamut of codings and each should be tried before throwing in the towel.

6Q0 907 379 AG - Coding: 0002202 or 0002229 or 0002238
6Q0 907 379 AH - Coding: 0000299 or 0000284
6Q0 907 379 AQ - Coding: 0002356
6Q0 907 379 AS - Coding: 0002347 or 0002368 or 0002368 or 0002491
6Q0 907 379 AT - Coding: 0000269
6Q0 907 379 BC - Coding: 0002136 or 0002098
6Q0 907 379 C  - Coding: 00044
6Q0 907 379 D  - Coding: 00124 or 00188
6Q0 907 379 E  - Coding: 0001097
6Q0 907 379 G  - Coding: 00044 or 00045
6Q0 907 379 H  - Coding: 00188
6Q0 907 379 L  - Coding: 0001097
6Q0 907 379 M  - Coding: 0000000
6Q0 907 379 R  - Coding: 0000008
6Q0 907 379 T  - Coding: 0000281 or 0000296 or 0000299

Make some quick money
Eat as much as you like at Alfonso's Wedding
A Classic Wedding Cake 

Friday, May 3, 2013

VW POLO DIAGNOSTICS




After I completed all the minor repairs (as can be seen in my previous blog) to my VW Polo 2.0L Highline she finally went for her 90 000 kms service. But hardly did I get her back when I heard a very soft and occasional "ting, ting, ting" coming from the right front wheel. The sound was difficult to identify at first, not even the auto service technicians at the center could hear it. I found that the wheel had a few millimeters of sideways play when I jacked-up the VW Polo. This prompted me to check all the nuts & bolts and I found the nut on the tie-rod end to be loose. After tightening it, the sideways play was cured. However, it didn't cure the soft, occasional and irritating  "ting, ting, ting."  Twice thereafter I had the wheel off but found nothing out of the ordinary. Anyway I suspect its the right right hand side CV joint that is starting to go but it kind seems strange that a CV joint should give up the ghost round about 90 000 kms, its just way too early.

VW Amarok left hand drive double cab in snow white.
The tough smart VW Amarok Double Cab.
The 2.0L VW Polo right hand side drive shaft is very different from that of its siblings, it is much thicker and the spline that the hub slides onto, is much coarser that any other VW Polo. This drive shaft is an agents only item and its not cheap and to replace it by substitution to get rid of the occasional "ting" is a bit extravagant. My VW Polo is a very different beast from the rest of the VW Polo range and finding information for it is quite difficult. It seems every service centre has all the other manuals except that of the VW Polo Classic 2.0L highline.

VW DIAGNOSTICS
For starters it has the following odd ball ECU controlling an odd ball BBX engine rated at 84KW and 116HP.
Address 01:   Engine
Controller ID 06A 906 032 PB 
Sotware Coding Coding 00071

ENGINE TYPES:
Essentially Bxx implies VW Polo engines manufactured after 2005, whereas Axx implies engines manufactured prior to 2005 or rather between 2001 and 2005. The following  engines range from 1.2L to 1.4L to 1.6L to 1.8L to 1.9L and 2.0L and include diesel engines. BMD, BBM, BME, BZG, BKY, BUD, BLM,  BBZ, BNM, BWB, BMS, BNV, BAH, BTS, BJX,  BBU, BMT, BLT, BBX,

The following  list of Axx engines also range from 1.2L to 1.4L to 1.6L to 1.8L and 1.9L and include diesel engines, AWY, AZQ, AUA, AXU, AUB, AMF, ASY, ATD, AXR, ASZ. However the Axx, Bxx rule isn't hard and fast or cast on stone. There are VW Polo vehicles manufactured prior to 2005 with BMD, BME, BBY, BKY, BBZ, BAY,BLT engines fitted and there are some manufactured after 2005, fitted with AXU,ATD, ASY, AXR, ASZ engines.

Concept cars by Volkswagen
My 2.0L Volkswagen Polo  ECU's isn't only used in 2.0L Golf,  Jetta and VW Polo but also in 1.8T like the Seat Ibiza Cupra, Seat Leon, and the Seat Toledo Cupra with ME7.5.10 software.

2.0L GOLF / JETTA - ECU or Engine Management System
AWD 06A 906 032 CL 2001
AWD 06A 906 032 CM 2001

AZG 06A 906 032 DS 2001 (manual)
AWW 06A 906 032 DL 2001 (manual)
AZG 06A 906 032 FN 2002 (manual)
AVH 06A 906 032 BP 2001 (manual)
AVH 06A 906 032 FQ 2002 (manual)
AVH 06A 906 032 MC 2003 (manual)
BEV 06A 906 032 MT 2004 (manual)
BBW 06A 906 032 PE 2004 (manual)
AWP 06A 906 032 HS 2002 (manual) 
AWP 06A 906 032 LP 2002 (manual) 
AWP 06A 906 032 NK 2002 (manual) 
AWP 06A 906 032 SK 2002 (manual) 
AWP 06A 906 032 RN (6spd manual)
AWP 06A 906 032 SM (6spd manual)
AZL 06A 906 032 NH
AZL 06A 906 032 MN
AZL 06A 906 032 NJ

AZG 06A 906 032 DT 2001 (automatic)
AVH 06A 906 032 BQ 2001 (automatic)
AWW 06A 906 032 DM  2001 (automatic)
AWW 06A 906 032 GH 2001 (automatic)
AVH 06A 906 032 FR 2002 (automatic)
AZG 06A 906 032 FP 2002 (automatic)
AVH 06A 906 032 MD 2003 (automatic)
BEV 06A 906 032 NA 2004 (automatic)
BBW 06A 906 032 PD 2004 (automatic)
AWP 06A 906 032 LQ (5spd automatic)
AWP 06A 906 032 NL (5spd automatic)
AWP 06A 906 032 SL (5spd automatic)

VW DIAGNOSTICS CONT.
My 2007 VW Polo Classic 2.0L Highline is an 9N4 with a JHF 5 speed odd ball manual transmission with odd ball gear ratios and also has a obscure Immobilizer module (6Q0 920 825 C) which doubles up as the Instruments Module. This is easily visible because of the software coding. There are several dozen of other Instrument Modules none of which are compatible to the 2007 VW Polo Classic 2.0L Highline.

Address 25:             Immobilizer  
Controller ID         6Q0 920 825 C
Component         IMMOBILIZER VDO V06
Sotware Coding 00141

Address 17:              Instruments 
Controller ID            6Q0 920 825 C
Component              KOMBIINSTRUMENT VDO V06 
Software Coding 00141

VW DIAGNOSTICS CONT.
The following VW 9N and 6N3 Instrument controllers have various coding, which is subject to other on-board equipment. The  software versions in their 93c86 EEPROM  range from V2 to V17 and appears incompatible to 6Q0 920 825 C. As can be seen below, only the letter suffix changes but the software is somewhat different.

Controller: 6Q0 920 825 E / Coding: 01144  =   VW Polo 9N1  = software VDO V06
Controller: 6Q0 920 825 F / Coding: 01132  =   VW Polo 9N = software VDO V05
Controller: 6Q0 920 825 G / Coding: 01132  =   VW Polo 9N = software  VDO V03 
Controller: 6Q0 920 825 J / Coding: 01142   =   VW Polo 9N3  = software VDO V06
Controller: 6Q0 920 825 H / Coding: 01141  =   VW Polo 9N1  = software VDO V06
Controller: 6Q0 920 825 K / Coding: 01148  =   VW Polo 9N = software VDO V05


TRANSMISSION TYPES:
The following  list of  5 speed manual transmissions are fitted in the  1.8T Mk4 Golf, 1.8T Beetle, 2.0L Beetle, 1.8T Golf, 1.8T Jetta IV, Jetta IV 2.0L, Golf IV 2.0L,  Jetta 1.8L, Jetta 1.9L, Jetta  2.0L, 2.0L Golf VR6, non of which has the odd ball JHF transmission used in the 2007 VW Polo Classic 2.0L Highline.
CDN, DZC, DZQ, EBD, EBJ, EBP, EBQ,  EGQ, EGR, EHA, EHC,   EGT,  EKG, EKH, EMS, EMT, ENJ, EZK, FBY, FBV, FBW, FCF,  EGF, EWW,  EUH, GQQ,  JCR, JDM, JDQ.

If you have a VW Polo Classic 2.0L Highline, you may post your VW Diagnostics report below.  


Trade Forex and make enough cash
to buy a Volkswagen
Beautiful Women in wedding Gowns.