Printable View
SeanC I've just recently ordered a gap tool for outback trips and was wondering if you or anyone knows where I can find a list of fault codes and what they mean (what action is needed) for a disco 4 that I can print out and leave in the vehicle. That way when I have no internet access the gap tool can still be useful.
As you previously mentioned I would normally do the same and Google the code to get assistance but in the Bush we get slightly stranded when technology is used.
With the IIDTool you get a description of the code as well so no need to print anything out. How the code and description is interpreted can be trickier though.... being a CANBUS system sometimes the codes are just the starting point but the actual fault may be something else.
I bought the manuals from this website and saved them onto my tablet which lives in the car..I use the search function on it to bring up what I need. Whether it be codes or wiring diagrams etc. Great way not to be without help
I use the same tablet to talk to the gap tool 90% of the time. I find the Android system works better then the Apple system on my phone.
Interpreting fault codes is the real challenge. There are hundreds of signals that can trigger thousands of fault codes programmed across dozens of ECU’s and many are triggered by each other - think of the CAN system as a Social Media Platform.
The JLR SDD (Symptom Driven Diagnostics) software used by LR technicians recognise this issue and attempts to combine known issues with symptoms and fault codes to make recommendations - and even then it sounds like it is hit and miss.
Normally for diagnostics you want to make sure no codes have been cleared - but once you believe everything is working as expected, I believe it is good to clear all logged faults.
I now regularly check mine for new fault codes to try and identify any early warning signs and hopefully to help me recognise when something more important does happen.
Couldn't agree more, and the only thing worse than not having the tool to do the job is having the perfect piece of kit and not knowing how to use it, it really is worth a few hours on a rainy day to get up to speed on it, I think you will be pleased with the capability. It can be a bit tricky when fault codes pop up interpreting the root cause but that's what the knowledge base (and lots of helpful people) on this forum is fantastic for.Quote:
Originally Posted by Tombie
It would be great to find out what your fault codes were (are) and what you eventually find is the problem, I hope not to serious.$$$
Interestingly I have been reading up on the SDD software used by JLR. Even something as benign as the different combination and sequencing of warning lamps and messages can make a big difference in interpreting the actual fault.Quote:
Originally Posted by PeterJ
The training manual stresses you must take note of every symptom the owner reports - something many technicians don’t always listen to.
I would love to be able to read the programming code in all of the ECU’s. I suspect it is a real mess with multiple ECU’s acting and triggering conflicting signals at the same time.
I read somewhere that the D3/D4 has some 4000 fault codes - but as any processing plant control room operator knows - having excessive warnings and alerts does not help spot a real issue when it comes up. Personally, I would have preferred it to have no faults. [emoji48]
Nailed it!Quote:
Originally Posted by DiscoDB
I upgraded the firmware today and the GAP tool is back up and working properly.
Thanks!
How good is the GAP tool hey - brilliant. [emoji106]Quote:
Originally Posted by Barraman
It's good to see we have closed the GAP on this one. A good outcome Merry Christmas. NickQuote:
Originally Posted by DiscoDB