Thread: Discovery 2 starting problem

Is it an auto? You haven’t mentioned the XYZ switch.

Also, I had some strangeness in mine a while back and traced it to some corrosion in the in cabin fusebox. Just a thought.

I'm thinking dicky solenoid.

have you got the original style batter terminal connector?
These can also cause issues. Mine did, and was changed for this exact reason.
The wire gets a bit loose in the "crimped" part of the connector and the fixing cam/nut mechanism gets very vague and doesn't clamp as well as it should.

Some live troubleshooting is needed: you must see when it refuses to crank if the starter relay is engaging or not, if it does there is a bad contact in that fusebox or in the associated connector,(provided the lucar connector to the starter solenoid terminal is well connected) if the relay doesnt engage when you turn the ignition to crank the problem can be in the interior fusebox too(they used to suffer from corrosion)

Originally Posted by sierrafery

if the relay doesnt engage when you turn the ignition to crank the problem can be in the interior fusebox too(they used to suffer from corrosion)

They still do, although mine, amongst other things, caused it to crank in ignition position II, which was fun.

It doesn't take much, and can cause all manner of weirdness:
IMG_5875.jpgIMG_5877.jpgIMG_5876.jpg

Thanks to all for the guidance.
I haven't lifted the engine bay fuse box but will as the last throw to achieving normality. In desperation I have installed a push-button switch in a direct wire from battery to starter relay terminal. With key at position2, excellent starting, but still no start by key at cranking position 3. It never rains but it pours- with the switch operating the engine would start and run 10 seconds only. After some inspiring reading in the notes to my Black Box Solutions Faultmate MSV 2 analyzer I checked the door locking action, no joy, then I noticed the red light in the key was not present. Replaced the battery in the key and engine runs continuously.

Now it's clear, it was an immobiliser issue