Well, last week I had the "Check Engine" light come on, and when they hooked it up to read what code it was throwing, it was "Cylinder 2 Mis-fire". They cleared it and I drove most of that day before it returned. Took it back in today and they did a "Software Update" based on a TSB they'd received, and cleared it again. Hadn't driven 50 miles before the check engine light came on again.

So, I figure that, along with the ticking noise, means I'll be up for this as well.

Mac

 

I have a '12 JKUR and was avidly following the Pentastar tick thread that was shut down. I have opened another thread and hope to keep the discussion at a more mature (and informative) level.

https://www.jk-forum.com/forums/jk-t...es-jks-244235/

Also, I have created a spreadsheet in Google Docs of the 2012 JK's who have developed the dreaded "tick" and are in need of or have had a head replacement. On the forums addressing this issue, it was becoming confusing to keep track of what issues have developed and what has been done to address those issues. In order to protect the privacy of forum members, member user names are not included in the spreadsheet. Also, I am the only one who is able to edit the spreadsheet. You can access it through a link in the above thread.

If you have any questions, comments or would just like your JK added to the data you can contact me via PM. Thank you.

 

Wendy, in another thread you made a statement about working with dealers to get heads replaced. As I am not familiar with your bio, are you a rep or did I just missunderstand? What is being done with the list you generatted?

 

JKbender...

I am just an enthusiastic Wrangler owner, but have no affiliation with dealerships or anything similar. No one "official" is looking at the spreadsheet info that I'm aware of. I just put the info together because I like to have the facts to a problem and then put all the ducks in a row to get a more complete picture. The original thread was becoming very tedious to read through; 73 pages, some of which were filled with child-like name calling. We should all be able to learn from each other's experiences...that is the nature of the JK-Forum.

My '12 JKUR is my favorite of all the Wranglers I've owned. If I do develop an issue with my engine, I want to go to the dealer educated.

 

Let's just hope that CCuChris doesn't bomb this Thread again.

I'm at work now and can't seem to open your spreadsheet Wendy, does it include the mileage and the jeep build for all issues? What is the latest build date to have the tick?

Thanks!

 

Sounds good, just thought that we might have an insider amongst us.

.... Just a well organized person!

 

Hi SabFan...

I ditto that!

Yes. The spreadsheet includes mileage and production date for the member's who included that info in the thread or PM'd me. The latest build date, of the Jeep not the engine, with issues is 4/12.

 

And what I've heard is the tick usually shows up after 3000 Miles right? between 3000 and 15 000?

I'm just curious as to how many people with builds after April 2012 with more than 15 000miles that don't even have that tick?

EDIT: I know, 15000 miles in 4 months is a heckuvalot!

It would be interesting to see if most if not all Post-April builds are actually fine?

 

Auto Week had an article on this that sugested (no specific date given) that the new head did not hit the assembly plant until mid july.

 

You are correct, and I do know this.

The problem is, having an engine assembled and having the jeep built is two radically different dates. Someone has posted in the past (and I forget who it is) that his engine was assembled two months prior to having his jeep built (which is located on the inner driver door - while the engine assembly is somewhere on the actual engine).

So for example, if they are still using the engines that were assembled in june to build the august jeeps (within that two month range). Let's hope that Chrysler had the wits to change the heads on the engines that were waiting in line to be fitted inside non-built jeeps.

Hope that post wasn't confusing?