Volkswagen Eos Forum banner
1 - 18 of 18 Posts

·
Registered
Joined
·
124 Posts
Discussion Starter · #1 ·
I wanting to get a cheap scanner for my Eos. Anyone have any experience with the Xtool Vag401, Nexas V007 OBD2 or Ancel VD500 scanner? They claim to read some VAG fault codes.
 

·
Administrator
Joined
·
2,565 Posts
Let cost be your guide - a cheap [i.e. low cost] scanner will not have the capabilities and accuracy of a proper VW compatible professional scanner.

What do you want?

A scanner that just reads codes but cannot rectify any issues?

A scanner that is VW-compatible that can access codes, read them and allow recoding and instigate action where appropriate to test the vehicle management systems.

Suffice to say one will cost significantly more than the other however the old saying "first cost is not end cost" will always apply.

Simply put, a cheap generic scanner is wasted money, a VW-compatible full-featured scanner will pay for itself many times over.
 

·
Registered
Joined
·
124 Posts
Discussion Starter · #3 ·
I understand that. The above scanners say they read VAG codes. I was just trying to find out if anyone had any experience with any of them. Are these scanners any better than the $15 special on Amazon? What are their limitations?
 

·
Administrator
Joined
·
2,565 Posts
I understand that. The above scanners say they read VAG codes. I was just trying to find out if anyone had any experience with any of them. Are these scanners any better than the $15 special on Amazon? What are their limitations?

Exactly what I said above - you get what you pay for. If you do a search of this forum, you will find numerous references to problems where the critical VW codes and data were not available and/or could not be reset with a basic scanner

What is the point of reading codes if you cannot safely and effectively remedy the problems arising from the scan results?

The professional scanners have dedicated user forums which provide substantial assistance in understanding and rectifying fault codes.
 

·
Registered
Joined
·
1,381 Posts
Any of those will do more than a $15 Amazon special, which (I guess - unless you share the link and I can see otherwise) won't read VAG codes and won't do any VAG live data or similar. I don't have any direct experience with the tools you link to, but I do have something similar, and all such tools seem to be based on more or less the same Chinese electronics and software.

However, you would be much better off getting an OBDeleven dongle which works with your smartphone (if you have an Android phone, you can get the cheap first-generation white dongle; if you have an iPhone you need the expensive second-generation black dongle).

If you choose to get one of the tools you mention, it may be harder for you to get help on forums like this one and you may be missing some useful diagnostic capabilities found in OBDeleven or VCDS. However, they can be a good start - they were the way I got into VW diagnostics - and if you find one for considerably less money than the OBDeleven dongle you need, they are a good introduction to the world of VW diagnostics. Just be aware that you may need to invest more money later. :)

There's also a link in my signature to a Diagnostics 101 guide, if you're interested in knowing more before buying.
 

·
Registered
Joined
·
124 Posts
Discussion Starter · #6 ·
This car is actually my 3rd vehicle and is only used a few hundred miles a year. It is 2011 and has 104K miles and has been throwing the CEL about every 4-500 miles. None of the CEL codes seem to be related, the last being the intake manifold (which was replaced by VW under extended warranty). I feel with all the extended warranties by VW due to defective parts, I am hesitant about taking it anywhere but the dealer. I do not have the time or space to do repairs myself and I was hoping to read the CEL to figure out if I am going to the dealer or the neighborhood mechanic. Maybe I just take it back to the dealer (400 miles after the intake replacement) and have them do the diagnostic for $90.
 

·
Registered
Joined
·
1,381 Posts
One of the tools you mentioned will do that job for you (and should also show you live data so you can investigate a bit further if you want). I would suggest it is worth having something that can read VW fault codes in your toolbox - even if you do decide to take it to the dealer.
 

·
Registered
Joined
·
371 Posts
There is a wide following of VW and other VAG products, and the consensus is OBDEleven is pretty much the best for price/performance.

As you've found out, engine codes can be cryptic or misleading (or even, simply nothing logged when there is a problem) so really they are a first step in a proper diagnostic process. I imagine even the most basic garage would have the ability to read codes, and might even be good (or better than the dealer) at actually diagnosing the root cause of a problem properly.
 

·
Registered
Joined
·
7 Posts
I wanting to get a cheap scanner for my Eos. Anyone have any experience with the Xtool Vag401, Nexas V007 OBD2 or Ancel VD500 scanner? They claim to read some VAG fault codes.
I have a VCDS and am very glad I got it after reading many postings of money wasted on scanners that didn't do the job. Worth every penny. Excellent user manual and customer service. Keep in mind that two dealer diagnostic tests cost almost the same as this scanner.
 

·
Registered
Joined
·
8,486 Posts
Buying a VW compatible diagnostics tool is a good idea. But don't expect it to fix faults. Like any test equipment it is a 'helper' and the human brain (or artificial intelligence) is still required to learn what it does, what it tells you and how best to choose steps to solving a problem. Information coming back from diagnostics can be like a wooley cloud or Google results from the internet. Knowledge and experience may still be needed to get a solution.

I've used VCDS for years, but as long as it's V.W compatible other tools can be just as good once you learn how your Efi engine and roof work to relate to diagnostics results.

Here's an easy step to find out if your cheap Chinese tool will help you with an EOS roof fault: Connect the tool and check it scans and shows no faults when the ignition is on. Now open the roof about half way until the side flaps open. Carefully and quickly reach inside the 'fish tank) and disconnect the connector at the bottom (one side is easier). This is the flap sensor connector. Check your scanner. Unless it tells you you have a roof sensor fault on the correct side, you have wasted your money.
 

·
Registered
Joined
·
53 Posts
Ok, so my 2007 EOS 2.0T is so messed up and thinks it's a 4-door, etc....so, I want to buy a OBD scanner.
Are the ones that are Bluetooth connected to a phone better/worse than a PC-connected scanner...
They all seem to be about $100-$150....i have searched several other threads on these devices, only to have vendor pop-up ads follow me everywhere!
 

·
Registered
Joined
·
8,486 Posts
I see a difference between a 'Scanner' and a 'Diagnostics tool'. A cheap scanner reads fault codes but may not read all of them, including the EOS roof. A diagnostics tool in the rights hands with knowledge of using it helps you find and fix faults. In both cases the tools are only as good as the V.W algorithm. Fault codes don't always translate to a specific faulty part or the part may not be as faulty as you think.

A 4 door EOS isn't a quick fix with a diagnostics tool, although it will tell you if an electronic module is suspect. Then it's down to you to analyze the data and make a decision which diagnostics doesn't do.
 

·
Registered
Joined
·
53 Posts
Hi all (especially expert voxmagna),
I went ahead and bought the OBD eleven diagnostic scanner....Whoa boy, it looks like my 2007 EOS 2.0 has a ton of problems, so here's what I learned. I also referred to earlier threads here (OBS II, VCDS or ?? | Volkswagen Eos Forum (vweosclub.com) )

1) Most of these module errors are "intermittent" and likely can be deleted since the battery has been replaced, etc....correct?
2) The rear left door problem has me bugged since I have to manually lower all four windows prior to roof operation. Since the car "thinks" the rear left door is open, the interior lights stay on all the time??
3) The airbag "igniter" and dash yellow warning is a problem since a repair shop already did some wire soldering under the driver's seat.

Comments welcome..Thanks
Doug Hitchcock
Cleveland, OH USA



Here's the data (problems in red)
OBDeleven data log
Date: 2022-09-05 17:45
VIN: WVWFA71FX7V046757
Car: Volkswagen Eos
Year: 2007
Body type: Coupe convertible
Mileage: 109090 KM

---------------------------------------------------------------
01 Engine
System description: 2.0l R4/4V TFSI
Software number: 1Q0907115E
Software version: 0020
Hardware number: 8P0907115B
Serial number: VWX7Z0G23NT87J
Long coding: 041C010A1C070160
Trouble codes:
No trouble codes found
---------------------------------------------------------------
02 Transmission
System description: GSG DSG 082
Software number: 02E300043R
Software version: 1302
Hardware number: 02E927770AD
Hardware version: C30
Serial number: 00001007310370
Coding: 0000020
Trouble codes:
No trouble codes found
---------------------------------------------------------------
03 Brakes
System description: ESP FRONT MK60
Software number: 1K0907379AC
Software version: 0101
Hardware number: 1K0907379AC
Coding: 0021218
Trouble codes:
No trouble codes found
---------------------------------------------------------------
04 Steering Angle Sensor
Trouble codes:
No trouble codes found
---------------------------------------------------------------
08 Air Conditioning
System description: ClimatronicPQ35 121
Software number: 1Q0907044J
Software version: 0303
Hardware number: 1Q0907044J
Serial number: 00000000000000
Trouble codes:
No trouble codes found
---------------------------------------------------------------
09 Central Electrics
System description: Bordnetz-SG H52
Software number: 3C0937049AE
Software version: 2002
Hardware number: 3C0937049AE
Hardware version: 063
Serial number: 00000006874236
Long coding: F58C8F0340041000470000000F00000000285D035C0001

