VW T4 Forum - VW T5 Forum banner

1 - 12 of 12 Posts

·
Registered
Joined
·
4 Posts
Discussion Starter #1
Hi all, been having a nightmare with my van the last week!

recently my van has been occasionally into limp mode whilst driving (could have been down to leaky fuel rail on engine which is now fixed) and then the other day whilst driving along fine the console lit up like a christmas tree but the van continued to drive along fine until i stopped and tried to restart the engine, the engine would fire but then cut out after a secound. after towing it home and connecting it to vcds the following faults were logged.

Address 01: Engine Labels: 070-906-016-AXD.clb
Part No SW: 070 906 016 AJ HW: 028 101 156 8
Component: R5 2,5L EDC G000SG 7002
Revision: 12345678 Serial number: VWZ7Z0F3524839
Coding: 0001072
Shop #: WSC 02756 785 00200
VCID: 58EA81D56E0788D76A8-5184

2 Faults Found:
18058 - Powertrain Data Bus
P1650 - 000 - Missing Message from Instrument Cluster
Freeze Frame:
RPM: 0 /min
Torque: 275.7 Nm
Speed: 0.0 km/h
Load: 0.0 %
Voltage: 12.24 V
Bin. Bits: 00001100
Torque: 0.0 Nm
Torque: 146.4 Nm

18045 - Powertrain Data Bus
P1637 - 000 - Missing Message from Electric Load Controller
Freeze Frame:
RPM: 0 /min
Torque: 275.7 Nm
Speed: 0.0 km/h
Load: 0.0 %
Voltage: 12.24 V
Bin. Bits: 00001100
Bin. Bits: 00000000
(no units): 1.0

Readiness: 0 0 X X X

-------------------------------------------------------------------------------
Address 08: Auto HVAC Labels: Redir Fail!
Part No: 7H0 820 045 AC
Component: CLIMA/AC 0303
Shop #: WSC 00000 000 00000
VCID: 6696BF2DD4732E27E84-513C

2 Faults Found:
00229 - Refrigerant Pressure
002 - Lower Limit Exceeded
01299 - Diagnostic Interface for Data Bus (J533)
013 - Check DTC Memory

-------------------------------------------------------------------------------
Address 09: Cent. Elect. Labels:. 7H0-937-049.lbl
Part No: 7H0 937 049 T
Component: BORDNETZ SGVER 1.0 2001
Coding: 0000101
Shop #: WSC 02756 785 00200
VCID: 43D046B987813B0F2FA-513C

2 Faults Found:
01299 - Diagnostic Interface for Data Bus (J533)
013 - Check DTC Memory
01341 - Control Module in Instrument Panel On Comfort CAN (J285)
008 - Implausible Signal

-------------------------------------------------------------------------------
Address 17: Instruments Labels: 7Hx-920-xxx-17.lbl
Part No: 7H0 920 951 N
Component: KOMBI+WEGFAHRSP VDO V02
Coding: 00412
Shop #: WSC 00527
VCID: 37282269C65967AF832-513C
WV2ZZZ7HZ6H115194 VWZ7Z0F3524839

4 Faults Found:
00771 - Fuel Level Sensor (G)
30-00 - Open or Short to Plus
00562 - Sensor for Oil Level/Temperature (G266)
30-00 - Open or Short to Plus
00779 - Outside Air Temp Sensor (G17)
30-00 - Open or Short to Plus
01312 - Powertrain Data Bus
37-00 - Faulty

-------------------------------------------------------------------------------
Address 19: CAN Gateway Labels: 6N0-909-901-19.lbl
Part No: 6N0 909 901
Component: Gateway K<->CAN 0001
Coding: 00006
Shop #: WSC 02756
VCID: 70BAD975E3B7F097828-513C

1 Fault Found:
01312 - Powertrain Data Bus
37-00 - Faulty

-------------------------------------------------------------------------------
Address 46: Central Conv. Labels: 7H0-959-433.lbl
Part No: 7H0 959 433 B
Component: C2L Komfortgerát 0004
Coding: 00069
Shop #: WSC 02756
VCID: 323E137D2D3B8287B4C-4B1E

