Showing posts with label OBD2. Show all posts
Showing posts with label OBD2. Show all posts

Friday, January 4, 2019

Volkswagen

Volkswagen

Volkswagen cars are extremely popular. In fact, they are so  popular that Volkswagen as a brand is the favourite car of many South Africans, besides being the most popular car sold on the South African market. Volkswagen cars are also popular elsewhere and are sold in virtually every country throughout the world; but its popularity and its global acclaimed robustness doesn't make it indestructible. 

Volkswagen cars give problems, in fact they are more troublesome now, than they've ever been. The reason, the ODB-II system with its ever increasing number of ECUs.  This system has several features that means well, like controlling toxic emissions, like giving you the best fuel efficiency;  and is capable of detecting minor issues or glitches before they actually occur, among so many other beneficial features.

However, like every coin has two sides, and as there are always two side to every story, there is also a reaction to every action.   Meaning for every beneficial feature of OBD-II there is a detrimental feature to OBD-II. OBD-II is essentially a computer system with a host of additional computer modules remotely placed through the body of the car, some of which have an effect on the Engine ECU. 

These modules or sub-ECUs oversee various features, like an airbag controller module/ECU that supervises the airbag. This module is connected to crash sensors placed in strategic positions in the car, that triggers when a crash occurs and ensure that the airbag is inflated within the required time frame. Then there is also an immobilizer module/ECU that supervises the starting process ensuring the correct code from the key transponder chip corresponds with its randomly generated code. There is also an ABS Brakes module, a Gateway module, a Steering Assist module, an Instrument Module, a Central Convenience module, a Radio module, to mention but a few. All of which are potentially sources of problems.

If we only look at the Airbag and the Immobilizer modules/ECUs, both will impede driveability and the starting of the car, by influencing the Engine ECU. If the Engine ECU doesn't received the expected signal from either, it would refuse to start the engine. The Engine ECU is the heart of the ODD-II and normally sits in the engine compartment or inside the car under the dashboard. All three these modules/ECUs mentioned, sometimes also referred to as nodes, are in within a meter of on another but here's the downside. 

To get them to sing in harmony they are connected together by a wiring harness. This wiring harness plugs into each and every node in the car, and also share a common twisted-pair wire-connection  called a bus which is terminate at each of its ends with 120 Ω resistors. This bus can be either Controller Area Network (CAN) or  Local Interconnect Network (LIN) or even FlexRay. Each module also has a power supply and an earth connection. All of these wire connections are potentially sources of problems.

The average car can have anything between 5 and 100 modules/ECUs, some ECUs have as few as six connections and others as many as 80 or 94 or even more. Each of these physical connections are prone to corrosion, metal fatigue and physical flexing due to suspension vibration and is a source of future problems. Some ECU's earth connection is solely made through body contact and if it looses contact due to vibration or water ingress, it will undoubtedly cause an error or errors. 

These errors are stored in the ECU's non-volatile memory which can at times be quite cryptic. I can say that without doubt that every "automotive technician" has misinterpreted DTCs and replaced unnecessary components in the process. Even returned cars to the owners claiming that they solved the problem but didn't, they were just under the misapprehension that they did.

If any connection out of this glut of connections becomes intermittent for some reason or the other, it would be like trying to find a needle in a haystack and there are so many "automotive technician" that have never touched a needle nor even seen a haystack, let alone find a needle in a haystack. Be that as it may, one of the advantages of OBD-II is that it increases the likelihood of a DIY fix, providing the fixer is fairly dexterous and have some electronic and mechanical knowledge and have access to a diagnostic scanner.

A fairly common plug connection that goes intermittent, is the one that connects to the throttle body. It supplies the voltage to the stepper motor that controls the throttle butterfly valve. This plug also sends feedback to the ECU so that it knows how wide open or close the valve is. So many mechanics insist on stripping the throttle body due to a throttle body DTC and claim after cleaning it, the problem was solved. However a few days later the error would be back. A word of caution, Don't suspect replaceable parts especially if it has less that 100 000 km on its clock. Exhaust the possibility that it's a possible wiring harness problem before replacing expensive items because they can never be returned to the agents after its been installed.

