"no BUS" error troubleshooting
There was a recall on the steering wheel clock spring. Did you ever take your 07 JKUR into the dealership and have it replaced? If not, I would suspect that 1st since it's a common known problem.
I think the best route (the professional route) to a solution for you is to read the sticky about OBD2 Enhanced Code Scanners, acquire one of the programs (Appcar, Jscan, BlueDriver, etc.) plus a hardware scanner (BlueDriver includes there own scanner, OBDLink MX for example is required by the others), then proceed based on the trouble codes.
Last edited by Mr.T; May 19, 2020 at 06:22 PM.
Yep, there's a problem on all forums regarding asking for help then never following up.
I think the best route (the professional route) to a solution for you is to read the sticky about OBD2 Enhanced Code Scanners, acquire one of the programs (Appcar, Jscan. BlueDriver, etc.) plus a hardware scanner (BlueDriver includes there own scanner, OBDLink MX for example is required by the others), then proceed based on the trouble codes.

I think the best route (the professional route) to a solution for you is to read the sticky about OBD2 Enhanced Code Scanners, acquire one of the programs (Appcar, Jscan. BlueDriver, etc.) plus a hardware scanner (BlueDriver includes there own scanner, OBDLink MX for example is required by the others), then proceed based on the trouble codes.

If controls don't work or wipers won't turn off unless key is off then my guess is you have lost the CAN Bus somewhere to the dash. On the 07 the CAN is the white/red & white/grey wires twisted together. I know that because that is the point I tapped the Chev CAN into the Jeep system. Open circuit also prevents AC working and TAP shift won't work.
Thanks for the quick response. Wasn’t trying to hijack the thread as I was venting a little bit really not expecting anything back...and as a matter of fact, I haven’t yet taken it in for the clock spring recall yet. I read the notice they sent and it said it can cause the air bag light to illuminate. I hadn’t heard of it causing this issue, but appreciate your recommendation and will be making the appointment today. I will let you all know if it did make a difference or not.
This is also a great suggestion of where to start. Having any of these OBD2 scanners are worth their weight in gold. Anytime a dash light comes on the computer will store a diagnostic code, the scanner will allow you to grab the code which then can provide you further information about the code to help hunt the problem down. Without one of these scanners it is kind of like throwing darts at a dartboard with a blindfold on.
I think you know this already, but just in case; The key method only shows the basic codes from the PCM (powertrain control module) only. It takes an enhanced scanner get to the proprietary codes and the other modules.
That said, I haven’t taken it in for the clockspring recall yet, but I did remove the dash this weekend and inspected the wiring. Only found a couple areas where the bundle was tight against the support structure, but no wires worn through the coating. Taped them up good and repositioned the bundle taking the stress off those areas. Checked all the grounds on the driver and passenger side kick-panel locations; no defects. I disassembled the cluster, inspected the PCB for burn spots and secure components. Nothing. Also removed the TIPM and inspected it as well. Shot all the fuses and relay coils for continuity/resistance; all was good. Reinstalled the TIPM, dash, cluster, and radio; problem is now gone. I’m assuming a bad connection, probably on the cluster, which was fixed by reseating the connector upon installation. I have driven the Jeep over 100 miles since with no reoccurrence of the dash light Christmas tree act, whereas, before I couldn’t get around the corner from my house without it going off.








