Survey- For those with misfire issues

[Idlethunder]

No, they told me about it later when I asked how they got it resolved so quickly (I expect them to have it until the next day)

I was in and out of the service department with the update today in less than an hour. What they did is labeled as RRT 22-231 on the invoice.

Give me a few days to drive it and I’ll report back.

Sponsored

 

[Snapper692]

Well, looks like I am in the club now as well. 21 gladiator rubicon 3.6 AT build date of 9-20. at 5500 miles and CEL, code reader shows p0302. I can feel it missing at idle. My dealer service is only open M-F, so it will be Monday before I can even get a chance to see when I can get it in. Starts missing a lot worse in gear with foot on the brake. Once it gets more rpm it goes away. But the code Is set hard. Already lost a week earlier this year for a radiator replacement at 2200 miles (original had a large separation where the plastic and metal were bonded). After reading all of these issues not feeling great, lots of issues for a brand new truck.

My 2019 3.6 just threw the p0302 with the same issues.....Any update on what your issue was?

 

[ShadowsPapa]

My 2019 3.6 just threw the p0302 with the same issues.....Any update on what your issue was?

P0302 is a misfire, cylinder 2.

My misfire was a Cam/crank learn issue.
And it was cylinder #2 that was the worst.

Don't necessarily count on what fixes it for one fixing it for all.

 

[rjogren13]

My 2019 3.6 just threw the p0302 with the same issues.....Any update on what your issue was?

Nope stopped for about a month and just came back today. Makes no sense closest dealer is telling me Feb before I can get a service appointment. I have checked all fuses in the engine bay they were ALL loose thought that fixed it. Not happy had to have the radiator replaced (massive leak) at 2500 miles, now this with 6500 on it.

 

[Idlethunder]

My 22 Rubicon started with p0304 about a month after delivery. A few weeks later it was showing p0300 once or more every week but only when driven from a cold start. The misfires were so slight I couldn’t hear or feel them. Had I not been live monitoring with Jscan, I wouldn’t have known it was misfiring. The CEL would come on briefly and flash a few times when Jscan showed large spikes. Most of mine were on cylinder 4 followed closely by 2. I could see the p0300 with the quick diagnostic tool while it was running but it almost never stored the code past the next key cycle. The few times it did store the code, the engine would quickly go into limp mode then shut down but a minute or two later it would fire back up and run fine.

Around the end of November, the misfires became much more noticeable and started happening after I’d gone far enough to get it up to temp. These happened at least once a week after I’d driven 20 miles and stopped somewhere for 10 minutes or longer. With these new misfires, the truck would run very rough for several seconds while flashing the CEL but it usually straightened itself out after 15 to 20 seconds. Same as before, I could see p0300 with the diagnostic tool while it was running but once I shut it down, the code was gone. There were 2 instances in December where it shut itself down and stored the code but just like before, after letting it sit for a couple minutes, it fired back up and ran fine.

I took mine in on Dec 21 and they did the cam/crank relearn that ShadowsPapa mentioned. My small town dealership hadn’t heard of the relearn but from what I’d been told here, they were able to find an RRT on the issue. Since they reprogramed mine on the 21st, I’ve put over 800 trouble free miles on it while monitoring with Jscan. At no point since the relearn have I had more than 20 or so across all cylinders and that includes a 350 mile round trip to Dallas on Tuesday. I cannot say for certain that the problem is permanently resolved but at this point, I am very optimistic.

 

[Plasterboard]

I have had to same issues/symptoms as everyone else.

Today my wife stopped in for an oil change and the service record says they did “FLASH PCM PER RRT 22-231”. Same RRT that Idlethunder mentioned.

We will see how it pans out over the next few days/weeks.

 

[Idlethunder]

I have had to same issues/symptoms as everyone else.

Today my wife stopped in for an oil change and the service record says they did “FLASH PCM PER RRT 22-231”. Same RRT that Idlethunder mentioned.

We will see how it pans out over the next few days/weeks.

Hopefully your result will be as good as mine. It has only been 20 days since they flashed mine but Jscan shows very few misfires and the CEL hasn't come on once. I'm at about 1,500 miles since it was updated and have not had a single problem

 

[ShadowsPapa]

Mine was in last year to deal with the misfires. They said they did the relearn according to the TSB they'd found. Said nothing about a PCM flash, just forced the relearn. There was nothing on that paperwork that indicated there was a reflash.
I went in today for wave service - they said my truck showed up in the list for this 22-231 flash. They performed it.
I wonder if this actually does what they had done before, but now as different thing as sometimes happens if they have more instances of the same problem.

 

