Survey- For those with misfire issues

[Idlethunder]

My 22 Gladiator Rubicon with build date of 1 – 22 had the check engine light come on as soon as I pulled out of the driveway 2 days ago. I stopped in at my dealer that afternoon and they said the code showed misfires on cylinder 4. They cleared the code and made an appointment to bring it back this coming Friday to have it checked out and do the PCM update.



After having it for several months and 5,900 miles, I have not noticed anything odd with the way the engine runs or idles. The only mods I’ve made has been to add the longer front LCAs from the Mopar 2” lift kit, K&N engine air filter, Redarc brake controller, and upgraded lights.



I do have Jscan, and a Vgate iCar Pro with bypass cable for when I lift and go to bigger tires but hadn’t hooked it up because so far, the 33s work well for everywhere I’ve been. After the CEL and my dealer visit, I plugged in the vgate and bought a Jscan license. My plan was to drive it with the Vgate adapter connected to see how many misfires come up. The first time I used Jscan, the truck had sat overnight for about 14 hours and within a minute of leaving the house it showed 48 misfires on cylinder 4 and 1 to 2 on the others. I drove 4 miles to work, approx. 6 minutes, and when I got to the office, cylinder 4 showed a total of 52 and the others were all between 1 and 3. I waited 20 minutes and drove another 20 miles and all 6 cylinders showed less then 5 misfires. Since then, I have done this several times and misfires are a lot more frequent the longer the Jeep has been sitting. First thing this morning I drove about 8 miles to the store and back. Cylinder 4 showed 95 misfires with most of them happening withing the first couple of minutes after startup, the other 5 cylinders showed less than 4 misfires each. I have not had the check engine light come back on since the dealer cleared it 2 days and 120 miles ago.



The Gladiator goes to the dealer this Friday morning and I will update when I have more information. I am hoping this is an easy fix but after reading thru all the problems people have had, I am worried.

Sponsored

 

[TheLunk]

Very similar to my issue. Time to start comparing build dates??

My build date for my 22 overland was 12-09-21.

PS- the new engine should be delivered by Wednesday or Thursday.

Door panel shows a build date of 3-22 for me...

fwiw - I haven't caught another light this week...

 

[ShadowsPapa]

My 22 Gladiator Rubicon with build date of 1 – 22 had the check engine light come on as soon as I pulled out of the driveway 2 days ago. I stopped in at my dealer that afternoon and they said the code showed misfires on cylinder 4. They cleared the code and made an appointment to bring it back this coming Friday to have it checked out and do the PCM update.



After having it for several months and 5,900 miles, I have not noticed anything odd with the way the engine runs or idles. The only mods I’ve made has been to add the longer front LCAs from the Mopar 2” lift kit, K&N engine air filter, Redarc brake controller, and upgraded lights.



I do have Jscan, and a Vgate iCar Pro with bypass cable for when I lift and go to bigger tires but hadn’t hooked it up because so far, the 33s work well for everywhere I’ve been. After the CEL and my dealer visit, I plugged in the vgate and bought a Jscan license. My plan was to drive it with the Vgate adapter connected to see how many misfires come up. The first time I used Jscan, the truck had sat overnight for about 14 hours and within a minute of leaving the house it showed 48 misfires on cylinder 4 and 1 to 2 on the others. I drove 4 miles to work, approx. 6 minutes, and when I got to the office, cylinder 4 showed a total of 52 and the others were all between 1 and 3. I waited 20 minutes and drove another 20 miles and all 6 cylinders showed less then 5 misfires. Since then, I have done this several times and misfires are a lot more frequent the longer the Jeep has been sitting. First thing this morning I drove about 8 miles to the store and back. Cylinder 4 showed 95 misfires with most of them happening withing the first couple of minutes after startup, the other 5 cylinders showed less than 4 misfires each. I have not had the check engine light come back on since the dealer cleared it 2 days and 120 miles ago.



The Gladiator goes to the dealer this Friday morning and I will update when I have more information. I am hoping this is an easy fix but after reading thru all the problems people have had, I am worried.

I'd put back in a good air filter before they work on it.



