Skip to content

Engine will only run for 2 secs

Featured Replies

Hi all I'm in need of some expert assistance again, I've just come back from a week away and the car was parked at Birmingham airport. The problem started when I went to start the car, it fired up for about 2 secs then died and refused to start after that unless I close all the doors lock and unlock and start again, then I just get the 2 secs of life. Other things noted

1 no glow pre heat light

2 no wipers

3 no dash lighting, with lights on

4 no dash indicator repeater warning (green arrows)

5 immobiliser light comes on for about 2 secs then gos out

6 if I leave the ignition on I get a flashing red brake warning with bleeps

7 carnt read any info with vcds...

8 locks and unlocks fine with fob

07 oct mk2 vrs tdi

I'm now home after a long day with lots of AA peeps, any advice would be fantastic

Martin

Is the Battery ok? After standing for a week with these symptoms that is the first thing I'd check. 

 

Low battery voltage causes all sorts of strange occurrences on the Octavia.

Edited by booke23

sounds like an immo problem.

  • Author

Yes that was fine, flat now only because I been trying all sorts of different ways of starting it :)

  • Author

I would like to try the spare key to rule out the Immobiliser but I put it somewhere safe 6 years ago :/

If you can't read anything with VCDS it sounds like gateway has gone down. This would certainly cause the faults you have. Given the recent wet weather I would check for water ingress. Two ways of getting to the control unit. You can either take off the interior trim by the drivers knees and go up that way. Personally I find it easier to take the scuttle trim out, remove the wiper linkage and remove the plastic plate.

  • Author

If you can't read anything with VCDS it sounds like gateway has gone down. This would certainly cause the faults you have. Given the recent wet weather I would check for water ingress. Two ways of getting to the control unit. You can either take off the interior trim by the drivers knees and go up that way. Personally I find it easier to take the scuttle trim out, remove the wiper linkage and remove the plastic plate.

If its the gateway I changed in order to get rid of the battery drain issue for the Columbus then it's up above the glove box.? Would that be the said item?

There maybe a few locations then, they did move them about on later cars. Address word 19 is gateway and it handles communication between control units. If it falls over then you get the symptoms you describe. It's a small square control unit with a single plug on it. Usually blue or red.

  • Author

Hi again, tonight ive checked with the spare key and put the old gateway back in and managed to do a bit of a scan with the following results. anyone know what this lot means ????......Please

 

VCDS Version: Release 12.12.0 (x64)
Data version: 20130910

Monday,28,October,2013,19:25:25:32803

Chassis Type: 1Z (1U - Skoda Octavia (1997 > 2011))
Scan: 01 02 03 08 15 16 17 19 22 29 35 36 37 39 46 56 76
 
VIN: TMBEH21Z972068237   
-------------------------------------------------------------------------------
Address 01: Engine        Labels: None
   Part No SW: CUSTOM-CODE     HW: 03G 906 018 EL
   Component: JBS PPD DPF    G    OFF   
   Revision: --H32---    Serial number: SKZ7Z0F3813160
   Coding: 0000072
   Shop #: WSC 66565 257 00032
   VCID: 234FDE58E155DB06A91-513C

7 Faults Found:
005685 - Powertrain Data Bus
               P1635 - 009 - Missing Message from A/C Controller
005785 - Powertrain Data Bus
               P1699 - 009 - Missing Message from Steering Wheel Electronics
005712 - Powertrain Data Bus
               P1650 - 009 - Missing Message from Instrument Cluster
005785 - Powertrain Data Bus
               P1699 - 009 - Missing Message from Steering Wheel Electronics
006272 - Powertrain Data Bus
               P1880 - 009 - Missing Message from Diagnostic Gateway
005488 - Engine Start Blocked by Immobilizer
               P1570 - 008 -
005696 - Internal Control Module
               P1640 - 009 - EEPROM Error - Intermittent
Readiness: N/A

  • Author

cool thanks..... is the ecu power relay in the ecu ?

EEPROM error is worrying on a mapped ECU.

Does it run now? The fact you now have communication means there was an issue with gateway. Will any of the codes clear?

Battery drain can make those codes show up.

Like the rosstech sais, unplug the cables drom battery and toutch them together for a few seconds, this will drain all unwanted power from system.

I did this once.

  • Author

I could only get comms from scanning in 1u rather than 1z chassis the codes clear but are straight back, still will only run for 2 secs. Also tried the joining of the power leads together for 10 mins, then put jump leads on another running car just to make sure there was plenty of power .......same result .......dead

I've about exhausted all ideas now so booked it in to the stealers. :(

Thanks for all the help guys.

It's a gateway/comms issue. All the control units are reporting that they can't communicate with one another. Hence the starting issue. If the engine ECU can't talk to the dash then it won't start. Wild stab in the dark but what I'd do is disconnect the engine ECU and see if the can bus comes back up. If that does nothing try other control units one by one. You can get into 19 gateway, have a look in the value blocks, you should be able to see what's seeing what.

You have an ECU issue, was de car remapped, was the ECU opened.

If soo, I got the feeling water must goy in.

To access the ECU you need to take out wipers and plastic surrounding bottom of windshield.

After taling ECU from clips/holding structure, just holded having the main plug facing down.

Have someone try to start the  car to see.

I donnot recomend this often as could burn something inside, water contact.

Here is an ECU from a 1.6tdi after mapped and wasn´t sealed properly

dsc0047km.jpg
dsc0049jty.jpg
dsc0056ag.jpg

a 2007 Octavia VRS TDi would be remapped through the OBD port, it wouldn't need to be opened up. That's only for the newer models with TRICORE & really old models that can't be done by OBD

  • Author

Evening all. Ok our beloved skoda tech guy called me today and said they carnt get any comms from the car, so they will need 3 hours labour to start looking for wiring faults.

So I'm just shy of 300 quid lighter with no news, nor a car that runs.

I feel this is going to be expensive :(.

I will post more news as I find out.

  • Author

Today's update.....

The dealer called me and said its good news.

They said the fault was wiring somewhere between dash and engine bay. They Located the problem under battery tray a wire that had corroded off. All repaired and running fine I'm told, so not a major expense.

I'm not sure which wire it was but ill have a look when I get the car home, it just may help someone else with the same problem. :)

Thanks again guys.

Bad earth? Glad its worked out ok, could have been squeaky bum time!!

  • Author

Or a canceled Xmas lol

Either a CAN wire or a supply from ebox for the gateway i'd expect. Either way they have done well to find it and fix it. Good work by the tech there, CAN faults 'can' be  nightmare.

  • 5 years later...
On 05/11/2013 at 20:47, martin1611 said:

Today's update.....

The dealer called me and said its good news.

They said the fault was wiring somewhere between dash and engine bay. They Located the problem under battery tray a wire that had corroded off. All repaired and running fine I'm told, so not a major expense.

I'm not sure which wire it was but ill have a look when I get the car home, it just may help someone else with the same problem. :)

Thanks again guys.

Hi can i ask if you what and where the wire broken was! Was it an earth! i have the same problem! 

Hi can i ask if you what and where the wire broken was! Was it an earth! i have the same problem! 

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.