Another intermittent connection it the 6 pin plug that interfaces with the accelerator pedal. This is a common source of the dreaded EPC problem. In many cases, a squirt of electro cleaner may solve this problem. That's to say until it's triggered by something else. It's worth while to check the voltage supply stability and ground impedance between the 6 pin plug and the ECU. Remembering that the pedal's earth connection is grounded inside the ECU and the ECU is grounded to the body or chassis and not the engine. In some cases, the ECU will function normally because its metal casing is not earthed.

Also, don't be tempted to earth the pedal earth directly to the body when there is a  significant resistance reading. Rather replace that portion of the wiring harness that may have gone high resistive. Offset ground connections and ground loops can cause voltage drops and magnetic impedance which are major causes of noise hum, and interference in computer systems (ECU). So don't alter the the existing ground connections because it could introduce issues you've never experienced before.

Saturday, July 16, 2016

VAG 405 SCAN TOOL

VAG405 SCAN TOOL

A week ago I  ordered a VAG405 scan tool from an online store. This scan tool is essentially a dedicated stand-alone OEM level diagnostic device for scanning Volkswagen, Audi, Skoda, Seat, VW Golf, VW GTI , VW Polo, VW Jetta, VW Beetle, VW Passat, VW Touareg, vehicles... etc. Restated, it's a scan tool specific to VAG vehicles manufactured since 1990 to the current day, yet it is quite unlike the Autel D900 diagnostic scan tool I evaluated in a previous blog which is not VAG specific but can scan several makes of vehicles.


As can be seen, it can scan Golf 3, Golf 4 Beetle, New Beetle, Passat.....

It also scans the Polo, Sharan, Lupo, Bora and the Transporter, etc...

However, when the scan tool arrived, I expected something much smaller, like perhaps the size of a Samsung S7, but to my surprise it was actually quite substantial, sporting a large easy to read backlit LCD with OBD/EOBD functionality. The box also included a nylon carry case, an OBD2 cable, a USB cable and a VAG405 user's manual.

Initially, I was intrigued by the general claims made by the advert and reiterated on  the actual box it which it was packaged. It stated that  the VAG405 scan tool reads most electronic controlled modules and erases Diagnostic Trouble Codes (DTCs) from the ECU's non-volatile memory triggered by the Engine, Transmission, ABS, Airbags, Climatic control (AC), Steering wheel, Immobilizer, Instrument cluster and Central electronics, etc. That it reads and clears generic trouble codes on VAG vehicles using either ISO 9141-2 ("CARB"), or ISO 1430 ("KWP-2000") and ISO-15765 ("CAN") protocols for the latest cars and can even resets the MIL light, airbag, ABS and a host of other  OBDII systems.


ISO 1941 Protocol
KWP2000 Protocol
CAN Bus Protocol
And that it can also resets oil service light and retrieve the ECU embedded VIN (Vehicle Information Number) as well as display I/M readiness. 

All of this just sounded too good to be true so I just had to get one. But after running tests I am sorry to say that I am not too impressed with it. Not because it is brick but that it is rather inclined towards cars built prior to y2k.  I found that the VAG405 timed-out and froze when scanning for trouble codes, while displaying "Please Wait" on its LCD screen. In order to reset it, I had to physically unplug the 16 pin DLC then reconnect, else I was going to wait forever.  I assume the "Please Wait" (timeout) is an incompatibility between the non-volitile memory used in my 2007 VW Polo 2.0L Highline and that used in VW prior to y2k. However, most of the other functions appear to be compatible.

I like the fact that it is powered from the car's battery via the DLC and therefore doesn't need batteries but a nice to have would have at least been an on-off switch fitted to the scan tool, to reset the scan tool when it freezes. The software is fairly simplistic and easy to use, though rather limited since it doesn't allow you to change module coding. I couldn't retrieve my car's embedded VIN and I don't think this VAG405 can't retrieve it from  any later model VAG vehicle. It is a very nifty scan tool and great value for money if you own an older VW vehicle or Audi but steer clear of it if your car is newer that year 2000. Perhaps this peculiarity is specific to my scan tool yet everything else seem to function as per claim in the advert and on the box.

Below is a series of photographs that I uploaded to demonstrate the functionality of this scan tool.



Engine control Module data
ABS control Module data
Airbag control Module data
Instrument Control Module data
Electronics Module Control data

Gateway Control Module data

Comfort Control Module data

Failed communication occurred several times but after unplugging DLC and
reinserting comms appeared to be much better.