Subsystem 1 - Part No: 7H2959802
Component: Tõrsteuer.FS KLO 0203

Subsystem 2 - Part No: 7H2959801
Component: Tõrsteuer.BF KLO 0203

No Faults Found
or DTCs not supported by controller
or a communication error occurred

End----------(Elapsed Time: 06:41, VBatt start/end: 12.2V/12.1V)-----------


Having searched around on here i found a few threads where people had similar issues and faults along with solutions, unfortunately none of which have solved the problem. I have checked both the ecu under the battery tray and the module under the steering wheel to see if any pins had burnt out/ corroded but all looks ok. Can anyone shed any light on what to check next? hoping to find a solution without having to remove and check the wiring loom. I have recently had the engine out and fitted cruise control but the van has been working fine for the last couple of months since that was done until the other day.

Any help greatly appreciated!
 

·
Special Rapporteur
Joined
·
9,771 Posts
Is that the complete VCDS scan? If so, the immediate thing that stands out is a lack of response from Address 03 - the ABS controller.

On a 2006 van there are relatively few devices on the powertrain data bus - the most obvious being the ECU, the ABS controller, the CAN Gateway and the Airbag controller - though there may be one or two others depending on options fitted.

So, assuming that you've chosen the correct model number in VCDS (which determines the list of devices it scans for, on which addresses) I would start by suspecting something wrong at the ABS controller. At the very least I would try unplugging the loom and checking the connector. If you've had the engine out it's not inconceivable that this has taken a knock and may not be fully engaged.
 

·
Registered
Joined
·
2,129 Posts
I would say you could start by getting hold of a wiring diagram/diagrams that show all of the data-bus wiring.

On you fault code read-out there's a large number of sensors & units that allegedly have failed. Far too many I would say to believe. Address 17 shows a number of engine sensors that have lost power & it strikes me that if the data-bus wiring has failed somewhere that could account for your issues.
You need to do some wiring checks using a multi-meter on the data-bus wiring first to confirm one way or the other that it is OK & then go from there.
I'm guessing the data-bus wiring will be just a couple of wires that link around a lot of the vans control units, but as I've never had anything to do with the data-bus on these vans before I can't be any more help with it. Other than to say, form my experience on modern aircraft if a data-bus, (usually a screened, twin core cable that links around the various computers connecting them all together) fails it can quite often fail to read any information from that particular unit where it's failed & sometimes, depending upon the type of failure, any units after the failed part.

As I said in my previous post, there is another member on here recently with what at first glance appears to be a similar issue with the data-bus not communicating with the ASR/ABS & albeit on a different year vehicle, (a lot earlier year I think) it could be worth keeping an eye on that thread to compare the two.
 

·
Registered
Joined
·
4 Posts
Discussion Starter #6
thanks for all your replies so far, greatly appreciated.

checked all the wires with a multimeter and all seems good, also checked the abs connector and all seems ok in there, but it is still throwing up the same faults. is it worth replacing the cables, even though the seem ok with continuity that doesn't always mean the signal will be good? any other ideas on where to check next?

Im selecting 7h in vcds which i believe to be the correct model number for my van (2006 2.5 AXD engine) but when i select the ABS module vcds doesnt even acknowledge its exsistance, if the ABS control unit was faulty would this be the case?

having now removed most of the bumper and the whole of the dash board this issue is starting to annoy me!!
 

·
Special Rapporteur
Joined
·
9,771 Posts
Yes - chassis type 7H is right (or right enough) for that year.

Which version of VCDS are you using? Can you post up the complete scan? It's very odd that VCDS does not even appear to be looking at address 03.

If the ABS controller has failed completely then I would expect to see a "no communications" error from it.

I don't think you are looking at a single wire failure here. The CAN network is very robust. It's designed to work over 2 wires but can fall back to functioning over just one at reduced speed.

If you look at the CAN gateway you should be able to see what CAN devices are configured to be on the network. However, I can't think of a good reason why that config would have suddenly changed, and it would not make a difference to the VCDS scan either, because AFAIK the gateway config is ignored by VCDS on a pre-facelift.

