LR3 Talk about the Land Rover LR3 within.
Sponsored by:
Sponsored by:

Hooray! Suspension fun!

Thread Tools
 
Search this Thread
 
Old Nov 15, 2015 | 01:57 PM
  #11  
houm_wa's Avatar
Camel Trophy
Joined: Apr 2009
Posts: 4,247
Likes: 482
From: North of Seattle
Default

So you have Polybushes, Johnson Rods AND Proud Rhino spacers? Good luck to you...

I think you are going to have a tough time making the EAS happy with that much change to spec. That said, if you are still having trouble calibrating, I'd suggest just contacting the guys at GAP. Their customer support team is great.

Looked like your calibration numbers were okay (they were all between 150 and 250) but I don't know if they were correct with respect to each other. Also, not sure if the PR spacers change where the nominal values should be.
 
Reply
Old Nov 15, 2015 | 03:45 PM
  #12  
TOM R's Avatar
Baja
Joined: Mar 2009
Posts: 5,736
Likes: 230
From: south n.j. and ne va.
Default

Guess you did not read my poly bush threads, they say do not use grease only soap lol, I used marine grease

I am guessing all the sensor wires look good no corrosion in the plugs, saw an lr3 rip off the front sensor wires on one side yesterday
 
Reply
Old Nov 15, 2015 | 05:19 PM
  #13  
Zelatore's Avatar
Thread Starter
|
Rock Crawling
Joined: Oct 2015
Posts: 379
Likes: 44
From: NorCal
Default

Yes, it's a lot of mods though I don't see any reason they should conflict with one another. The Proud Rhino kit is of course offered with or without rods and bushings are, well, bushings.

Correct me if I'm wrong, but the rods and spacers should not change the calibration height numbers I read on the GAP tool. Both the spacers and rods effectively push the strut down in it's stroke but should have no effect on what the computer sees; it has no way to monitor what part of the travel you are using other than the height sensor. I don't see how that would cause my cross axle error. As for the inability to reach normal ride height I can see how the spacers could cause a problem here if they were too big, but again I'm not reaching them unless I manually deflate the corners. When I monitor the height data while lowering from off-road to normal I can see each corner going down at what appears to be the same rate. It's not like one corner stalls out causing the truck to return to extended height.

I suppose if I had a spare set of height sensors laying around I could pop them in and try them, but I'm not keen to throw $400 at the problem with no firm logic behind why.

I could easily be talked out of doing all the bushings though. It may not cost much but it is a PITA to be sure, as some of you recently found out. Last time I did them I had a lift to work on. This time I'm not so lucky.

And besides, I just picked up a new RRC project today so I'm already getting antsy to start playing with it even though I've told myself I won't start that little adventure until next year.
 
Reply
Old Nov 19, 2015 | 06:33 PM
  #14  
Zelatore's Avatar
Thread Starter
|
Rock Crawling
Joined: Oct 2015
Posts: 379
Likes: 44
From: NorCal
Default

Today I took the truck back to stock. No johnson rods, no Proud Rhino kit, just stock, other than the poly bushings which obviously I won't be doing a quick change on.

The plan was to get it back stock and re-establish a base line height calibration and to see if my cross-axle error returns.

But no...I left the RRC within sight of the LR3, so it's still mad at me.

I now have a nifty new error: C1A00-53 (AF) Control module - System programming failure - deactivated

I can clear it but it comes right back. I'm not sure what to make of this one. Anybody have some insight here?

BTW, I mounted the new 33.3" tires. As expected, it will take a little more trimming and if it falls to the bumps it will be immobile, but I think they will work. They'd better - they're bought and paid for!
 
Reply
Old Nov 19, 2015 | 07:32 PM
  #15  
Zelatore's Avatar
Thread Starter
|
Rock Crawling
Joined: Oct 2015
Posts: 379
Likes: 44
From: NorCal
Default

Wait - I think I've got that sorted. I was able to re-activate the EAS with the GAP tool and it looks to be happy for the moment. So tomorrow we'll play with calibrations and making room for the bigger tires.
 
Reply
Old Nov 19, 2015 | 11:14 PM
  #16  
houm_wa's Avatar
Camel Trophy
Joined: Apr 2009
Posts: 4,247
Likes: 482
From: North of Seattle
Default

Don, do yourself a favor and contact the GAP Support guys. They can help you if your EAS faults persist. In developing the IIDTool they have learned everything there is to know about the EAS. Even if it's just a little assistance with a proper calibration; they are solid.
 
Reply
Old Nov 20, 2015 | 12:11 AM
  #17  
Zelatore's Avatar
Thread Starter
|
Rock Crawling
Joined: Oct 2015
Posts: 379
Likes: 44
From: NorCal
Default

I hate to trouble them with something that isn't their problem but I might send them an email anyway. Hopefully tomorrow will be productive. Fingers crossed.
 
Reply
Old Nov 20, 2015 | 10:45 AM
  #18  
houm_wa's Avatar
Camel Trophy
Joined: Apr 2009
Posts: 4,247
Likes: 482
From: North of Seattle
Default

They probably like it! If I was part of a customer support team I'd want new stuff. Up to you if you want to go open kimono and tell them all the mods you've made. The main thing is that you need to ensure a proper calibration. You can tell them your live values and see what they think.
 
Reply
Old Nov 20, 2015 | 12:43 PM
  #19  
Zelatore's Avatar
Thread Starter
|
Rock Crawling
Joined: Oct 2015
Posts: 379
Likes: 44
From: NorCal
Default

Just came back from a test drive with stock rods and no Proud Rhino kit, running the new 33.3" Coopers.

All street testing, various speeds up to 80 mph. No problems to start with so I thought perhaps the issue had been the Proud Rhino stuff. Then about 10 minutes in I got the cross axle error again and dropped to the bumps:

C1A07-62 (AF) Cross articulation - Algorithm based failure - signal compare failure

I was trying to watch my real-time height number to see if I saw an anomaly that would have triggered this but they jump around so much I can't actually watch them. I cleared the fault and it did not return in the 5 minute drive back home.

I am now able to use all the heights, access/normal/off-road without triggering extended mode due to a false obstruction, so that may have been due to the Proud Rhino kit.

FWIW, I checked the numbers when I got back home - hey, I wanted an excuse to use the nifty metric tape measure I amazon'ed...

measured height
GAP reported height
calibration

LF 470mm RF 460mm
6 -18
207 157


LR 485mm RR 490mm
-9 26
207 160

This was in normal tolerance, so not super-accurate.

The thing that stands out to me is the large difference in the GAP reported heights side to side. Front at 6 and -18; rear at -9 and 26, Yet the truck actually sits pretty level and close to the correct factory heights of 466mm front and 485mm rear.

Given the reported 'cross axle' error, I can't help but think these measurements are the root of the problem. I know calibration numbers can be wildly different, but should the reported heights be that much different?
 
Reply
Old Nov 20, 2015 | 12:52 PM
  #20  
Zelatore's Avatar
Thread Starter
|
Rock Crawling
Joined: Oct 2015
Posts: 379
Likes: 44
From: NorCal
Default

And yes, I did just send this same info to GAP. I did not tell them anything about the rods or spacers since I'm not running them at the moment. My thinking is that would only confuse the issue. I'll try to get it sorted with the stock stuff then add in the mods one at a time.

We'll see if they have any helpful input.
 
Reply



All times are GMT -5. The time now is 06:42 AM.