Total loss of power driving down highway
Registered User
Joined: Jul 2015
Posts: 1
Likes: 0
From: Virginia
All culprits I can think of have been replaced. Fuel pump, no change. Cam sensor, no change. Crank sensor, no change. Pcm, no change. Tps sensor, no change. Plugs, wires, cap, rotor, and Catalytic converter, no change. Unplugged O2 and, no change. According to the ASE master mechanic that scanned my truck everything is working like it should other than it is running a little lean. But O2 is cycling like it should to try and compensate. I thought that maybe the ignition coil was getting hot and may not be producing a hot enough spark. The only code that sets is a random misfire when truck acts up. Mechanic seems to think that maybe a fuel injector is failing when under load.
Registered User
Joined: Jul 2015
Posts: 20
Likes: 0
I replaced the crank sensor again with a new warranty one and so far so good. I haven't gotten on the freeway yet but as far as driving in town at 35 mph or less, all is good. Have a friend that works for dodge and he said that the crank sensor needs to be mopar. that it won't accept a crank sensor from aftermarket. So if this one fails I will test his theory.
Registered User
Joined: Jul 2015
Posts: 20
Likes: 0
Ok crank sensor replacement didn't fix it. Same problem exists. No change other than problem is becoming more frequent. Starting to lean towards bad injector or injectors. The only code that sets is random misfire code. When spark plugs were changed #7, #8, #6 were all wet with fuel.
Registered User
Joined: Jul 2015
Posts: 20
Likes: 0
Pulled injector replaced 6 out of 8 and no change. Replaced crank sensor with one from the dealer and no change. Cleaned entire fuel system and throttle body, and still no change. Runs great for a short period, and then sputters and loses all power. Doesn't die. Just starts sputtering and missing.
Administrator
Joined: Apr 2010
Posts: 87,467
Likes: 4,220
From: Clayton MI
Does it do the same thing with the O2 sensors unplugged? (I seem to recall you tried this, and it didn't help either.....)
What you really need, is to be able to do data logging. Plug in, go for a drive, note at what elapsed time it starts to fail, drive home, look at the logs. It *should* be patently obvious at that point, what the issue is.
What you really need, is to be able to do data logging. Plug in, go for a drive, note at what elapsed time it starts to fail, drive home, look at the logs. It *should* be patently obvious at that point, what the issue is.