Subsystems:
System description: Wischer 020407 021
Software number: 1K1955119E
Software version: 0501
Coding: 0038805

System description: RLS 210307 020
Software number: 1K0955559AB
Software version: 0105
Coding: 0208933

Trouble codes:
01800 - Light switch Implausible signal
Intermittent
02071 - Local data bus No signal/communication
Intermittent
00532 - Supply voltage Lower limit not reached
Intermittent
00446 - Function limitation due to insufficient voltage Lower limit not reached
Intermittent
01520 - Rain/light recognition sensor No signal/communication
Intermittent
01520 - Rain/light recognition sensor Implausible signal
Intermittent
00154 - Front passenger windshield wiper motor Lower limit not reached
Intermittent
02383 - Windshield wiper motor fcn rest. due to insuff. voltage Lower limit not reached
Intermittent
---------------------------------------------------------------
0F Digital Radio
System description: SDAR SIRIUS H06
Software number: 8E0035593H
Software version: 0080
Hardware number: 8E0035593H
Serial number: AUZ4Z7G0068441
Trouble codes:
00532 - Supply voltage Lower limit not reached
Intermittent
00446 - Function limitation due to insufficient voltage Lower limit not reached
Intermittent
02635 - Tuner not enabled/activated
static
01304 - Radio No signal/communication
Intermittent
---------------------------------------------------------------
15 Airbag
System description: 74 Airbag VW8C
Software number: 1Q0959655A
Software version: 0180
Hardware number: 1Q0959655A
Serial number: 003B3001S7W%
Coding: 0014132

Subsystems:
System description: BF-Gewichtsens. 007
Software number: 1Q0959339A
Software version: 0003

Trouble codes:
01217 - Side airbag igniter, driver side Upper limit exceeded
Intermittent

00532 - Supply voltage Lower limit not reached
Intermittent
---------------------------------------------------------------
16 Steering Column
System description: J0527 036
Software number: 1K0953549AQ
Software version: 0070
Hardware number: 1K0953549AQ
Coding: 0012021
Subsystems:
System description: E0221 002
Software number: XXXXXXXXXXX
Software version: 0010
Trouble codes:
No trouble codes found
---------------------------------------------------------------
17 Dashboard
System description: KOMBIINSTRUMENT VDD
Software number: 1Q0920973B
Software version: 1610
Hardware number: 1Q0920973B
Hardware version: 000
Serial number: VWX7Z0G23NT87J
Coding: 0023207
Trouble codes:
00446 - Function limitation due to insufficient voltage Lower limit not reached
Intermittent
00532 - Supply voltage Lower limit not reached
Intermittent
---------------------------------------------------------------
19 Gateway
System description: J533 Gateway
Software number: 7N0907530H
Software version: 1620
Hardware number: 1K0907951
Hardware version: H42
Serial number: 080911F2001841
Long coding: 355000
Trouble codes:
01304 - Radio No signal/communication
Intermittent
00532 - Supply voltage Lower limit not reached
Intermittent
00484 - Vehicle location recognition control module No signal/communication
Intermittent
---------------------------------------------------------------
1C Position Detection
System description: Kompass 002
Software number: 1Q0919965
Software version: 0001
Hardware number: 1Q0919965
Serial number: 1350208TKBCK02
Trouble codes:
No trouble codes found
---------------------------------------------------------------
25 Immobilizer
System description: IMMO VDD
Software number: 1Q0920973B
Software version: 1610
Hardware number: 1Q0920973B
Hardware version: 000
Serial number: VWX7Z0G23NT87J
Trouble codes:
No trouble codes found
---------------------------------------------------------------
26 Roof Control
System description: Verdecksteuergeraet
Software number: 1Q0959255B
Software version: 0622
Hardware number: 1Q0959255B
Hardware version: 000
Serial number: 070820456
Coding: 0655360
Trouble codes:
00532 - Supply voltage Lower limit not reached
Intermittent
---------------------------------------------------------------
42 Driver Door
System description: Tuer-SG 004
Software number: 1Q0959701E
Software version: 1213
Hardware number: 1Q0959701E
Coding: 0001207
Trouble codes:
01811 - Supply voltage for door control module, driver side Lower limit not reached
Intermittent
---------------------------------------------------------------
44 Steering Assistance
System description: EPS_ZFLS Kl.071 H07
Software number: 1K1909144L
Software version: 1806
Trouble codes:
No trouble codes found
---------------------------------------------------------------
46 Comfort System
System description: KSG PQ35 RDK 052
Software number: 1K0959433CT
Software version: 0218
Hardware number: 1K0959433CT
Hardware version: 008
Serial number: 00000000000000
Long coding: 13908A800186281B0804040FB0080E0488DC00
Subsystems:
System description: Sounder n.mounted
System description: NGS n.mounted
System description: IRUE n.mounted
Trouble codes:
00532 - Supply voltage Lower limit not reached
Intermittent
00893 - Release button in rear lid handle Short circuit to ground
Intermittent (but rear lid latch mechanism recently replaced)