The software is quite informative, guiding you to causes of comms errors.
Link Error! This happened when I scanned the Steering Control Module and the Radio Control Module, both of which was present and responded to the Autel D900 scan tool.






OBD readiness tests of the 8 monitors, 6 of which are feature in the above image and
2 are featured in the image below, all of which pass,




The first 6 Control Modules, A peculiarity I picked up is that the Airbags is listed before ABS which
isn't normal compared to other dedicated scan tools and computerized scan tool software.

Control Modules 16 -25 

Control modules 35 -56

I don't believe that there are no stored codes because I know there are airbag error codes stores which I determined using VCDS. Like I mentioned earlier, the VAG405 is more suited to vehicles manufactured prior to y2k.

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.

Wednesday, May 15, 2013

Volkswagen Electronics


VOLKSWAGEN ELECTRONICS

AUDI  MODULE CODING

Electronics has taken over the modern day car, a trend that started prior to 1994. Since then  motor vehicle electronics technology has taken on a completely different form. With the advent of OBD (On-Board Diagnostics) there has been strides to standardize automotive electronics in all vehicles with relative success. With the arrival OBD II automotive electronics standardization was close to uniform, however there were other derivatives, among which was EOBD (European OBD). Thereafter, CAN-Bus was introduced which is now the defacto standard for all cars built after 2008 internationally. All cars built from 2012 only sports CAN-Bus,  and are not backward compatible to older ODB II protocols, like KWP2000 for example. This move implies every auto technicians who financially invested in ODB II scanners will have to get the latest equipment in order to scan the latest cars. Just look at the Audi Q7 with its 50+ electronic modules all of which are CAN-Bus only. 
Audi Q7 has more than 50 Electronic Modules.

The hexadecimal list of Electronic Modules below are just an idea of what can be expected in current and future motor vehicles many of them having as many as 24 different module versions, many modules are incompatible with the various models of Audi, VW, Skoda and SEAT, each with its own features and coding.

02: Auto Trans
05: Acc/Start Authorization
07: Control Head
08: HVAC
0E: Media Player 1
0F: Digital Radio
11: Engine II
13: Auto Dist. Regulation
15: Airbags
16: Steering Wheel
18: Aux. Heater  
19: CAN Gateway
1E: Media Player 2  
20: High beam assist
22: All Wheel Drive
28: Heating / Air Conditioning (Rear)
2E: Media Player 3
34: Level Control
36: Driver's Seat
3C: Lane Change
3D: Special Function
42: Door Elect, Driver
47: Sound System
4F: Centr. Electr. II
52: Door Elect, Pass
55: Headlight Range
56: Radio
57: TV Tuner
5C: Lane Maintenance
61: Battery Regul.
62: Door, Left Rear
65: Tire Pressure Monitor
67: Voice Control
6C: Back-Up Camera
6D: Trunk Electronics
72: Door, Right Rear
77: Telephone


AUDI : - SOME ENGINE CONTROL UNITS AND CODINGS




Engine:

Controller:     8E0 909 518 A,
Coding:         0011581 or 0016711

Controller:    8E0 909 518 AA

Coding:         0011501

Controller:    8E0 909 518 AC
Coding:        0004501 / 0004581

Controller:     8E0 909 518 AF
Coding:         0016701 / 0016751 / 0016581

Controller:     8E0 909 518 AK
Coding:         0016711 /  0016751 /  0016501

Controller:     8E0 909 518 AL
Coding:         0011584

Controller:     8E0 909 518 AS
Coding:         0011511

Controller:    8E0 909 518 AQ  
Coding:        0011501

Controller:     8E0 909 518 F
Coding:         0016701 or 0016751

Controller:     8E0 909 518 G
Coding:         0016581


 AUDI Automatic Transmission 
codings will be covered in Future Blogs.

VIN Number identification 
will also be covered in Future Blogs.

Volkswagen’s new modular architecture 
will also be covered in Future Blogs.


Thursday, February 7, 2013

VAG


VW DIY

In the not so distant pass, whenever something went wrong in your VW, Polo, Jetta, Passat,  AudiSeat or Skoda,  you could do one of two things. Either  take it to a VW specialist to have it checked out or you could fix it yourself, if you are a hands-on, DIY kind of person. Nowadays the latter option has faded away into obscurity. With the stream of problems VAG cars are having, many of us are in the dark regarding repairs. We make educated guesses, replace parts by substitution, often costing huge amounts of money for repairs and the fault still persists. Below I have out-lined some of the problems I have encountered and with any luck shed some light on the problems you've been having with your VAG car. But before I go any further you may be itching to ask "What is a VAG car?"

