5.2 PING - Tried many common fixes, what is next?

From : scruff

Q: i have a 1999 dakota with the 5.2 it has the classic ping problem. i have tried the following fixes found in this group and various web sites 1. tsb wire reroute 2. napa bras cap and rotor 3. 180 thermostat 4. autolite 3923 plugs 5. msd superconductor wires 6. new mopar pcv valve 7. verified that there is no plenum vaccum leak using the proceedure recommended in the tsb about the same. 8. using high octane gas all have provided some performance enhancements but none have cured the ping. now what is left .

Replies:

From : jim mccarthy

intake manifold gasket is next. common thing -- had to replace it twice on mine in the first 40k miles. argh. i have a 1999 dakota with the 5.2 it has the classic ping problem. i have tried the following fixes found in this group and various web sites 1. tsb wire reroute 2. napa bras cap and rotor 3. 180 thermostat 4. autolite 3923 plugs 5. msd superconductor wires 6. new mopar pcv valve 7. verified that there is no plenum vaccum leak using the proceedure recommended in the tsb about the same. 8. using high octane gas all have provided some performance enhancements but none have cured the ping. now what is left .

From : scruff

maybe i wasnt clear enough on number 7. the subject title on the tsb mentioned is spark knock and engine oil consumption due to intake manifold pan gasket oil leak i performed the test with a vacuum gauge. there is no leak. thanks for giving it some thought though! on sat 1 nov 2003 094730 -0600 jim mccarthy someone@somewhere.com wrote intake manifold gasket is next. common thing -- had to replace it twice on mine in the first 40k miles. argh. i have a 1999 dakota with the 5.2 it has the classic ping problem. i have tried the following fixes found in this group and various web sites 1. tsb wire reroute 2. napa bras cap and rotor 3. 180 thermostat 4. autolite 3923 plugs 5. msd superconductor wires 6. new mopar pcv valve 7. verified that there is no plenum vaccum leak using the proceedure recommended in the tsb about the same. 8. using high octane gas all have provided some performance enhancements but none have cured the ping. now what is left .

From : jr

if its too lean might be o2 sensor. fyi on sat 01 nov 2003 152355 gmt scruff scruff@domain.com wrote i have a 1999 dakota with the 5.2 it has the classic ping problem. i have tried the following fixes found in this group and various web sites 1. tsb wire reroute 2. napa bras cap and rotor 3. 180 thermostat 4. autolite 3923 plugs 5. msd superconductor wires 6. new mopar pcv valve 7. verified that there is no plenum vaccum leak using the proceedure recommended in the tsb about the same. 8. using high octane gas all have provided some performance enhancements but none have cured the ping. now what is left .

From : scruff

any way to test for a defective o2 sensor on sat 01 nov 2003 123213 -0500 jr jr@nospam.com wrote if its too lean might be o2 sensor. fyi on sat 01 nov 2003 152355 gmt scruff scruff@domain.com wrote i have a 1999 dakota with the 5.2 it has the classic ping problem. i have tried the following fixes found in this group and various web sites 1. tsb wire reroute 2. napa bras cap and rotor 3. 180 thermostat 4. autolite 3923 plugs 5. msd superconductor wires 6. new mopar pcv valve 7. verified that there is no plenum vaccum leak using the proceedure recommended in the tsb about the same. 8. using high octane gas all have provided some performance enhancements but none have cured the ping. now what is left .

From : mrdancer

intake manifold gasket is next. common thing -- had to replace it twice on mine in the first 40k miles. argh. jim next time just replace the gasket with rtv not another gasket. this is the fix recommended by mopars tech engineer larry shepard. i did it on my dakota at 50k miles and its still running great at 167k+ miles. to the op looks like your next step is high-octane fuel. the other fix is where the dealer reprograms your fuel curve; apparently it works but youll lose performance. i have a 1999 dakota with the 5.2 it has the classic ping problem. i have tried the following fixes found in this group and various web sites 1. tsb wire reroute 2. napa bras cap and rotor 3. 180 thermostat 4. autolite 3923 plugs 5. msd superconductor wires 6. new mopar pcv valve 7. verified that there is no plenum vaccum leak using the proceedure recommended in the tsb about the same. 8. using high octane gas all have provided some performance enhancements but none have cured the ping. now what is left .

From : redneck tookover hell

yep the engine runs rich not lean any way to test for a defective o2 sensor ill start watching reality tv shows when i can vote people off the planet. .

From : clare snyder on ca

on sat 01 nov 2003 152355 gmt scruff scruff@domain.com wrote i have a 1999 dakota with the 5.2 it has the classic ping problem. i have tried the following fixes found in this group and various web sites 1. tsb wire reroute 2. napa bras cap and rotor 3. 180 thermostat 4. autolite 3923 plugs 5. msd superconductor wires 6. new mopar pcv valve 7. verified that there is no plenum vaccum leak using the proceedure recommended in the tsb about the same. 8. using high octane gas all have provided some performance enhancements but none have cured the ping. now what is left have you checked the egr if egr is not working properly there is nothing you can do to stop the ping. .

