Transmission Fault message

[Silenceisgolden]

Twice during a recent 1,000 kilometre trip I have seen the message "Transmission fault" and the transmission has locked into 3rd gear. Command shift didn't work, just 3rd gear whatever I tried.

Both times it cleared simply by stopping the engine and re-starting. Has anyone else come across this? Is it a sign of bad things to come? Car is a D4 MY2011, 84,000 kilometres, no towing, no city driving, no serious off-road. Typical country car.

Thanks for any suggestions.

[lpj]

Could be the brake switch. It's not expensive to replace. Are you under warranty still?

[lpj]

also, replacing the brake light globes with non genuine can cause the computers to have a little tanty.

[Graeme]

What occurred immediately prior to the message?
Is your VIN before BA588607?
You need to get the gearbox fault codes retrieved.

PS LED brake lights are fitted to these vehicles.

[Silenceisgolden]

Thanks for the replies. Lpj, yes, I still have 10 months of the extended warranty left, so I might end up getting my moneys worth from it!

Yes Graeme, the VIN is earlier, BA578560. Does this mean I should be getting a software update or something? I didn't see any other warnings on the dash before the message - at both times I was in the Snowy Mountains using the command shift a lot for the downhill sections. I didn't see the message untill I looked for it, after noticing that it was stuck in 3rd.

This also happened when the car was nearly new - again, it was while using command shift for engine braking a lot. Then it also cleared with an engine stop and re-start.

[IndusD4]

I get this from time to time when in low range with the gear selector in D. I put it down to it having difficulty finding the right gear, as every time it happens I'm on an incline. Like you say, turning off the engine and starting it again clears the error message. I did check for fault codes once after it happened but there weren't any.

Mine is a 2011 TDV6, VIN is later than BA588607. As in my case it only happens in low range, it hasn't really bothered me.

Ron

[Silenceisgolden]

Thanks Ron, makes me feel a bit better if I am not the only one. I am not concerned if it is just an occasional glitch in the ECU - just as long as the ECU is not responding to some bad news within the transmission.

[s7oney]

Hi
That could be very bad news or pretty much nothing, getting the fault codes read is definitely the place to start

Sent from my GT-I9506 using AULRO mobile app

[Graeme]

Yes Graeme, the VIN is earlier, BA578560. Does this mean I should be getting a software update or something?The gearbox is in the range for when soft stator bushes were used. If any of the faults are P0729 to P0735, P0783, P2702 to P2704 (The issue is the subject of a Land Rover Technical Bulletin, no LTB00514, issued 17th January 2013) then the gbox is dying and you should take steps to get it rebuilt under warranty. If none of the above faults then make sure the oil is changed more frequently than generally advised, possibly every 50K Kms, to keep the metal contamination low to prolong the life of the bushes.

[Silenceisgolden]

The gearbox is in the range for when soft stator bushes were used. If any of the faults are P0729 to P0735, P0783, P2702 to P2704 (The issue is the subject of a Land Rover Technical Bulletin, no LTB00514, issued 17th January 2013) then the gbox is dying and you should take steps to get it rebuilt under warranty. If none of the above faults then make sure the oil is changed more frequently than generally advised, possibly every 50K Kms, to keep the metal contamination low to prolong the life of the bushes.

Thanks Graeme, I hadn't heard of that problem. I am a bit green on the whole fault reading bit - I have an OBD2 reader that I bought to use on my tractor. If I use it on the car, will it delete the fault messages thus making a problem for the dealer if I take it in for repair? Being now in a rural area, it is a 7 hour drive to my dealer to have codes read.

[LRD414]

Your generic OBDII reader is unlikely to pick up much, especially not on the transmission. Given your distance from a dealer, investing in one that reads all ECUs may be worth it. You can read codes without clearing if you wish to preserve them for dealer investigation or clear them yourself. If it's a persistent issue the codes will return anyway.

The IID tool from GAP is used by many, including me. Have a look at this thread:

http://www.aulro.com/afvb/electronic-diagnostic-systems/210627-diagnostic-tool-a14my-d4-sdv6.html

Also, here's a link to a Disco3 thread that provides a wealth of detail regarding the transmission bush failure that Graeme has described:

DISCO3.CO.UK - View topic - 6-sp auto gearbox - flushes, faults, failure and 'finking' (http://www.disco3.co.uk/forum/topic108824.html)

It could be the brake switch but that usually seems to be accompanied by other errors such as HDC (only based on what I've read, it hasn't happened to me).

Hope that helps.

Scott

[Silenceisgolden]

Great info Scott, thank you. Reading the UK posts it does sound like my problem - I had also noticed that it seemed reluctant to lock the torque converter which was also mentioned in the UK forum.

I will investigate getting a better code reader - it seems that the IIDTool requires either an iPad (no Android yet) or the flashier D4 screen - mine has the old basic screen.

Thanks again everyone for the help.

Cheers,

Paul

[shanegtr]

IID tool works with the basic screen as well, mine works fine with my 05 D3;)

[gghaggis]

There is an Android app out for the IID GAP tool - I use it regularly. It will also work with the D3 or D4 screen.

Cheers,

Gordon


Great info Scott, thank you. Reading the UK posts it does sound like my problem - I had also noticed that it seemed reluctant to lock the torque converter which was also mentioned in the UK forum.

I will investigate getting a better code reader - it seems that the IIDTool requires either an iPad (no Android yet) or the flashier D4 screen - mine has the old basic screen.

Thanks again everyone for the help.

Cheers,

Paul

[Silenceisgolden]

Thanks Shane and Gordon - their website was a bit vague on that point, good to know that it will work. Cheaper than driving a 14 hour round trip to the dealer.
Cheers.

[IndusD4]

it seems that the IIDTool requires either an iPad (no Android yet) or the flashier D4 screen - mine has the old basic screen.


The IIDTool also works with steering wheel buttons. Bluetooth versions can use both an app or steering wheel buttons. Also when using an IIDTool the first time it "upgrades" the screen to the 2012 version.

Ron

[Silenceisgolden]

...... when using an IIDTool the first time it "upgrades" the screen to the 2012 version.

Ron

Hmmm, is this a good thing? The 2011 screen looks okay to me....

Could it cause hassles with warranty jobs?

Thanks, Paul

[IndusD4]

It wasn't a problem having the compressor replaced under warranty :)

[Stuart02]

Thanks for the replies. Lpj, yes, I still have 10 months of the extended warranty left, so I might end up getting my moneys worth from it!

Yes Graeme, the VIN is earlier, BA578560. Does this mean I should be getting a software update or something? I didn't see any other warnings on the dash before the message - at both times I was in the Snowy Mountains using the command shift a lot for the downhill sections. I didn't see the message untill I looked for it, after noticing that it was stuck in 3rd.

This also happened when the car was nearly new - again, it was while using command shift for engine braking a lot. Then it also cleared with an engine stop and re-start.

This isn't helpful per se but our 2010 D4 did the same once with about 30000 kms on it, coming down the Blue Mountains using command shift. Turned it off and on and it never happened again before we sold it at 70000 kms. *Shrug*

[Silenceisgolden]

This isn't helpful per se but our 2010 D4 did the same once with about 30000 kms on it, coming down the Blue Mountains using command shift. Turned it off and on and it never happened again before we sold it at 70000 kms. *Shrug*

Actually that is helpful Stuart - my first thought was that it was a simple computer glitch and if the same happened to you that lends support to the theory. I took it to MLR and they found no fault codes logged.