One other thing to check: do you know for sure that your battery and alternator are both good? You can get very odd symptoms if the battery voltage sags too low. I notice you had a battery voltage in the scan you included earlier, but don't know if that was engine running or not.
 

·
Registered
Joined
·
4 Posts
Discussion Starter #8
Vcds Version is 18.2, the full scan results are below. when trying to access 03 - ABS it produces the error message 'No response from controller' would this indicate that the ABS controller could be faulty or bad communication with it?

When you say look at can gateway, im new to using vagcom so i don't fully understand what i'm looking for/where to be looking for the list?

The van currently wont start, it will fire then cut out after a second so the alternator is not in use but the battery has been recharged but is still only showing 12.5V which is quite low, i will put it back on charge and try a different battery to see if that helps.


Wednesday,07,March,2018,16:54:55:20017
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 7 x64
VCDS Version: 18.2.0.3 (x64) HEX-V2 CB: 0.4411.4
Data version: 20180212 DS287.0
www.Ross-Tech.com


VIN: WV2ZZZ7HZ6H115194 License Plate:
Mileage: 487610km-302986mi Repair Order:



--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Chassis Type: 7H (7H - VW Transporter/Multivan (2003 > 2010))
Scan: 01 02 03 08 09 0B 0D 15 16 17 18 19 1C 22 2D 37 45 46 47 56
57 6E 76 77 78 7D

VIN: WV2ZZZ7HZ6H115194 Mileage: 487610km-302986miles
-------------------------------------------------------------------------------
Address 01: Engine Labels: 070-906-016-AXD.clb
Part No SW: 070 906 016 AJ HW: 028 101 156 8
Component: R5 2,5L EDC G000SG 7002
Revision: 12345678 Serial number: VWZ7Z0F3524839
Coding: 0001072
Shop #: WSC 02756 785 00200
VCID: 58EA81D56E0788D76A8-5184

7 Faults Found:
18058 - Powertrain Data Bus
P1650 - 000 - Missing Message from Instrument Cluster
Freeze Frame:
RPM: 0 /min
Torque: 275.7 Nm
Speed: 0.0 km/h
Load: 0.0 %
Voltage: 12.62 V
Bin. Bits: 00001100
Torque: 0.0 Nm
Torque: 146.4 Nm

18045 - Powertrain Data Bus
P1637 - 000 - Missing Message from Electric Load Controller
Freeze Frame:
RPM: 0 /min
Torque: 275.7 Nm
Speed: 0.0 km/h
Load: 0.0 %
Voltage: 12.62 V
Bin. Bits: 00001100
Bin. Bits: 00000000
(no units): 1.0

16497 - Intake Air Temp. Sensor (G42)
P0113 - 000 - Signal too High
Freeze Frame:
RPM: 0 /min
Torque: 275.7 Nm
Speed: 0.0 km/h
Load: 0.0 %
Voltage: 12.62 V
Temperature: 133.2°C
Temperature: 3.6°C
Temperature: 4.5°C

18045 - Powertrain Data Bus
P1637 - 000 - Missing Message from Electric Load Controller
Freeze Frame:
RPM: 0 /min
Torque: 275.7 Nm
Speed: 0.0 km/h
Load: 0.0 %
Voltage: 12.62 V
Bin. Bits: 00001100
Bin. Bits: 00000000
(no units): 1.0

18043 - Powertrain Data Bus
P1635 - 000 - Missing Message from A/C Controller
Freeze Frame:
RPM: 0 /min
Torque: 275.7 Nm
Speed: 0.0 km/h
Load: 0.0 %
Voltage: 12.62 V
Bin. Bits: 00001100
Bin. Bits: 00000000
(no units): 144.0

16622 - Manifold Pressure / Boost Sensor (G31)
P0238 - 000 - Signal too High
Freeze Frame:
RPM: 0 /min
Torque: 275.7 Nm
Speed: 0.0 km/h
Load: 0.0 %
Voltage: 12.62 V
Bin. Bits: 00001100
Absolute Pres.: 1336.2 mbar
Absolute Pres.: 2182.8 mbar

