Transmission Fault message

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...y-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'

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

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

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

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

Quote:

---

Originally Posted by 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

---

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.

Quote:

---

Originally Posted by Silenceisgolden

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

Quote:

---

Originally Posted by IndusD4

...... 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

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

Quote:

---

Originally Posted by 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.

---

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*

Quote:

---

Originally Posted by Stuart02

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.