What Tests Can I Perform To Find The Cause Of The Misfire Condition?
Now that you have an idea of what are some of the causes of a misfire condition... you might be asking yourself, ‘Where should I start?’.
In this section, I'm gonna' offer you a simple diagnostic strategy that should help you find and resolve the root cause of the misfire or ‘dead’ cylinder on your 2.0L or 2.4L Chrysler.
STEP 1: Identify the dead cylinder. This usually entails connecting your scan tool to your vehicle and reading the misfire diagnostic trouble codes. Then by matching the misfire code to its engine cylinder using an illustration of the engine cylinders.
In many cases, the PCM does not give you any misfire codes, even though the engine is suffering a bona fide misfire. In these cases, you'll need to do a manual cylinder balance test by unplugging one injector at a time (to see which one has NO effect on the engine's idle).
The fuel injector that does not worsen the engine's idle when unplugged... tells you that that specific cylinder is ‘dead’.
STEP 2: Test the ignition system . Since the majority of misfires are caused by a failed component in the ignition system, it's important to make sure that the misfiring cylinder is getting spark. You should:
- Perform a spark test (using a dedicated spark tester) on the spark plug wire of the cylinder that the misfire code is accusing of being dead.
- Testing for spark with a spark tester is the most important first test since you'll know right away if the misfire is due to a lack of spark.
- Check to see if the spark plug boots and spark plugs are swimming in engine oil from a leaking valve cover gasket.
- If you got spark from your spark tester (from the cylinder the misfire code is accusing of misfiring), the next step is to remove the spark plug or spark plugs (of the affected cylinders) and check them for wear and tear, carbon tracks, anti-freeze, etc.
- If you get no spark, then the next step is to check for spark directly on the ignition coil pack tower.
- You can find all of these ignition system tests here:
- How To Test The Coil Pack (Chrysler 2.0L, 2.4L) (at: easyautodiagnotics.com).
- Carbon Tracks Are A Common Cause Of Ignition Misfires (at: easyautodiagnotics.com).
STEP 3: Test the fuel injectors. If the ignition system is not the cause of the misfire, then the next step is to check the fuel injectors.
You'll need to:
- Resistance test each of the 4 fuel injectors.
- Do a Noid light test of each one to make sure the PCM is pulsing them (activating them).
- You can find the fuel injector tests here:
STEP 4: Test the compression of each engine cylinder. Other tests that should be done, if the ignition system and fuel injectors check out OK are:
- Engine compression test.
- Checking for vacuum leaks.
- You can find the engine compression test here:
The above list of steps may seem/sound like troubleshooting a Misfire is a complicated thing but it really isn't. Depending on your level of ‘wrenching’ experience, this is something that you can accomplish without taking it to the shop.
What Tools Do I Need To Test The Misfire Code(s)?
Finding the exact cause of the misfire codes or misfire condition is possible... with the proper tools. Without them, you won't be able to diagnose /troubleshoot those issues on your 2.0L or 2.4L Chrysler car or mini-van.
Depending on what the root cause of the misfire is, you may need several tools. Most of these you can buy online, none of these will break the bank and I'll make some recommendations on them. Here's a guide to some of the basic tools that can be and are used:
- Ignition System Tests:
- Spark Tester.
- Test Light.
- Fuel System Tests:
- Noid Light.
- Fuel Pressure Gauge.
- Engine Mechanical Tests:
- Compression Tester.
Now of course, you'll also need basic hand tools like: screw-drivers, ratchet wrenches, sockets, etc. You'll also need a generic scan tool to retrieve the Diagnostic Trouble Codes (DTCs) from the Computer's memory.
Keep in mind that using the right tool for the job will save you time, frustration, and /or keep you from damaging the component that you're testing.