Last evening, started and drove 6 blocks - all but 2 or 3 of these were in the first minutes. Once I hit the highway very few added misfire (I'm wondering if it's an open loop vs. closed loop thing on mine)

2 is ALWAYS the worst, 4 is usually next but usually a lot lower than 2, then 6.
Mine is definitely a left bank, even cylinders thing. No doubt the pattern. Every single time I've watched for misfires or caught it in the act, it was left bank, #2 the worst in every case.

No CEL, no dinging, no misfires I could FEEL last night anyway.
I am on a new tank of fuel as of last week so we'll see.
Hope to drive it 6 hours to Kenosha on Thursday - hopefully I'll be driving it back on Saturday night LOL.

 

[Hootbro]

My 22 Gladiator Rubicon with build date of 1 – 22 had the check engine light come on as soon as I pulled out of the driveway 2 days ago. I stopped in at my dealer that afternoon and they said the code showed misfires on cylinder 4. They cleared the code and made an appointment to bring it back this coming Friday to have it checked out and do the PCM update.



After having it for several months and 5,900 miles, I have not noticed anything odd with the way the engine runs or idles. The only mods I’ve made has been to add the longer front LCAs from the Mopar 2” lift kit, K&N engine air filter, Redarc brake controller, and upgraded lights.



I do have Jscan, and a Vgate iCar Pro with bypass cable for when I lift and go to bigger tires but hadn’t hooked it up because so far, the 33s work well for everywhere I’ve been. After the CEL and my dealer visit, I plugged in the vgate and bought a Jscan license. My plan was to drive it with the Vgate adapter connected to see how many misfires come up. The first time I used Jscan, the truck had sat overnight for about 14 hours and within a minute of leaving the house it showed 48 misfires on cylinder 4 and 1 to 2 on the others. I drove 4 miles to work, approx. 6 minutes, and when I got to the office, cylinder 4 showed a total of 52 and the others were all between 1 and 3. I waited 20 minutes and drove another 20 miles and all 6 cylinders showed less then 5 misfires. Since then, I have done this several times and misfires are a lot more frequent the longer the Jeep has been sitting. First thing this morning I drove about 8 miles to the store and back. Cylinder 4 showed 95 misfires with most of them happening withing the first couple of minutes after startup, the other 5 cylinders showed less than 4 misfires each. I have not had the check engine light come back on since the dealer cleared it 2 days and 120 miles ago.



The Gladiator goes to the dealer this Friday morning and I will update when I have more information. I am hoping this is an easy fix but after reading thru all the problems people have had, I am worried.

Do you live monitor the misfire counters in real time with Jscan at startup? Your situation is very similar to what I had with my 2020 Gladiator on cylinder #4. 90% of my #4 cylinder misfire counts were within the first 30 seconds after start and then level out with a few ticks on the count on my 30 mile commute.

I did spark plug replacement, coil position swap and even checked for coolant leakage into cylinder #4 with nothing detected and problem remained. I traded it off.

I would be interest if the dealership finds anything on yours. Before I traded, I briefly started a log when my ESS disable light would post and monitor the misfire count. I would get a pending P0300 code but it would never post.

 

[ShadowsPapa]

I really wish AlfaOBD would hurry up and update to support 2022 models. I'd love to capture much better data. JSCAN leaves so much out.
Here we are about to hit the 2023 model year as far as production and they've not supported 2022 yet.

I did freeze frames with AlfaOBD on our other Jeeps and it showed a lot more detail.
JSCAN logs are so incomplete but then it's not aimed at this sort of thing anyway.

 

[Idlethunder]

I'd put back in a good air filter before they work on it.



Last evening, started and drove 6 blocks - all but 2 or 3 of these were in the first minutes. Once I hit the highway very few added misfire (I'm wondering if it's an open loop vs. closed loop thing on mine)

2 is ALWAYS the worst, 4 is usually next but usually a lot lower than 2, then 6.
Mine is definitely a left bank, even cylinders thing. No doubt the pattern. Every single time I've watched for misfires or caught it in the act, it was left bank, #2 the worst in every case.