From : clare snyder on ca

on sat 01 nov 2003 225120 gmt scruff scruff@domain.com wrote any way to test for a defective o2 sensor put the scanner on it and watch for zero crossing counts. if it is alternating high/low every second or so it is working fine. on sat 01 nov 2003 123213 -0500 jr jr@nospam.com wrote if its too lean might be o2 sensor. fyi on sat 01 nov 2003 152355 gmt scruff scruff@domain.com wrote i have a 1999 dakota with the 5.2 it has the classic ping problem. i have tried the following fixes found in this group and various web sites 1. tsb wire reroute 2. napa bras cap and rotor 3. 180 thermostat 4. autolite 3923 plugs 5. msd superconductor wires 6. new mopar pcv valve 7. verified that there is no plenum vaccum leak using the proceedure recommended in the tsb about the same. 8. using high octane gas all have provided some performance enhancements but none have cured the ping. now what is left .

From : clare snyder on ca

on 01 nov 2003 233647 gmt mopar440@aol.comedy.biz redneck tookover hell wrote yep the engine runs rich not lean any way to test for a defective o2 sensor if the sensor goes bad the check engine light usually comes on and the engine can go either way. a good voltmeter can be used to see if the sensor is switching if a scanner cannot be found. voltage should oscillate between roughly .3 and .8 volts higher and lower than .45 ill start watching reality tv shows when i can vote people off the planet. .

From : scruff

thanks for your replies! can you tell me how to i check the egr on wed 05 nov 2003 002012 gmt clare @ snyder.on .ca wrote on sat 01 nov 2003 152355 gmt scruff scruff@domain.com wrote i have a 1999 dakota with the 5.2 it has the classic ping problem. i have tried the following fixes found in this group and various web sites 1. tsb wire reroute 2. napa bras cap and rotor 3. 180 thermostat 4. autolite 3923 plugs 5. msd superconductor wires 6. new mopar pcv valve 7. verified that there is no plenum vaccum leak using the proceedure recommended in the tsb about the same. 8. using high octane gas all have provided some performance enhancements but none have cured the ping. now what is left have you checked the egr if egr is not working properly there is nothing you can do to stop the ping. .

From : clare snyder on ca

on wed 05 nov 2003 130618 gmt scruff scruff@domain.com wrote thanks for your replies! can you tell me how to i check the egr basically you need a scanner. however if you put a vacuum guage on the line to the egr you should get vacuum at normal cruise and if you apply vacuum at idle the engine should run very rough and stall. if either of these do not happen you need to look farther. on wed 05 nov 2003 002012 gmt clare @ snyder.on .ca wrote on sat 01 nov 2003 152355 gmt scruff scruff@domain.com wrote i have a 1999 dakota with the 5.2 it has the classic ping problem. i have tried the following fixes found in this group and various web sites 1. tsb wire reroute 2. napa bras cap and rotor 3. 180 thermostat 4. autolite 3923 plugs 5. msd superconductor wires 6. new mopar pcv valve 7. verified that there is no plenum vaccum leak using the proceedure recommended in the tsb about the same. 8. using high octane gas all have provided some performance enhancements but none have cured the ping. now what is left have you checked the egr if egr is not working properly there is nothing you can do to stop the ping. .

From : weisserer

think you got problems now wait till you get the ford!!! yeh you re right maybe i will get the toyota tundra v8.. my old yoda in college never failed me and i beat the hell out of it.. real off road adventures.. only downfall of that truck were the spot welds rusting on the bed.. .

From : frankie

and the japanese thing. think you got problems now wait till you get the ford!!! yeh you re right maybe i will get the toyota tundra v8.. my old yoda in college never failed me and i beat the hell out of it.. real off road adventures.. only downfall of that truck were the spot welds rusting on the bed.. .

From : frankie

think you got problems now wait till you get the ford!!! trade it in on a ford.. that is my plan next year with my dakota!! my ping was intake plenum.. at 20k then at 43 k miles.. at 66 k now it was pinging on 87 octane when going up hills switched to 89octane and all is quiet.. sad thing it at 13mpg this 5.2 should not be able to taste what it is burning.. .

From : budd cochranfrankie

looking good mac but does it have a trebuchet mount -- budd cochran in tribute to the united states of america and the state of israel two bastions of strength in a world filled with strife and terrorism. ------ --- outgoing mail is certified virus free by avg and norton checked by avg anti-virus system http//www.grisoft.com. version 6.0.537 / virus database 332 - release date 11/6/2003 .