Hello forum,
I have an ongoing issue with my 2.5TDI 2002 T4 transporter. The engine runs but very lumpy at idle. There is no power when driving. Originally thought it was turbo issue but now thinking its a fuel timing problem as lots of blow by in crankcase (crankcase breather popping off). Possibly a dud ECU but it does run and drive so not sure.
This led me onto posting on T4forums, where I was asked to use VCDS. I attempted first a Gendan KKL cable and could only get communication with the immobo and dash display. Since then I have purchased the Hex V2, with same result. I also checked the following:
- continuity of the diagnostic wires from the fuse box to the ECU,
- the diagnostics point checked earths, checked live, check continuity to the immobo, radio is disconnected but checked the continuity on the K line all using/following official T4 wiring diagrams.
Didnt find any problems there.
The interface connects fine, but have noticed that the Vignition voltage is 0.03V not sure if this is because of an issue on the van, or because my vcds socket doesnt have power from the ignition like other vehicles may? I do of course get ignition voltage on the van when turning the key.
Could someone please support me in attempting to connect to the ECU please. Below the only data I could pull using the Autoscan feature. When clicking on other modules (such as Engine-01) I receive no response error message.
***I also carried out another scan for a different chassis number as the year in brackets matched my van and these are the results.***
Back Story - Maybe relevant, maybe not.
Originally van wouldnt start at key turn first go, would have to repeat key turn, this led onto not starting at all. Van always ran well up until this point. Been remapped in the past.
Found melted cables from the glow plugs to the ignition key. New wiring looms fitted to engine and key by myself, new glow plugs. Van would then turn over but not stay running. New cable was fitted to the Fuel shut off solenoid from ignition (by garage) allowing van to start, I had previously found that wire to the fuel shut off solenoid was very corroded, and I broke this during attempting to remove solenoid. I supplied new solenoid to mechanic when van when in to his garage, but he didnt use the new one, just added a wire from ignition switch to the fuel shut off solenoid, mechanic said seems to be an issue with immobo (he was using Vagcom) so he bypassed it, but never mentioned anything about ECU communication. The van wont start if non immobo key is used, so its not actually bypassed like he said, just the fuel shut off solenoid.
Since receiving the van back, it runs like a mess as previously stated. I have a guy providing guidance on the T4forums but VCDS is not connecting so at a standstill currently.
T4Forums post if you wanted to read:
www.vwt4forum.co.uk
I have an ongoing issue with my 2.5TDI 2002 T4 transporter. The engine runs but very lumpy at idle. There is no power when driving. Originally thought it was turbo issue but now thinking its a fuel timing problem as lots of blow by in crankcase (crankcase breather popping off). Possibly a dud ECU but it does run and drive so not sure.
This led me onto posting on T4forums, where I was asked to use VCDS. I attempted first a Gendan KKL cable and could only get communication with the immobo and dash display. Since then I have purchased the Hex V2, with same result. I also checked the following:
- continuity of the diagnostic wires from the fuse box to the ECU,
- the diagnostics point checked earths, checked live, check continuity to the immobo, radio is disconnected but checked the continuity on the K line all using/following official T4 wiring diagrams.
Didnt find any problems there.
The interface connects fine, but have noticed that the Vignition voltage is 0.03V not sure if this is because of an issue on the van, or because my vcds socket doesnt have power from the ignition like other vehicles may? I do of course get ignition voltage on the van when turning the key.
Could someone please support me in attempting to connect to the ECU please. Below the only data I could pull using the Autoscan feature. When clicking on other modules (such as Engine-01) I receive no response error message.
Code:
Chassis Type: 70 (70 - VW Transporter/Multivan (1991 > 1996))
Scan: 01 02 03 08 15 22 25
VIN: WV1ZZZ70Z2H130152
-------------------------------------------------------------------------------
Address 25: Immobilizer Labels: 6X0-953-257.lbl
Part No: 6X0 953 257
Component: IMMO 0008
Coding: 00001
Shop #: WSC 00000
VCID: 7DA7F71344EF0B03A49-4B1E
WV1ZZZ70Z2H130152 VWZ1Z0B2022104
No fault code found.
End----(Elapsed Time: 01:46, VBatt start/end: 14.5V/14.5V. VIgn 0.0V)------***I also carried out another scan for a different chassis number as the year in brackets matched my van and these are the results.***
Code:
Chassis Type: 70 (7D - VW Transporter/Multivan (1996 > 2004))
Scan: 01 02 03 08 15 17 18 19 22 25 35 37 56
VIN: WV1ZZZ70Z2H130152 Mileage: 439800km-273279miles
-------------------------------------------------------------------------------
Address 17: Instruments Labels: 7D0-920-xxx-17.lbl
Part No: 7D0 920 902 P
Component: T4-KOMBIINSTR. VDO V01
Coding: 00411
Shop #: WSC 02757
VCID: 313F1B23C8373F63701-5184
No fault code found.
-------------------------------------------------------------------------------
Address 19: CAN Gateway Labels: 6N0-909-901-19.clb
Part No: 6N0 909 901
Component: Gateway K<->CAN 0001
Coding: 00000
Shop #: WSC 02757
VCID: 70B9DE2703BD766B3FF-5184
No fault code found.
-------------------------------------------------------------------------------
Address 25: Immobilizer Labels: 6X0-953-257.lbl
Part No: 6X0 953 257
Component: IMMO 0008
Coding: 00001
Shop #: WSC 00000
VCID: 7DA7F71344EF0B03A49-4B1E
WV1ZZZ70Z2H130152 VWZ1Z0B2022104
No fault code found.
End----(Elapsed Time: 03:08, VBatt start/end: 14.5V/14.5V. VIgn 0.0V)------Back Story - Maybe relevant, maybe not.
Originally van wouldnt start at key turn first go, would have to repeat key turn, this led onto not starting at all. Van always ran well up until this point. Been remapped in the past.
Found melted cables from the glow plugs to the ignition key. New wiring looms fitted to engine and key by myself, new glow plugs. Van would then turn over but not stay running. New cable was fitted to the Fuel shut off solenoid from ignition (by garage) allowing van to start, I had previously found that wire to the fuel shut off solenoid was very corroded, and I broke this during attempting to remove solenoid. I supplied new solenoid to mechanic when van when in to his garage, but he didnt use the new one, just added a wire from ignition switch to the fuel shut off solenoid, mechanic said seems to be an issue with immobo (he was using Vagcom) so he bypassed it, but never mentioned anything about ECU communication. The van wont start if non immobo key is used, so its not actually bypassed like he said, just the fuel shut off solenoid.
Since receiving the van back, it runs like a mess as previously stated. I have a guy providing guidance on the T4forums but VCDS is not connecting so at a standstill currently.
T4Forums post if you wanted to read:
Low charge air pressure, no turbo boost
Hello guys, I have an ongoing issue with my 2.5TDI AJT engine with assumed low charge air pressure. This engine has the EGR blanked and EGR intercooler removed. Previously been remapped. The problem - While sitting on the drive and someone revving the van to 4k revs the turbo arm only...
www.vwt4forum.co.uk
Last edited by a moderator:
