Quote:
Originally Posted by multihull
I had my transfer case recall done Thursday week ago and now I'm having issues with a warning on the Dash. "Service 4WD system" I've checked my diff and transfer oils and all is OK. I notice today that i can here the transfer case motor shifting when I start to drive forward and I can feel the car do a strange hop as I turn out of my drive. I thought this was the ABS wheel speed sensors but found these all to be OK and it's actually the transfer case trying to lock. Similar to when you go to low range. And the engine is not shifting gears until a far higher rev range. Like its in low range.
I have now check out the feed back on the USA jeepcommander.com forum and there's a hole heap of issues this recall has caused.
http://www.jeepcommander.com/forums/...er+case+recall
Don't get the recall done unless your ready for the problems.
I'm phoning them tomorrow and asking if they can remove the recall flash to my transfer case. If they don't it's off to court. I'm pissed off!
|
Sounds like the same thing as everyone here who's reported the "Service 4wd system" error, except maybe you're just a bit more observant, noticing the actuator running, change in shifting points, etc?
Maybe worth a shot getting your dealer to re-do it properly as-per a few of the other guys posts here.
Buut... with all these issues being reported, I'm starting to think that DC owe everyone an explanation and more detail of the original problem.
From an engineering perspective, it's ticking a lot of boxes for being a sham/hack work-around.
The only thing we've been told is that a software update has been issued to fix "cracking" circuit boards... that's suspicious on a lot of levels.
My guess is that some component(s) in the PCM have been suffering early thermal fatigue at the solder joints, and rather than paying to swap and re-reflow the components, they've updated the firmware to be more intelligent or lenient about interpreting some of the signal(s) it's getting.
That wouldn't necessarily be a bad thing, but it does look like they might've rushed it, or bitten off more than they could chew using only a software update.
Then-again, lots of people have had no problems (once the procedure is followed correctly.)... so maybe it's a red-herring
.
Would be interesting to see stats of how many have had issues.