Perhaps make a note of them (If you press the enter button it should give the time of the error) and then clear them - have a look in a week/2/3/4 what ever and see what has re-appeared.Mark.
2006, D3 SE Auto - gone but not forgotten.
2014 BMW 530d M Sport Tourer.
1977 Triumph Spitfire 1500
_________________________________________________
Disco Picture Website Here
9th Feb 2013 5:48 pm
Disco_Mikey
Member Since: 29 May 2007
Location: Dundee, Scotland
Posts: 20836
Dont get too hung up on fault codes. Only worry about them if their is actually an issue My D3 Build Thread
Can't do that with an IID tool as it works standalone from a PC.Mark.
2006, D3 SE Auto - gone but not forgotten.
2014 BMW 530d M Sport Tourer.
1977 Triumph Spitfire 1500
_________________________________________________
Disco Picture Website Here
9th Feb 2013 10:18 pm
BBS SPY Site Sponsor
Member Since: 15 Jun 2007
Location: Sunny Cyprus
Posts: 3054
Ah, that's not good. Being able to keep copies of previously read fault codes is actually a very important part of using the fault code feature.
I will try to explain why.
As Klaus7269 has noted, because CAN BUS based vehicles like the Disco 3/4 are so complex, with so many interdependent ECU's, even if there are no real faults on a vehicle, the various ECU's still pick up some faults that they store codes for due to re occurring anomalies in the vehicles systems and wiring.
Some fault codes are the same on all vehicles, like this pick up coil thing in the Body control, and are just design left overs,
Some fault codes are quite common on all vehicles, like occasionally missing Bus messages, which are likely due to wiring loom differences and although common and most vehicles have some, which ECU's are affected and how often, can vary from vehicle to vehicle.
Some others are just unique per vehicle oddities, maybe some ECU's might occasionally throw a wobbly, possibly a flash issue or you may have a sensor somewhere that occasionally disappears for a microsecond or two, enough to trigger a fault but not enough to cause any real day to day vehicle usage problem.
For example, the Crash sensor in the drivers door may disappear once a week for a few micro seconds.
Causing the Airbag ECU to regularly log this as a fault code, with the intermittent tag flagged up.
As the owner of the vehicle, and after clearing the fault codes many times, you get to learn what is normal for your vehicle and appreciate what is normal for it.
Supposing that your Passenger door crash sensor or wiring starts to go faulty, but it is more serious with the sensor disappearing for days at a time. So bad that it puts on the Airbag warning light.
As an owner of the vehicle that is conversant with what is normal for your vehicle, when you read the fault codes you will see that there is a new one for the Passenger door sensor that was not there before and so will know which door sensor and wiring to concentrate your time and effort on.
If you did not have this information and simply relied on a dealer or Indie, then he would read the codes, see fault codes for both doors and possibly waste time, effort and your money on chasing down the wrong fault and looking in the wrong place.
Being able to build a library of what is normal for any vehicle, be it Fault codes, Live data parameters and even settings is a very real and useful asset in figuring out what is different and wrong on that vehicle when it develops a problem.
Klaus7269
Even if it involves writing it down, or using a camera to to keep a record of the Fault codes you have before clearing them, it is still worth the effort.
10th Feb 2013 4:04 pm
J@mes
Member Since: 10 Nov 2008
Location: Bomber County
Posts: 4547
anglefire wrote:
Can't do that with an IID tool as it works standalone from a PC.
Can't believe you bit at that Mark, was quite obviously a loaded statement! 2014 D4 XS
2005 D3 SE - Gone
10th Feb 2013 4:30 pm
Robbie
Member Since: 05 Feb 2006
Location: ¯\_(ツ)_/¯
Posts: 17932
BBS SPY wrote:
Save the current list of faults to a file on your PC, then clear them and see what comes back.
Colin, you can be more subtle than that!
Land Rover - Turning Drivers into Mechanics Since 1948
Member Since: 15 Jun 2007
Location: Sunny Cyprus
Posts: 3054
I do not deny that it was indeed a Loaded question and that i already knew the some equipment has no Fault code list saving ability, and i apologize if that in providing my reply may have seemed un subtle.
But the reality is that most class all Diagnostic equipment as equally capable and judge it solely on cost which is simply not the case.
You may not agree with my process in highlighting this particular difference, but the reality is my point is still absolutely correct and having the ability to save codes before clearing them is a very worthwhile and helpful function.
I did point out that you can just jot them down or take pictures of them.
Last edited by BBS SPY on 11th Feb 2013 5:56 pm. Edited 1 time in total
10th Feb 2013 5:00 pm
mrszymon
Member Since: 17 Apr 2012
Location: London
Posts: 425
The BBS marketing machine shoots to the fore again.
Clearly the "competition" is doing very well, seeing as the vast majority of BBS marketing recently is badmouthing other products
10th Feb 2013 5:18 pm
SteveMfr Site Sponsor
Member Since: 11 Jan 2011
Location: Strasbourg
Posts: 200
Actually the IIDTool can and does save fault codes - though we do not do this on all IIDTools yet. Numerous beta users have noticed the new "Scan and Filter" function in FW v2.18. This new function (also) logs all faults in IIDTool memory. These logs can then be read by the IIDTool Updater and displayed in a browser. We've done this primarily to help users share their faults and find solutions more easily.
We are working on a couple of items that may surprise some people... All in due time.
As for logging in general: it's certainly a good idea to log the faults from time to time.
This can become very useful when a real problem occurs, but general good practice could be to;
- Clear faults upon purchase of a diagnostic tool because having faults logged from a very long time ago can lead to searching for problems that don't exist. This can be especially important if you have not owned your car since new as not knowing all history can sometimes lead to problems: e.g. faults can be logged during a repair (air bag disconnected, for example) and stay there until cleared.
- Check for faults regularly (days, weeks - this is very easy to do with an ultra-portable diagnostic tool... ) knowing there were no repairs or a low battery condition during this period.
- Investigate hard faults.
And some general info to understand DTC's (Diagnostic Trouble Codes or more commonly, faults):
LR has ECU's on CAN network (RRS,LR3,LR4,L322 2010+ are CAN only, L322 2002-2004 No CAN and L322 2005-2009 has CAN and other buses). In this system, hard faults are local to an ECU and have a prefix of P, C or B ;
P = Powertrain, C= Chassis, B = Body
Prefix U are network faults. These can occur without any real problem.
They do have a purpose but it generally does not make sense to start investigating with a U fault only; it does make sense if you have a hard fault or a problem with the vehicle.
When no warning lights are on, you rarely have serious problem to resolve.
I will say this too: I've said before that I really respect Colin and what he has done with his company. If you read the statistics on how many start-ups go belly up, bringing a company to fruition is a feat to be applauded - especially in the tech sector where success is even more rare.
By the same token, being noticed by one of the industry leaders (and having a new product launched due to the competition you are presenting) as an upstart is one of the better things that can happen to a young venture.
Colin, should we say 'thanks' for the kudos? www.gap-diagnostic.com
12th Feb 2013 2:12 pm
jobster
Member Since: 08 Jul 2012
Location: Hilversum
Posts: 591
don't get to friendly. We as simple (potential) customers will only benefit of great features for a good price if you both are willing to cut each other's throat (so to speak) ......... 8)
Oh, and willing to sign up for Beta testing on IIDTool.RLD Sump Guard
GVIF & rear camera
New FBH via Dan
BAS Remap with IIDTool
12th Feb 2013 3:18 pm
BBS SPY Site Sponsor
Member Since: 15 Jun 2007
Location: Sunny Cyprus
Posts: 3054
Hiya Steve
Quote:
Actually the IIDTool can and does save fault codes - though we do not do this on all IIDTools yet.
That's really good news chap. It might not seem like a big thing but as i detailed, its really kinda useful to have and as such clearly you already appreciate its worth.
I look forward to hearing about the surprises
Thank you for your kind comments, As you appreciate it has not been easy, and i remember the days that there was no equipment / capability at all beyond what a dealer had and when no one here had even heard of the CCF, let alone the ability to edit it at will.
Now there is a choice of very capable equipment, all beyond dealer equipment and clearly you also deserve due respect for having bought the IID development along so very much in such a short time. I am sure this was also not easy and has been hard work.
Certainly you have risen well beyond beginner level in our eyes, and you deserve all due Kudos. As you know i have expressed deep gratitude to you for giving me very good reason to crack the whip on my guys to do better faster, and i am kinda hoping and figuring the same may be true for you.
It's certainly going to be an interesting future for LR diagnostics
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