17978 - Engine Start Blocked by Immobilizer
P1570 - 000 - - MIL ON
Freeze Frame:
RPM: 0 /min
Torque: 275.7 Nm
Speed: 0.0 km/h
Load: 0.0 %
Voltage: 8.21 V
Bin. Bits: 00001100
Bin. Bits: 11000000
(no units): 0.0

Readiness: 0 0 X X X

-------------------------------------------------------------------------------
Address 09: Cent. Elect. Labels:. 7H0-937-049.lbl
Part No: 7H0 937 049 T
Component: BORDNETZ SGVER 1.0 2001
Coding: 0000101
Shop #: WSC 02756 785 00200
VCID: 43D046B987813B0F2FA-5160

4 Faults Found:
01299 - Diagnostic Interface for Data Bus (J533)
013 - Check DTC Memory
01341 - Control Module in Instrument Panel On Comfort CAN (J285)
008 - Implausible Signal
01598 - Drive Battery Voltage
002 - Lower Limit Exceeded
01330 - Central Control Module for Central Convenience (J393)
004 - No Signal/Communication

-------------------------------------------------------------------------------
Address 17: Instruments Labels: 7Hx-920-xxx-17.lbl
Part No: 7H0 920 951 N
Component: KOMBI+WEGFAHRSP VDO V02
Coding: 00412
Shop #: WSC 00527
VCID: 37282269C65967AF832-5160
WV2ZZZ7HZ6H115194 VWZ7Z0F3524839

5 Faults Found:
00771 - Fuel Level Sensor (G)
30-00 - Open or Short to Plus
00562 - Sensor for Oil Level/Temperature (G266)
30-00 - Open or Short to Plus
00779 - Outside Air Temp Sensor (G17)
30-00 - Open or Short to Plus
01312 - Powertrain Data Bus
37-00 - Faulty
01330 - Central Control Module for Central Convenience (J393)
49-00 - No Communications

-------------------------------------------------------------------------------
Address 19: CAN Gateway Labels: 6N0-909-901-19.lbl
Part No: 6N0 909 901
Component: Gateway K<->CAN 0001
Coding: 00006
Shop #: WSC 02756
VCID: 70BAD975E3B7F097828-5160

3 Faults Found:
01312 - Powertrain Data Bus
37-00 - Faulty
01330 - Central Control Module for Central Convenience (J393)
49-00 - No Communications
01320 - Control Module for Climatronic (J255)
49-00 - No Communications

End----------(Elapsed Time: 06:41, VBatt start/end: 12.5V/12.5V)-----------


cheers for you help!
 

·
Special Rapporteur
Joined
·
9,771 Posts
Fair comment - the battery volts won't be with the engine running if you can't start it!

It certainly appears as though not much is talking to anything else on either of the CAN networks.

It's difficult to say anything conclusive about the ABS controller - because if it's alive and well but the network connections are dead you will still see no communications with it!

As you've probably already concluded, the engine is being cut by the immobiliser - and this is probably because it can't communicate with other key modules on the van.

Can you confirm that all of the electronic control modules (specifically the ECU and the dash insert) are the originals for the van?
 

·
Registered
Joined
·
4 Posts
Discussion Starter #10
i believe all the modules to be original, but i cant say for sure as i havent had the van from new. Ive had the van for 5 years and never had any issues like this before. Im going to bite the bullet and take the ecu and ABS controller for testing see if that shows any issues.

One thing that confuses me is that it is finding different faults each time i run the scan, is this normal?
 

·
Premium Member
Joined
·
4,705 Posts
Had similar problems with a customers Transporter, it was the Cluster that was at fault... he sent it away for repair, then we were able to access it all via VCDS
 

·
Special Rapporteur
Joined
·
9,771 Posts
I was thinking the same - the dash insert is where the CAN networks come together (with the diagnostic port) so if there's a single fault, that's a likely point. Unfortunately it's the most complicated to change, so test and repair (rather than swap in another unit) is probably the easiest option.
 
1 - 12 of 12 Posts
Top