Jeep Wrangler Forum banner
1 - 12 of 12 Posts

toomanyjeepsx3

· Registered
Joined
·
21 Posts
Discussion starter · #1 · (Edited)
2014 JKUR .................I'm still having trouble .... going on 2 weeks. No one can figure it out. I've had a Mopar laptop/software/obd on it along with a $6000 snap-on and Mopar software. Obd cant read vin or anything passed the tipm to the under hood pcms's. Inside pcms all work fine. Amp/hvac and so on can be seen. Pcm/tcm/abs and so on modules cant be seen. Jscan cant get passed the obd and you have to manually enter the vin on the other scanners.

I walked out to the jeep 2 weeks ago and the fob didn't open the door...use the key and open to the alarm, key wont start it when inserted, zero start, alarm mode, radio lockout out, flashers and nearly all lights on the dash. Its like the computers went missing while parked overnight. Key is recognized by the wcm. wipers went on and off twice while messing with it over a weeks' time. No amount of resetting pcms/ecu's or tipm works. tipm was pulled a few times, all pins and connectors look and feel perfect. Battery is perfect, battery terminals have been touched together a dozen times. Zero coming out of security alarm mode. Pcm unplugged and all pins/connecters are perfect, zero water of corrosion. Wiring harness looks perfect from front to back. Sway bar harness /sway bar are deactivated/bypassed with jscan. I pulled a friends tipm and put it in my jeep......no start but alarm mode/security mode went away !!

A week later i walk out to the jeep and magically the Jeep fob works and the key starts the jeep.... the dash lights are gone except for the cel. Lots of codes.....c2200,c121a,p0073.....zero temp outside shown.... but it showed minus 39 twice !!,u1148, u0241, u0163, all the headlight and turn signal code,p0222, p0123, b2204..........odd/bad ones are b2204 ecu configuration mismatch, u001, can c bus, u1148 additional can c ecu detected. My blinkers would go out when driving, it drove perfectly other than tat. Drove it for 2 days and when i woke up in the morning and went out to the Jeep and the fob would not open, key won't start, lockout/alarm/security back on. Can't read/see vin again.

Any ideas ?????I think its pcm or tipm or wiring harness....except in the case of the wiring harness i don't think it would get fixed sitting overnight or not work a few days later while parked. I am leaning towards sending the tipm and or the pcm out for testing ???.... because I don't know what else to do !! There's a definite can bus issue


I have done a hard reset a few times ……twice afterwards the Jeep recognized the fob and it started . 20 plus codes , vin is available and JScan works . Hard reset was pulling the battery cables and tying them together for 2 hours until memory and capacitors were dumped.
Makes me think it’s not a wire, connector or harness. Tipm ??
 
Just remember KISS...... Jeep's computer systems are really weird and are really, really super sensitive to wiring screw ups. I had a wheel sensor short out on the rotor and my Jeep went into limp mode, threw all sorts of unrelated codes and even the dealer gave up on diagnosing the problem.
That being said, check and clean ALL ground connections. Check and clean ALL wiring connectors. Check with a fine tooth comb all of your wiring harnesses for shorts, broken wires, melted insulation, faulty heat protection and etc. Good luck and please let us know what actually fixes your problem!
 
Discussion starter · #5 ·
All connectors look great, wiring looks great, zero dirt dust or moisture in any . I couldn’t even find a squished wire or even any with abrasions. All grounds are tight and perfect. Zero melted anything .

the fact that the problem happed overnight while parked and not moving and then 2 weeks later it just decides to run for a couple days leads me to believe it’s not a wire. Wheel sensors generally give multiple codes and cause several driving issues.

I’d like to check continuity between the tipm and pcm but I need a wiring diagram to do that
 
I would suggest you take all of your ground wires off, clean and reconnect. Take all of the wire loom connectors apart, check to make certain all of the terminals are clean and properly seated. Check all of the wire looms for rodent damage. Replace your battery with a known good one. Throw away the stock JK battery terminal connectors and replace with heavy duty JK appropriate battery terminal connectors. If you still have problems, try to reach out to CMS Rock on this forum. He will give you so much technical info your head will pop. Once again....the fact that overnight all of this crap started leads me to believe it is your battery or rodent damage!
 
Discussion starter · #7 ·
I would suggest you take all of your ground wires off, clean and reconnect. Take all of the wire loom connectors apart, check to make certain all of the terminals are clean and properly seated. Check all of the wire looms for rodent damage. Replace your battery with a known good one. Throw away the stock JK battery terminal connectors and replace with heavy duty JK appropriate battery terminal connectors. If you still have problems, try to reach out to CMS Rock on this forum. He will give you so much technical info your head will pop. Once again....the fact that overnight all of this crap started leads me to believe it is your battery or rodent damage!
battery is a nearly new AGM. Battery is at 12.6 v. I even had a battery charger on it while messing with everything, so it’s been over that voltage also . Battery load tests just fine . Battery terminals are heavy duty aftermarket . Every single ground spot looks perfect . There’s not a speck of corrosion or rust and any terminal or grounds. All grounds were unhooked and tightened back in January when I did a head job on it.
Nearly every wiring connector has been taken apart and every single pin has been touched and checked for wiggling/loose parts . Zero dust , condensation or corrosion in any . They all look brand new. There’s not a single chew mark on any part of the wiring harness from bumper to bumper .

it’s done the overnight security mode non start thing twice…..doubt it’s rodents .
 
I really can’t help much, but can tell you I had a bad TIPM and it caused all sorts of strange and intermittent failures and codes (including inability to start). But, my symptoms were not an exact match to yours.

As you likely know, it is an expensive part. If you can find one to try without having to buy in advance, I would give it a shot.
 
the basics of the bus systems on a JK
simplest is the single wire Lin bus which has a master node in the cluster and that takes lin bus messages and sends them over the can IHS bus
for example when you press a button on the steering wheel to control radio or hands free or evic they all sends mux resistance to the speed control steering wheel switch
that speed control switch also contains a lin slave node and it reads the resistance and based on that sends out a digital lin message (single wire bus) over the clock spring to the cluster
The cluster receives the lin bus message and send a corresponding message out over the can ihs bus which can be picked up by the radio

The PCM sends out can messages only over the can C bus

The OBD2 diagnostic port only is connected to the can c diagnostic bus (different then can c bus)

The TIPM among other things is the interconnection between the 3 can busses and translates and relays messages between the 3 can busses (Can C and Can C diagnostic and Can IHS (interior high speed))

for example time displayed on clock is kept in the SKIM/WCM module and sent out over the Can C bus , the TIPM translates it to can IHS bus so that radio can display and change time stored in the WCM) but without a WCM all non nav can bus radios have no time to display
 
1 - 12 of 12 Posts