Have him look for a "pickup coil".

 

SWITCH, Distributor Pick-Up 56028143 that is a Mopar part number.

 

Just my luck ,P.I.T.A. to replace and it didn't fix the problem. It runs great then suddenly decides not to. Shut it off for a couple minits and goes back to running fine. Distributor pick up switch next ?

 

Any chance it could just be the ign. coil ?

 

Find out what's missing when it quits. Fuel, or spark, or both. Take it from there.

 

When I bought this truck the kid said he tuned it up a couple months ago so I figured that much was already done so no need to look there. The ck eng light ended up being the trans output speed sensor but the truck was still doing the same thing just no light. I pulled the dist cap and it looked new but the rotor button metal flap thing was bent to one side and the contact in the cap was burnt with melted plastic all around it so Im thinkin this must be the problem and replaced it, still same problem. So I checked the plugs , all 4 on DS good , pass side all 4 had no gap obviously had been dropped but installed without checking , so Im thinking this has to be the problem... nope. Dropped the gas tank , no water or trash in fuel. The whole time Ive been doing this Ive kept the gas level low so I limped to the gas station put in 7 gallons and it ran its a. off till it got below 1/4 tank . I think Im gonna change the fuel pump . Sounds rational right ?

 

A fuel pressure test would need to be done to verify that fuel pressure is the problem.

Tester can be rented for $100 (as Matt said in the other thread), you get all of that back once you return it.

 

A lesson I was taught a few years back (and have now experienced a couple times), is: When the module doesn't know there is a problem, the module IS the problem.

Basically, If the engine runs so poor that it shuts down randomly, and the computer doesn't think there is a big enough problem to log a fault code, the computer isn't doing its job.

The ECM will have a fuel and timing map to run from. It uses several inputs from sensors, reads the data, then decides what type of output it wants to give to make the engine run the way its map wants. Once it has given an output, its looking at all the input sensors again to verify the output was executed correctly. Normally, If the engine doesn't run the way it should, its because an incorrect input signal was given to the module, which confused it and made it give the wrong output, or an output driver isnt doing the job which the module asked it to do. Either way, The module will know SOMETHING is wrong. That doesn't necessarily mean that the fault code logged will always be exactly where the problem is, it just means that the MIL will illuminate and you will have a base to start troubleshooting from.

In the instance that the engine is not running within its limitation (ie. stalling at a certain speed), and no fault is logged, the module doesn't know whats going on and is most likely the source of the communication breakdown.

 

Thanks for all the advice guys . Looks like the fuel pump fixed it.