Re: RE: STILL having problems with the Ram

From: Christopher Orr (corr@manual-override.net)
Date: Mon Jun 04 2007 - 14:56:55 EDT


Tom-

I had a similar problem...Not being the mechanic type, I just figured it
was overly-sensitive to the quality of gas I put in...
It usually did it right after I fueled up at a BP with the lowest octane
gas...if I put 90 or 93 in, it would occasionally pop, backfire, chug,
and loose power, but not as bad as the lower octane stuff. Heet would
actually temporarily take care of the problem.

I also thought it might have been a fuel pump or filter issue.

FYI- This was a 2002 Dakota SXT with the 3.9.

-chris

Rick Barnes wrote:
> Tom, I would first suspect that crank sensor...but that is just a guess,
> they sure will act up like that.
>
> Rascal
>
> -----Original Message-----
> From: owner-dakota-truck@bent.twistedbits.net
> [mailto:owner-dakota-truck@bent.twistedbits.net] On Behalf Of Terrible Tom
> Sent: Monday, June 04, 2007 12:01 AM
> To: dakota-truck-moderator@bent.twistedbits.net
> Subject: DML: STILL having problems with the Ram
>
>
> Ok.. I'm really really getting fed up... I'm looking at Crown Vics on
> Autotrader and theres a grey one thats really nice. I'm not beyond
> dumping the Ram... after the problems I am having with it.
>
> For over 2 years now I have been having intermittant problems with the
> Ram's engine. Saturday I changed the cap, rotor, wires, ignition coil,
> and the plugs (went back to stock plug and heat range autolites - I was
> running 3923's)
>
> Today on the way home from work I was treated to a nice misfire session,
> with loss of engine power and backfires.
>
> NOT ONCE over the last 2+ years has it ONCE set a check engine light!
> It can me at the point its running so bad it almost stalls - popping and
> stumbling... but it never once sets a code.
>
> Help me out here people... I'm really getting to my witts end. Just a
> refresher - its a 2001 Ram 360 46Re Auto.
>
> Do I change the crank sensor? Map sensor? Distrib pickup coil? Has the
> ECM flaked out? I wish I had some direction. I don't want to just
> start throwing more parts at it. But with no engine codes - I have no
> idea where to start.
>
> Jon? I remember you hooked up to Adam's Dak when he had problems after
> the 02 BBQ, using your laptop... do you have the ability to monitor
> engine and sensor data while running? Or just pull codes? I know Walt
> had a pretty snazzy set up in his Ram for the Colorado trip - with his
> laptop reading real time data.
>
> I just might end up renting a car for the BBQ - or getting so pissed off
> I'll buy something else.
>
>



This archive was generated by hypermail 2b29 : Sun Jul 01 2007 - 21:47:16 EDT