Hello everyone, thank you for accepting me into your forum.
I own a 2005 Wrangler TJ Sahara with the 4.0 liter I6 engine and NSG370 6-speed manual transmission. I’ve had the "no bus" error sporadically for almost two years now. It has always resolved itself in the past, usually without any known reason for the solution. However, recently I’ve been getting this error and can’t seem to fix it. I’ve already tried removing the console, spraying WD-40 on the odometer contacts behind the dash, and reassembling it; disconnecting all the connectors (camshaft sensor, throttle position sensor, oxygen sensors, etc.) to see how it behaves without the connected sensors, but without success. I’ve also cleaned and checked all the grounds in the engine compartment, driver’s cabin, and passenger cabin. As soon as I turn the key to the "ON" position, I get the "no bus" error after a few seconds, along with the illuminated indicators. The error codes I was able to read are P0513, U0155, and U0168, which are mostly related to the SKIM (Sentry Key Immobilizer Module). I’ve also tried the spare key and treated all the connectors under the steering wheel with contact spray.
The interesting thing is: The car starts and drives – if you’re quick enough, the immobilizer doesn’t have time to engage and stall the engine - but you dont have any dash information since the no bus error. However, when you turn the key from the "ON" position (both with the engine running and when stationary) to the "START" position, all the indicators come on, and you hear a click in the turn signal relay under the steering wheel. If I let the key return from the "START" position to "ON", the indicators go out again. I initially thought it might be related to the radio, air conditioning, or something similar, since these systems are turned off in the "START" position. Unfortunately, just replacing the fuse in the glove compartment doesn’t seem to help. The ignition switch also doesn't seem to be the problem..
I’m really at a loss and hope someone has an idea of what the issue might be.
Thank you and have a great week!
I own a 2005 Wrangler TJ Sahara with the 4.0 liter I6 engine and NSG370 6-speed manual transmission. I’ve had the "no bus" error sporadically for almost two years now. It has always resolved itself in the past, usually without any known reason for the solution. However, recently I’ve been getting this error and can’t seem to fix it. I’ve already tried removing the console, spraying WD-40 on the odometer contacts behind the dash, and reassembling it; disconnecting all the connectors (camshaft sensor, throttle position sensor, oxygen sensors, etc.) to see how it behaves without the connected sensors, but without success. I’ve also cleaned and checked all the grounds in the engine compartment, driver’s cabin, and passenger cabin. As soon as I turn the key to the "ON" position, I get the "no bus" error after a few seconds, along with the illuminated indicators. The error codes I was able to read are P0513, U0155, and U0168, which are mostly related to the SKIM (Sentry Key Immobilizer Module). I’ve also tried the spare key and treated all the connectors under the steering wheel with contact spray.
The interesting thing is: The car starts and drives – if you’re quick enough, the immobilizer doesn’t have time to engage and stall the engine - but you dont have any dash information since the no bus error. However, when you turn the key from the "ON" position (both with the engine running and when stationary) to the "START" position, all the indicators come on, and you hear a click in the turn signal relay under the steering wheel. If I let the key return from the "START" position to "ON", the indicators go out again. I initially thought it might be related to the radio, air conditioning, or something similar, since these systems are turned off in the "START" position. Unfortunately, just replacing the fuse in the glove compartment doesn’t seem to help. The ignition switch also doesn't seem to be the problem..
I’m really at a loss and hope someone has an idea of what the issue might be.
Thank you and have a great week!