---------------------------------------------------------------
52 Passenger Door
System description: Tuer-SG 009
Software number: 1Q0959702H
Software version: 2121
Hardware number: 1Q0959702H
Coding: 0001206

Trouble codes:
No trouble codes found
---------------------------------------------------------------
56 Radio
Trouble codes:
No trouble codes found
---------------------------------------------------------------
62 Rear Left Door
System description: Tuer-SG 006
Software number: 1Q0959703A
Software version: 1203
Hardware number: 1Q0959703A
Coding: 0000192
Trouble codes:
01044 - Control module incorrectly coded no or incorrect basic setting/adaptation
static

01554 - Rear doors central locking LOCK motors Electrical error in circuit
Intermittent
00930 - Lock unit for central locking Left Rear Implausible signal
Intermittent
00937 - Left rear window lift switch Implausible signal
static
00102 - Left rear interior locking button Implausible signal

static
---------------------------------------------------------------
63 Entry Assistance Left
System description: J572 EASYENTRY FS
Software number: 1Q0959790A
Software version: 0603
Hardware number: 1Q0959790A
Hardware version: 560
Serial number: 5DS008646-01--
Coding: 0000002
Trouble codes:
00532 - Supply voltage Lower limit not reached
Intermittent
00446 - Function limitation due to insufficient voltage Lower limit not reached
Intermittent
---------------------------------------------------------------
65 Tire Pressure
System description: RDK
Software number: 1K0959433CT
Software version: 0440
Hardware number: 1K0959433CT
Hardware version: 008
Serial number: 00000000000000
Coding: 0100101
Trouble codes:
00625 - Speed signal Implausible signal
Intermittent
---------------------------------------------------------------
72 Rear Right Door
System description: Tuer-SG 004
Software number: 1Q0959812B
Software version: 0602
Hardware number: 1Q0959812B
Coding: 0000144
Trouble codes:
No trouble codes found
---------------------------------------------------------------
73 Entry Assistance Right
System description: J573 EASYENTRY BFS
Software number: 1Q0959790A
Software version: 0603
Hardware number: 1Q0959790A
Hardware version: 563
Serial number: 5DS008646-01--
Coding: 0000002
Trouble codes:
00532 - Supply voltage Lower limit not reached
Intermittent
00446 - Function limitation due to insufficient voltage Lower limit not reached
Intermittent
02005 - Coding pin Implausible signal
Intermittent
 

·
Registered
Joined
·
53 Posts
hi all,
can anyone help debug these diagnostic codes? I am tempted to have the OBD eleven app cancel out as many as possible? Just don't want to mess up the rest of the software
 

·
Registered
Joined
·
8,486 Posts
If you had a battery problem many random faults can occur. Make sure the battery is good and fully charged then clear all the fault codes. This does no harm to modules. Then turn the key off and on then re-scan. Those faults coming back after clearing are real. Those faults coming on only after clearing then driving are real but in another category. If you still get many voltage supply errors from different modules then you may have a problem with the module system voltage regulator. This produces a stable 5 volts +-0.1V, I think this regulator is non repairable (by most) electronic parts the convenience module? The easist place to measure 5 volts is on one of the most accessible sensor connector pins on the engine top side under the hood - e.g MAF sensor connector?

There are loads of other apparent faults, some may clear with diagnostics but anything voltage related as above will screw up a lot of things.
 

·
Registered
Joined
·
53 Posts
Hi all,
Thanks for the feedback re: my OBD eleven scanner and the faults.

I reset all faults and most of them are now gone. I will likely do this any time the battery dies.
BUT, the left-rear door fault is still bugging me (on a 2-door vehicle!)
The left-rear window operates normally (manually from driver's door) but only goes down half-way when doing roof retract operation?

I don't understand how to CHANGE the coding?

Automotive tire Automotive lighting Font Gadget Communication Device


OBDeleven data log

Date: 2022-09-21 09:04

VIN: WVWFA71FX7V046757
Car: Volkswagen Eos
Year: 2007
Body type: Coupe convertible
Mileage: 109150 KM

---------------------------------------------------------------
62 Rear Left Door

System description: Tuer-SG 006
Software number: 1Q0959703A
Software version: 1203
Hardware number: 1Q0959703A
Coding: 0000192

Trouble codes:
01044 - Control module incorrectly coded no or incorrect basic setting/adaptation
static
00122 - Outside warning light/door exit light LR Electrical error in circuit
static
00937 - Left rear window lift switch Implausible signal
static
00102 - Left rear interior locking button Implausible signal
static

Thanks for any suggestions..
Doug
 

·
Registered
Joined
·
8,486 Posts
I'm more familiar with vcds than OBD11. An EOS scan will report Module 62 Door, Rear Left and module 72 Door, Rear right. What this means is they used standard door controllers hence it reports 'Door' but these are only used as controllers for the rear windows in the 2 door EOS.

When the EOS key is first turned on the ECU defaults to assume a 4 door car but after successful communication with the EOS specific 2 door rear door/window controllers, this is changed to 2 door during the initialization phase. That's how you know if the rear door/window controllers are bad because if there's no communication with them or their internal firmware code is bad they don't mask out the 4 door personality to become 2 doors.

Something about your rear window controllers seems to be odd compared to mine. Have you or anybody changed the modules? Have the rear windows ever worked correctly for you?

MY07 Tdi has the following: Module 62 Door, Rear Left part 1Q0 959 811 B coded 0000128 and Module 72 Door, Rear Right part 1Q0 959 812 B coded 0000128 the same. You cannot assume that my UK parts and coding is the same as yours. Diagnostic tools like vcds have helper screens that tell you what codes mean when they are changed. I know in my case, both rear modules have the same coding but they change the part number by '1' to differentiate the left and right side, which I assume coincides with different internal firmware? Therefore I'm puzzled by what OBD11 is reporting for your car?

Before thinking and learning how to change coding to dig an even deeper hole for yourself, if you can't confirm rear modules are correct and always worked, I would run those part numbers past your dealer first who will tell you if they are correct for your VIN? Nothing is straight forward on these cars and your modules and coding may be correct? If diagnostics doesn't have a coding helper you will have to find out what it is from somebody here who has scanned their working car and has exactly the same rear door/window modules fitted. That's why it's important when buying a diagnostics tool you should scan and save the results before getting faults. That saved scan has all your module part numbers and coding which you can refer back to.

Finally, these modules are vulnerable to firmware corruption particularly when replacing batteries. In most cases this can be fixed by a dealer who will reflash them with their special kit. Alternatively, you can try leaving the battery disconnected for 2 or 3 days, then carefully reconnect it without arcs or sparks. If you are lucky, the modules will cold boot after IGN on and self install fresh uncorrupt firmware.

If this is all a bit much for you, let a dealer sort it out.
 
1 - 18 of 18 Posts
Top