Well, VAG stands for Volkswagen-Audi GMBH in Germany, also refers to Volkswagen Aktiengesellschaft or Volkswagen AG for short and Volkswagen-Audi Gelelschaft (Geleslschaft means Association). In essence, it's the same, exact and identical  group. And any car manufactured or sold by them is referred to as a VAG car. Amongst these are, VW, PoloJetta, Passat, Audi, Skoda, Touran, Tauareg, Beetle, Tiguan, Golf, PorscheAmrok,  RabbitBentley, BugattiBora, Phaeton, Vento, Kombi, Transporter,  Lupo and the  Lamborghini, each one with a different engine with varying capacities with obscure three letter abbreviations like, BBX, AAF, AEX and APE amongst many others. However many of them have the same or similar Electronics Bosch Motronic system hardware with software ranging from ME 5.x to ME 7.x, with several support modules in common, networked to the OBD II / OBD2 (On-Board Diagnostic System ver. 2) or Can-Bus (Controller Area Network) standard.

The VW Polo 2007 with new Bluemotion technology can switch its engine off
when it comes to a halt, yet plagued by the legacy VW EPC light problem.

The idea behind this is so that only the  Volkswagen dealership technician are supposed to do the servicing and perform repairs to your car. The VW car manuals specifically discourages anyone other than qualified or trained mechanics /auto-electricians and technicians or mechanicians to perform servicing, especially changing codes and performing readiness testUnder the OBD II and Can-Bus standard, an ECU (Engine Control unit) interfaces with various other modules fitted in the car and controls and manages all sub-circuits. For example, Central Electronics Module, ABS module, Temperature Control Module, Speed-o-cruise Module, etc... When one of these modules detects a fault with one of its components, it registers a error in the non-volatile memory. Lets say you have a front wiper motor problem and it just wont work, but the fuses are OK. Even if you suspect the wiper motor as faulty and it actually is faulty and you replace it, the new wiper motor still wont work after its been replaced and switched on. You first have to clear the error or errors  from non-volatile memory with a diagnostic tool. Then and only then will it work.  

I've had the same results with my power steering which just wouldn't work after some work was done to my car and in the process the Power Steering Motor was disconnected. When it was reconnected the power steering was very stiff and difficult to steer. After going through the entire process of checking and back-tracking it still didn't work. Eventually, when the diagnostic tester was plugged in, two errors codes showed up. The first indicating that the +30V supply had dropped to an unreliable level and the second a power steering error. The first was because the battery was disconnected and the second was because the power steering plug was disconnected. After erasing the two error codes from the non-volatile memory, the power steering work perfectly normal.

I can assuredly say that I am not alone or rather that my car trouble is not unique, neither am I the only VW owner having car trouble (see previous blogs).  It appears that my 2007 Polo Classic Highline shares most of the problems listed below with my fellow VW owners. There are probably hundreds if not thousands of other  VAG car owners experiencing the same issues with their cars as I am experiencing with mine. Here are just a few of the problems that my fellow VW owners shared with me :-

"VW polo dashboard brake light stays on" / "EPC instrument fault indication light is on" / "VW polo warning lights on dashboard" / "VW  polo classic is showing epc light, starting and dying" / "polo dashboard controls" /  "VW  polo warning lights off power steering" / "warning light on dashboard" / 2007 volkswagen polo problems" / "audi electronic power control indicator" / "won't rev" / "VW Polo EPC Warning Light" / "golf mk4 dashboard warning lights" / "epc instrument fault indication" / "VW  door key problem" / "VW  polo accelerator position sensor (g79)" VW throttle body sensors"

NB! Fellow VW drivers found this site to be helpful and was interested in checking out the following sites as well.

expowpphotojanicontroversy365nerdytoyslovelifelovehealthsightsofcapetownsowpboxelectroniquesblogspot-atphoto-magixgodssitesglycomixarth-ritisforex-bidfoodsofthecapelanguagesbarrier, pimpyocare-gimos.

Should you find this blog informative or even help full in the very least, please recommend it to others and click on the g+ tag below. Thanks.