[IanNubbit]

Mine was in last year to deal with the misfires. They said they did the relearn according to the TSB they'd found. Said nothing about a PCM flash, just forced the relearn. There was nothing on that paperwork that indicated there was a reflash.
I went in today for wave service - they said my truck showed up in the list for this 22-231 flash. They performed it.
I wonder if this actually does what they had done before, but now as different thing as sometimes happens if they have more instances of the same problem.

This is basically what I was told by STAR when i had a vehcile in (about 4 months ago or so now). Had me do a relearn, send them some live data they wanted, then had us ship it. There has been updates to the PCM since available that are related to P0300. I'm assuming tehy finally got all the data they needed and improved/fixed the tune.

 

[ShadowsPapa]

This is basically what I was told by STAR when i had a vehcile in (about 4 months ago or so now). Had me do a relearn, send them some live data they wanted, then had us ship it. There has been updates to the PCM since available that are related to P0300. I'm assuming tehy finally got all the data they needed and improved/fixed the tune.

Quick (I hope!) recap of the misfire mine had -
3 or 4 days after picking it up, 56 miles drove it - totally warmed up, parked, shopping 30 minutes or so, came back out and after backing out of spot and moving forward to the exit of the lot - ding ding and MIL flashing, finally staying on. Didn't feel anything really.
A few weeks later, same thing after driving 35 or so minutes, parking 45 minutes, coming back out. This time it was violent shaking started at slow speed and low RPM - had to pull over. Came out of it after a couple of minutes.
Did it two more times weeks later, could barely feel the misfire.
Had to be totally warmed up, had to park it 20-40 minutes, then start it and drive slowly, low RPM, for it to happen. Cold starts were fine, driving was fine.

Look familiar? Would love to see a copy of that STAR case (he said it was a TSB....?)

As luck would have it, I got there early, shut it down, sat in line about 20 minutes, and when I restarted the truck - bingo! Light came on. Of course it had a number of other errors related to bus communications errors but I was happy that all of those errors happened that morning while I started the truck to drive it into their check-in area.

 

[IanNubbit]

Quick (I hope!) recap of the misfire mine had -
3 or 4 days after picking it up, 56 miles drove it - totally warmed up, parked, shopping 30 minutes or so, came back out and after backing out of spot and moving forward to the exit of the lot - ding ding and MIL flashing, finally staying on. Didn't feel anything really.
A few weeks later, same thing after driving 35 or so minutes, parking 45 minutes, coming back out. This time it was violent shaking started at slow speed and low RPM - had to pull over. Came out of it after a couple of minutes.
Did it two more times weeks later, could barely feel the misfire.
Had to be totally warmed up, had to park it 20-40 minutes, then start it and drive slowly, low RPM, for it to happen. Cold starts were fine, driving was fine.

Look familiar? Would love to see a copy of that STAR case (he said it was a TSB....?)

As luck would have it, I got there early, shut it down, sat in line about 20 minutes, and when I restarted the truck - bingo! Light came on. Of course it had a number of other errors related to bus communications errors but I was happy that all of those errors happened that morning while I started the truck to drive it into their check-in area.

Star Publication. It's like 6 pages, lots of useless test info. Basically this came out right after the truck I worked on. Its load up a designated Flight recording to monitor, drive the vehcile in a set style and manner. Then perfom the Cam/Crank Relearn, and repeat the same flight recording. Send data to STAR, ensure no CEL and "learned" is shown in mis-fire data (basically make sure it detected none). and return to customer.
Mind you, first thing I did was pull the oil fitler and ensure no metal was debris because I've seen that a handful of times as well. This was also on a vehicle that had no physical mis-fire that could be felt.

Also, this is the begening of the Publication
NOTE: IF THERE ARE ANY FAULTS SET ALONG WITH P0300 IN THE PCM, FOLLOW PUBLISHED DIAGNOSTIC ROUTINES IN SERVICE LIBRARY FOR ALL FAULTS...DO NOT FOLLOW THIS STAR ONLINE CASE.
ADDITIONALLY, MISFIRE COUNTS MAY ONLY OCCUR ON ALL CYLS ON ONE BANK, WITHIN 1-2 MIN AFTER A HOT RESTART DURING A VERY LIGHT LOAD...IF CONDITIONS WHEN THE COUNTS OCCUR DO NOT MATCH THOSE MENTIONED ABOVE, USE PUBLISHED DIAGNOSITIC ROUTINES IN SERVICE LIBRARY TO DIAGNOSE ISSUE...DO NOT FOLLOW THIS STAR ONLINE CASE.

