Member Since: 20 Oct 2009
Location: London, UK
Posts: 1318
Intermittend Red suspension light, DTCode C1AO762,solved
[img]Can't seem to get issue resolved on 2006D3 manual, Red susp light after driving a few miles down on stops and message to drive at 30mpg. IIDtool read(not updated to latest SW) 5A07-unknown. The D3 is in SAfrica so remote diagnosis is not easy, it was briefly with Indi for service and check which found nothing. Obviously will need to go back but it's a 90min drive not much fun if drops to its stop and traveling at 30mpg, ignition cycle clears the fault and if you quick enough it's doesn't rise slowly. All ears for suggestions, will tell my Dad to try pulling F26 fuse and see if it doesn't drop to be able to drive to specialist. I not sure if the IIDTOOL is display the fault correctly and that's essentially my question have any one had similiar symptoms and the same faultcode, no air-loss so I'm thinking wheelsensor but that should give relevant DTC?
I only found this in Internet search: http://www.lrrforums.com/showthread.php?21...tops[/img]A few mods... and keeping it all running...Faultmate MSV2
MY09EGR's blanked Thanks Bellautos, BAS
Last edited by D4JWW on 11th Oct 2012 12:19 pm. Edited 1 time in total
5th Oct 2012 4:39 pm
The Transformer
Member Since: 22 Jan 2010
Location: Leicestershire
Posts: 1791
Anything else happen on the dash?
Not the usual silly brake light bulb or brake light switch? dealer spent 3 days running new wires and cleaning speed sensors on our old D3 only to find it was the brake light switch
5th Oct 2012 6:13 pm
D4JWW
Member Since: 20 Oct 2009
Location: London, UK
Posts: 1318
Thanks for the reply Tranformer, don't think it's that simple, I am very familiar with the brake light switch problem seeing I could similiate the fault when I blanked the EGRs on my09(fixed now), might try changing the switch any way and report back.A few mods... and keeping it all running...Faultmate MSV2
MY09EGR's blanked Thanks Bellautos, BAS
5th Oct 2012 8:54 pm
Kingmav66
Member Since: 20 Jul 2010
Location: Gloucestershire
Posts: 1349
Stu & BCC had suspension issues not long back. One was a faulty wheel sensor and the other was a broken cable from the wheel sensor to the ECU.
6th Oct 2012 9:17 am
marco 110
Member Since: 15 Nov 2009
Location: SALLES 33
Posts: 1014
ABS sensor or "speed" sensor !?............. Marco.
-D4 sdv6 HSE 2012 , high beam assist , surround cam, tv , and a lot of nice stuff..
Member Since: 20 Oct 2009
Location: London, UK
Posts: 1318
Cheers Kingmav, sorry Marco that's height sensor, the D3 is not driven much(once a month) which doesnt help but at least dry African climate has to be good for electrics had 39C today! Me thinks it's wire problem on loom near front wheel, but watch this space. Any comment on the fault code read by IIDTOOL???A few mods... and keeping it all running...Faultmate MSV2
MY09EGR's blanked Thanks Bellautos, BAS
6th Oct 2012 7:47 pm
D4JWW
Member Since: 20 Oct 2009
Location: London, UK
Posts: 1318
Update:
No parts changed, went to the local LR dealer(against my recommendation, parents one can't tell them anything), who just calibrated susp height Will wait for the report on test drive before I accept it's fixed!
Test drive, no faults, DTC logged by dealer before height calibration: C1A0762=cross articulation, U0421, U0132.
I asked that software be cheched(especially rear diff, gave them the TSB) replied its not necessary Client request obviously ignored. Land Rover Dealer in Potchefstroom,South Africa don't get my vote!A few mods... and keeping it all running...Faultmate MSV2
MY09EGR's blanked Thanks Bellautos, BAS
10th Oct 2012 1:40 pm
PatGAPInnov Site Sponsor
Member Since: 02 Dec 2011
Location: Montreal
Posts: 745
Hi Guys
5A07 = C1A07 which is the cross articulation error. This definition has been added on firmware V2.17 and up of the IIDTool. Generally, this error is caused by a bad calibration or a defective/intermittent sensor. The live values function will help diagnose the issue if it ever comes back.
“Will wait for the report on test drive before I accept its fixed!†Keep us posted on the developments!
Cheers!
11th Oct 2012 5:02 pm
D4JWW
Member Since: 20 Oct 2009
Location: London, UK
Posts: 1318
PatGAPInnov wrote:
Hi Guys
5A07 = C1A07 which is the cross articulation error. This definition has been added on firmware V2.17 and up of the IIDTool. Generally, this error is caused by a bad calibration or a defective/intermittent sensor. The live values function will help diagnose the issue if it ever comes back.
“Will wait for the report on test drive before I accept its fixed!†Keep us posted on the developments!
Cheers!
Thanks for the responce, any suggestion on what's meant by bad calibration? I assume the ecu will keep D3 fairly level even if one calubration value of is out synch with the other corners? This resulting in the above DTCs and the D3 go in sitdown mode?
Definetly updating the IIDtool firmware to V2.17A few mods... and keeping it all running...Faultmate MSV2
MY09EGR's blanked Thanks Bellautos, BAS
11th Oct 2012 5:20 pm
PatGAPInnov Site Sponsor
Member Since: 02 Dec 2011
Location: Montreal
Posts: 745
“Thanks for the responce," My pleasure!
"any suggestion on what's meant by bad calibration?“ First, let’s define what calibration means without getting too technical. The sensors calibration values are what links an actual corner height or measurement to the sensor physical mounting position. It is the reference point for the EAS ECU. A bad calibration may make the vehicle crooked and in extreme cases, it will make the EAS ECU in a fault state.
Here is an actual example of a bad calibration (pay attention to the measured height and current height values):
Front Left Calibration = 146
Front Left Measurement = 467 mm
Front Left Current Height = -14: This means the EAS read from the sensor that the actual height is 14mm below its target, it will therefore try to raise the corner
Target height would be 467 + (– 14) = 453 mm
Front Right Calibration = 128
Front Right Measurement = 485 mm
Front Right Current Height = 19 : Actual height is 19mm higher than target, so left and right target are incompatible, the EAS ecu try to lower FR but FL need to be raised, it finally find a mean between them.
Target height would be 485 + 19 = 504 mm
This is what “Cross Articulation Error†means.
*as seen in the live value function of the IIDTool
Note: The actual calibration values will be different for each vehicle and corners.
“I assume the ecu will keep D3 fairly level even if one calubration value of is out synch with the other corners?†Actually yes, even with a very bad calibration, most of the time the vehicle will be leveled.
Now, this error may also be caused by a bad sensor. The way to verify this is to go in the Live Values function, select the Suspension ECU and View Current Height. When the height is changed from standard to access or to any other modes for that matter, all corners should lower/raise equally and at the same rate.
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