No CEL, no dinging, no misfires I could FEEL last night anyway.
I am on a new tank of fuel as of last week so we'll see.
Hope to drive it 6 hours to Kenosha on Thursday - hopefully I'll be driving it back on Saturday night LOL.

Thank you for bringing it up to change out the air filter. I thought about it last night but completely forgot to do it. The OEM filter is back in now.



Before changing the filter, I wanted to get a before and after scan. The truck had sat for about an hour and the first picture shows the 2 minute drive from the house to the paved road. This time it showed 12 on cylinder 2, 30 on cylinder 4, and 1 on each of the others. From there I came home and had 1 more on cylinder 3 but the others stayed the same as shown in pic 2. I am letting it sit now and will drive it again after it has rested for about an hour and will post those results.

 

[Idlethunder]

Do you live monitor the misfire counters in real time with Jscan at startup? Your situation is very similar to what I had with my 2020 Gladiator on cylinder #4. 90% of my #4 cylinder misfire counts were within the first 30 seconds after start and then level out with a few ticks on the count on my 30 mile commute.

I did spark plug replacement, coil position swap and even checked for coolant leakage into cylinder #4 with nothing detected and problem remained. I traded it off.

I would be interest if the dealership finds anything on yours. Before I traded, I briefly started a log when my ESS disable light would post and monitor the misfire count. I would get a pending P0300 code but it would never post.

Yes, I have been using Jscan to live monitor the misfires. Today cylinder 2 has also been acting up but most of them are on # 4. Like you, it seems that most of mine happen less than a minute after startup. As suggested by ShadowsPapa, I went back to the OEM air filter and am going to test it again in a few minutes. I will also report what the dealer says when I let them look at it this Friday.

 

[Idlethunder]

After not being started for approx an hour and 15 minutes, and with the oem air filter back in, the results did not change much. The misfires on cylinder 4 and 2 both went up a little during the first minute of driving after startup in pic 1. With aftermarket filter, cylinder 4 reported 30 misfires during first minute then no more. With oem 58 were reported during first minute then none for the next 4 of the short drive. After it has sat for about an hour, I am going to drive it again for 30 minutes or so and will report the Jscan results

 

[Idlethunder]

I went for an 18 mile round trip drive this evening to check the misfire count one last time and attached are the live Jscan readings. During the first ¾ mile, approx. 1 minute, Jscan showed 108 misfires on cylinder 4, 21 on 2, 3 on 6, and 2 on numbers 1, 2 and 5 for a total of 138. For the next 8 miles, those numbers went up 4 or less per cylinder, the total misfires after 9 miles was 147. At mile 9 I turned around and came home. During the 9 mile drive home, cylinder 3 showed 5 more but the others showed no more than 1 per cylinder and the overall total for the 18 miles trip was 155. At no point since I picked up the Jeep early this year has the engine sounded strange or lost power at all. Since the dealer cleared the code on Friday, the CEL has not come back on.

If anyone can help, I have a few questions.
If there were actually 138 total misfires in the first 60 seconds of driving, shouldn’t something have been noticeable?
How many misfires are looked at as normal?
Approx how many would it take to set off the CEL?

As stated earlier, I have an appointment with the dealer this coming Friday and hopefully it won't be something serious. What has me worried is that I've spent the last couple of days reading thru all the forum posts about misfires and there seem to be so many different causes and solutions, or a lack of. I'm sure it is irrational but of all the vehicles I've owned, this Gladiator is far and away my favorite and I am worried about her.

 

[dcmdon]

Update...

I spoke to the service department and they are going to replace the engine. Unfortunately, they are backordered and there are many people in front of me in line. At this point they can't give a date or rough estimate, although they are trying to get that info from Jeep. The dealership has been great through this process, so I know they are working it hard.

And this is where the fact that Jeep doesn't provide loaners raises its ugly head.

If they gave you a Grand Cherokee or even better another Gladiator, you wouldn't really mind waiting. I know I wouldn't. I'd be happy to rack up thousands of miles on their truck while mine is being fixed.

But if I'm on my own with a rental I'll be pissed.