Supposevly there is suppsed to be a update if not already released since this came out, this was a data harvest basically to help engineers create the fix.

 

[ShadowsPapa]

Star Publication. It's like 6 pages, lots of useless test info. Basically this came out right after the truck I worked on. Its load up a designated Flight recording to monitor, drive the vehcile in a set style and manner. Then perfom the Cam/Crank Relearn, and repeat the same flight recording. Send data to STAR, ensure no CEL and "learned" is shown in mis-fire data (basically make sure it detected none). and return to customer.
Mind you, first thing I did was pull the oil fitler and ensure no metal was debris because I've seen that a handful of times as well. This was also on a vehicle that had no physical mis-fire that could be felt.

Also, this is the begening of the Publication
NOTE: IF THERE ARE ANY FAULTS SET ALONG WITH P0300 IN THE PCM, FOLLOW PUBLISHED DIAGNOSTIC ROUTINES IN SERVICE LIBRARY FOR ALL FAULTS...DO NOT FOLLOW THIS STAR ONLINE CASE.
ADDITIONALLY, MISFIRE COUNTS MAY ONLY OCCUR ON ALL CYLS ON ONE BANK, WITHIN 1-2 MIN AFTER A HOT RESTART DURING A VERY LIGHT LOAD...IF CONDITIONS WHEN THE COUNTS OCCUR DO NOT MATCH THOSE MENTIONED ABOVE, USE PUBLISHED DIAGNOSITIC ROUTINES IN SERVICE LIBRARY TO DIAGNOSE ISSUE...DO NOT FOLLOW THIS STAR ONLINE CASE.

Supposevly there is suppsed to be a update if not already released since this came out, this was a data harvest basically to help engineers create the fix.

Mega-thanks.
You just confirmed what basically happened that visit and what they told me.
The service advisor told me the tech found that STAR bulletin that, in his words "matched your situation almost exactly".
And it did - left bank, 2, 4 and 6 with 2 always being the worst, followed by 4 with quite a few less and then 6 with misfires but less than 4.
Always a hot restart under light load.
It's like they had driven my truck for several weeks.

That says "if there are any faults set along with.................." they are to resolve those that may be why the other faults appear to have either been resolved, or are waiting to happen again when it gets warm, but no other faults, including CAN communication errors, have happened since they did that CCDIFF relearn.

No wonder they were so confident - they could find a doc to match my description (although in substantially fewer words)

 

[IanNubbit]

Mega-thanks.
You just confirmed what basically happened that visit and what they told me.
The service advisor told me the tech found that STAR bulletin that, in his words "matched your situation almost exactly".
And it did - left bank, 2, 4 and 6 with 2 always being the worst, followed by 4 with quite a few less and then 6 with misfires but less than 4.
Always a hot restart under light load.
It's like they had driven my truck for several weeks.

That says "if there are any faults set along with.................." they are to resolve those that may be why the other faults appear to have either been resolved, or are waiting to happen again when it gets warm, but no other faults, including CAN communication errors, have happened since they did that CCDIFF relearn.

No wonder they were so confident - they could find a doc to match my description (although in substantially fewer words)

what was the date on that?

 

[ShadowsPapa]

what was the date on that?

11/10/2022

 

[Snook]

Quick (I hope!) recap of the misfire mine had -
3 or 4 days after picking it up, 56 miles drove it - totally warmed up, parked, shopping 30 minutes or so, came back out and after backing out of spot and moving forward to the exit of the lot - ding ding and MIL flashing, finally staying on. Didn't feel anything really.
A few weeks later, same thing after driving 35 or so minutes, parking 45 minutes, coming back out. This time it was violent shaking started at slow speed and low RPM - had to pull over. Came out of it after a couple of minutes.
Did it two more times weeks later, could barely feel the misfire.
Had to be totally warmed up, had to park it 20-40 minutes, then start it and drive slowly, low RPM, for it to happen. Cold starts were fine, driving was fine.

Look familiar? Would love to see a copy of that STAR case (he said it was a TSB....?)

As luck would have it, I got there early, shut it down, sat in line about 20 minutes, and when I restarted the truck - bingo! Light came on. Of course it had a number of other errors related to bus communications errors but I was happy that all of those errors happened that morning while I started the truck to drive it into their check-in area.

You and I have discussed this earlier in this thread, my issue is identical you yours. Mine has been running fine since my last Flashing CEL (P0300) in August. At that time the dealer said Engineering had no fix. I haven't taken it back for this latest update that everyone is talking about. Ive been absent for a while with a health issue.

Sponsored