2nd Gen Dakota Tech 1997 - 2004 Dodge Dakota Tech - The ultimate forum for technical help on the 2nd Gen Dakota.

The unusual Rattle noise

Thread Tools
 
Search this Thread
 
Old Jun 27, 2020 | 01:02 AM
  #21  
Vimes's Avatar
Vimes
Veteran
5 Year Member
Photogenic
Liked
Loved
Joined: Oct 2018
Posts: 451
Likes: 64
From: Midwest
Default

You might try unplugging the front O2 sensor, or both if you have two, and see how it runs. It will set a code, but it should also run off a set fuel/air mix table. Lean fuel can cause spark knock, but the set tables should lean towards rich since it can't detect what the mix is. If it clears, you may need to replace the O2 sensors. They can go lazy/bad without setting a code.

I'd also think about placing a call to the folks that flashed your computer and discuss it with them. Find out if they did any performance tuning that you weren't aware of. You may NEED 91/93 octane in it if they pushed the timing forward, and you'll also want to find out if they tuned it to run on a 180 thermostat. If they tuned it for 91/93 and a 180, and you're running 87 and a 195, knock city.

On the seafoam treatment, getting it to stall by pouring it in faster than it can take it then letting it sit is part of the treatment. You let it sit about 15 minutes, and the superheated seafoam cleans the top of the pistons as it evaporates off. So, you might give it another try as was suggested, only this time make sure it stalls on the last third of the bottle.

The only other thing I can think is knock sensors, different engines are tuned for different knock detection. If you used the 3.9L knock sensors they may not be able to work with the 5.9L engine, so your computer doesn't know it's knocking. This one may be off-base as the 3.9L sensors may not even screw into a 5.9L.
 
Reply
Old Jun 27, 2020 | 10:32 AM
  #22  
Aaron H's Avatar
Aaron H
Thread Starter
|
Rookie
Joined: Feb 2019
Posts: 80
Likes: 1
Default

Originally Posted by Vimes
You might try unplugging the front O2 sensor, or both if you have two, and see how it runs. It will set a code, but it should also run off a set fuel/air mix table. Lean fuel can cause spark knock, but the set tables should lean towards rich since it can't detect what the mix is. If it clears, you may need to replace the O2 sensors. They can go lazy/bad without setting a code.

I'd also think about placing a call to the folks that flashed your computer and discuss it with them. Find out if they did any performance tuning that you weren't aware of. You may NEED 91/93 octane in it if they pushed the timing forward, and you'll also want to find out if they tuned it to run on a 180 thermostat. If they tuned it for 91/93 and a 180, and you're running 87 and a 195, knock city.

On the seafoam treatment, getting it to stall by pouring it in faster than it can take it then letting it sit is part of the treatment. You let it sit about 15 minutes, and the superheated seafoam cleans the top of the pistons as it evaporates off. So, you might give it another try as was suggested, only this time make sure it stalls on the last third of the bottle.

The only other thing I can think is knock sensors, different engines are tuned for different knock detection. If you used the 3.9L knock sensors they may not be able to work with the 5.9L engine, so your computer doesn't know it's knocking. This one may be off-base as the 3.9L sensors may not even screw into a 5.9L.
I contacted b&g chrysler about it he said he’d look over the tune. What i did yesterday was file the crank sensor so it had a bit of play, and i retarded the timing with that. No more spark knock now. Now i don’t know what this means power wise if i’m losing some or what not. Also with the seafoam treatment thing, the engine has less than 2k on it everything is new. I also have a cam in it. I don’t thing my 03 dakota 5.9 has any knock sensors unfortunately. Thanks for the reply and if you suggest anything i’m willing to try
 
Reply




All times are GMT -4. The time now is 02:31 PM.