I still don't know how Jeep expects to sell $120,000 Grand Wagoneers and not provide all the things that "Premium" brands (with less expensive vehicles) provide just as part of their service.

 

[dcmdon]

My truck has been throwing a P0300 every couple of weeks. It never runs rough and the light goes out after a few minutes.

I would like to log this using my Tazer Lite. I seem to remember that this can be done. Has anyone else done this?

As I'm typing this, I remember that it might require a laptop to remain plugged into the tazer and turned on. Is that right? If yes, that's not really workable.

 

[Hootbro]

How many misfires are looked at as normal?
Approx how many would it take to set off the CEL?

From my research in the past, it is not a defined actual number but based on a percentage of expected ignition events vs. RPM load.

It will vary by manufacturer but a rough 2% error loaded will set the pending code on the first ignition cycle and the CEL will set if it happens again on the 2nd ignition cycle. A 10%+ error loaded will set the flashing CEL.

Also, the error percentage it tracks is an average over time. If your misfires count is high, but your engine run time is long, it may not post any codes pending or permanent unless a high enough concentration of misfire events happen in a shorter time span.

 

[ShadowsPapa]

Thank you for bringing it up to change out the air filter. I thought about it last night but completely forgot to do it. The OEM filter is back in now.

No use giving them anything to "ask" about LOL

There's still the thing about "oil" hitting the sensors even though that part of the K&N has been pretty much debunked. (I don't like them for other reasons - but some dealers look for reasons.... if you know what I mean)

From my research in the past, it is not a defined actual number but based on a percentage of expected ignition events vs. RPM load.

It will vary my manufacture but a rough 2% error loaded will set the pending code on the first ignition cycle and the CEL will set if it happens again on the 2nd ignition cycle. A 10% error loaded will set the flashing CEL.

Also, the error percentage it tracks is an average over time. If your misfires count is high, but your engine run time is long, it may not post any codes pending or permanent unless a high enough concentration of misfire events happen in a shorter time span.

Yeah, I appreciate that reminder.
That's an EXCELLENT explanation.

My wife's WK2 was bucking like a mad mule but the light was not requested and no DTC set - and mine I could not feel a thing wrong - smooth and ran fine, but flashed the light and set a DTC.WEIRD
And the next time it was rougher than heck, my math said it never fired properly a singe time, it missed every singe cycle, over 1,100 misfires in a bit over 2 minutes at ide RPM - no light, no code.
So go figure - smooth as silk, light and code. Rough, jumping around, missed every cycle, no code, no light.
I guess if it's just sitting idling it doesn't give a rip, but going 20 out of a parking lot is critical so it pitches a fit.

I got this report the first time - didn't know it was there until checking the files on my phone. I opened the OBDLink app for a minute to look at it, then closed it down and it had gathered this and more in that time -

And this one didn't ding, didn't request the light, and no codes anywhere - a span of about 2-3 minutes, likely closer to 2, at idle speed. Do the math - did it even fire once? It felt like I pulled a plug wire off my 4.0.
Actually, no, I could remove a plug wire on an older engine and it wouldn't buck as bad as my truck did while I recorded this. It wasn't just a "misfire" it was like for that one cylinder it was kicking back, not just simply "not firing and pulling it's load".

 

[Idlethunder]

The Gladiator is in the shop now and I will update findings tonight. My check engine light has not come back on after being reset by the dealer last Friday although Jscan has showed between 40 to 200 misfires for every drive, usually less than 10 miles, since the light came on last week. Today I told them that I need the truck back tonight so I do not expect them to tear into it too. Hopefully they can get an idea of what is causing them. They are also updating PCM software and they said that could help

 

[ShadowsPapa]

The Gladiator is in the shop now and I will update findings tonight. My check engine light has not come back on after being reset by the dealer last Friday although Jscan has showed between 40 to 200 misfires for every drive, usually less than 10 miles, since the light came on last week.

That really parallels my own 2022 experience thus far.

I looked around and I can't find any TSB or any other communication from Jeep that applies to a 2022. Looks like they are perfect and Jeep hasn't had any complaints (HAHAHAHA)
I looked for PCM related bulletins and found nothing for the 2022, which I find weird.

Sponsored