Notices
Series I Trouble Shooting This is the place to learn more about or discuss any issues you're having with your RX-8

CEL Codes U0073 and U0155

Old 05-03-2013, 12:34 PM
  #1  
('04 Nordic Green 6MT GT)
Thread Starter
iTrader: (1)
 
thomthoms3's Avatar
 
Join Date: Jun 2012
Location: Nashville, TN
Posts: 166
Likes: 0
Received 0 Likes on 0 Posts
TN CEL Codes U0073 and U0155

So today, I had someone read my CEL codes, and the two codes U0073 and U0155 showed up. I tried doing some research on them, but no luck. The only mods I have installed are AEM Cold Air Intake, and TurboXS cat back exhaust. Looking for any useful information. Thanks!
thomthoms3 is offline  
Old 05-03-2013, 04:01 PM
  #2  
Registered
 
sd1611's Avatar
 
Join Date: Mar 2012
Posts: 30
Likes: 0
Received 0 Likes on 0 Posts
Those are CAN bus communication errors. I get those sometimes when my OBD2 reader is not seated completely.

https://www.rx8club.com/series-i-tec...e-list-212975/
sd1611 is offline  
Old 07-02-2013, 02:55 PM
  #3  
New Member
 
Join Date: Jun 2013
Posts: 1
Likes: 0
Received 0 Likes on 0 Posts
My rx8 suddenly stops. Than the dtc is u0073 can bus communication. How can I repair my car.
Zamba is offline  
Old 07-02-2013, 02:59 PM
  #4  
Verbose SuperMod
iTrader: (2)
 
Join Date: Oct 2007
Location: Pacific Northwest
Posts: 16,683
Likes: 0
Received 137 Likes on 76 Posts
We can't really provide any suggestions on how to repair it until we know what is wrong with it.

As you see above, the U0073 is a CAN BUS communication error. This is not disabling your car, this is a communication error with the device that is reading the codes.


Sooo...how about providing more information about what's wrong?

https://www.rx8club.com/new-member-f...t-here-202454/
Originally Posted by RIWWP View Post
Questions we CAN answer:
Most issues that the RX-8 faces are easily answered when you post detailed, descriptive, and accurate explanations of what symptoms you are having with your RX-8. Many of our issues share common symptoms with at least one other issue. Several of the really common issues share MOST of their symptoms with another problem. So when you post: "power loss?" We can't really tell you what is going on. We can only throw the book of possible issues at you for you to figure out.

The amount of assistance you receive is DIRECTLY associated to how much detail you provide!

So what do you need to share?

A) Break each issue you are seeing out by itself. For each of these issues, detail what RPMs it occurs in, and what RPMs it doesn't. Detail how much throttle you are giving when it occurs.
B) Detail what the ambient temperatures are that you are seeing, what the gauges are doing.
C) If you have a CEL, GIVE US THE CODE! (most auto-parts stores will pull the code for free for you. Otherwise, you can buy a code reader for LESS than the dealer's diagnostic price, giving you a discount on that one, and free code pulling for the rest of the device's life, across every car you own) (Hint, search with Google and site:rx8club.com <CEL> before posting. You will probably find your answer.)
D) Detail any possible modifications or repairs that have been made within the last 3,000 miles, even if it seems like it's not related.
E) Detail the age and mileage of the car, and what maintenance history it has been on. NOT just "it's gotten regular maintenance" because there are wear items that are not part of "regular maintenance" for dealers and most shops.
F) Since many issues are ignition related, and you are going to get asked, give us the mileage and age of ignition coils, wires, and plugs.
G) Detail out when it DOESN'T happen. This is just as critical as when it does!

Another thing to keep in mind is that unless you are being a complete jackass, and unless the person responding to you is ignorant about the issues, our answers are going to be pretty accurate, if not dead on. Even if you don't like the option. We have no stake in your finances, no stake in making money off of it. We DON'T like to see unhealthy or busted 8s. So if you choose to ignore our recommendations, do so at your own peril, and don't come whining to us that you shoveled money at the problem that was completely unneeded.
RIWWP is offline  
Old 03-17-2014, 11:32 AM
  #5  
Yellow looks faster.
iTrader: (1)
 
Wolfe's Avatar
 
Join Date: Jun 2012
Location: North NJ - Utah
Posts: 445
Likes: 0
Received 0 Likes on 0 Posts
Sorry to revive this, But I'm trying not to create a new thread on a topic that is not quite answered where ever I search.

I'm getting the same codes. U0155 and U0073.

Some history I guess... I have an AccessPort on the car, and it can sometimes cut out of I bump it slightly, or just stop communications with vehicle. Its been installed for a while now with this happening, but no issues.

As I was driving to work today, the cars instrument cluster would just start failing. The RPM needle and speed would temporarily show 0 and then hop right back up to the normal RPM and speed I was driving, no stutters in the engine when this happened.

Two days ago, I installed new springs on the car. I heard maybe its possible to knock a connection loose? I don't know what we could have possibly hit. It drove home and for an hour after that with no issue and took it out yesterday and had no issues.

@thomthoms3 - Did you get your car sorted out? what was the problem?

Thanks for any help!
Wolfe is offline  
Old 03-17-2014, 11:52 AM
  #6  
Verbose SuperMod
iTrader: (2)
 
Join Date: Oct 2007
Location: Pacific Northwest
Posts: 16,683
Likes: 0
Received 137 Likes on 76 Posts
It's just a communication error. If you disconnect the accessport, does the dash problem go away?

I had 3 different OBD2 readers while I had my 8, and all 3 of them showed U codes when connected. None of the 3 showed the same U codes as the other 2, and which U codes any one would show, were always shown by that one.

One of the devices would cause my TCS to be disabled if I plugged it in and connected after the car was already running.


I saw elsewhere recently where a shop that was doing some testing on a Miata plugged in a data reader, and it fed a bit of extra voltage to the knock sensor on that particular car, triggering an ECU limp mode due to knock until they unplugged it and cycled the car off then on again.

So I think that some cars just don't like some OBD2 devices. There probably IS a reason for it, but not really something the average guy can predict and plan for, so I wouldn't worry about it. Just shift to only using the AP when you need to flash or log. My AP would only stay connected for about 45 minutes before shutting down, so I ended up leaving mine in a box on the shelf unless I needed it for logging or flashing.
RIWWP is offline  
Old 03-17-2014, 12:52 PM
  #7  
Yellow looks faster.
iTrader: (1)
 
Wolfe's Avatar
 
Join Date: Jun 2012
Location: North NJ - Utah
Posts: 445
Likes: 0
Received 0 Likes on 0 Posts
Stuck in the office till 2pm mountain time. Just freaking out a bout it a little. I really don't want to deal with any electrical problems... I will update here later with the current state of the car.

Thanks for the help!
Wolfe is offline  
Old 03-17-2014, 11:27 PM
  #8  
Yellow looks faster.
iTrader: (1)
 
Wolfe's Avatar
 
Join Date: Jun 2012
Location: North NJ - Utah
Posts: 445
Likes: 0
Received 0 Likes on 0 Posts
Unplugged the AP and it was all back to normal. Will be keeping watch on it though.
Wolfe is offline  
Old 03-23-2014, 10:57 AM
  #9  
('04 Nordic Green 6MT GT)
Thread Starter
iTrader: (1)
 
thomthoms3's Avatar
 
Join Date: Jun 2012
Location: Nashville, TN
Posts: 166
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by Wolfe View Post
Sorry to revive this, But I'm trying not to create a new thread on a topic that is not quite answered where ever I search.

I'm getting the same codes. U0155 and U0073.

Some history I guess... I have an AccessPort on the car, and it can sometimes cut out of I bump it slightly, or just stop communications with vehicle. Its been installed for a while now with this happening, but no issues.

As I was driving to work today, the cars instrument cluster would just start failing. The RPM needle and speed would temporarily show 0 and then hop right back up to the normal RPM and speed I was driving, no stutters in the engine when this happened.

Two days ago, I installed new springs on the car. I heard maybe its possible to knock a connection loose? I don't know what we could have possibly hit. It drove home and for an hour after that with no issue and took it out yesterday and had no issues.

@thomthoms3 - Did you get your car sorted out? what was the problem?

Thanks for any help!
As they have said, it seemed to just be an error with the code reader and the OBDII port on my car. I ignored the codes, and they went away. Not sure about your tach and speedo acting up though, that's beyond my knowledge. But as far as the two codes go, it ended up just being that the code reader wasn't plugged in all the way, so my car threw the codes.
thomthoms3 is offline  
Old 03-23-2014, 03:24 PM
  #10  
Rotary Evolution
 
Karack's Avatar
 
Join Date: Oct 2011
Location: Central FL
Posts: 853
Likes: 0
Received 0 Likes on 0 Posts
and do not plug in or unplug an OBDII device while the car is already on, usually that results in these erroneous codes being stored. doing that interrupts the communications temporarily from some scanners.
Karack is offline  
Old 04-04-2014, 09:03 PM
  #11  
Registered
iTrader: (15)
 
Twiztog43's Avatar
 
Join Date: Aug 2006
Location: Las Vegas
Posts: 1,052
Received 0 Likes on 0 Posts
I am also have the U0155 CEL.

I have had this issue for a while now, and has not caused any mechanical issues. However, I am wondering will I fail a smog test in California due to this SPECIFIC cel code, which has nothing to do with emissions?
Twiztog43 is offline  
Old 04-05-2014, 08:43 AM
  #12  
Verbose SuperMod
iTrader: (2)
 
Join Date: Oct 2007
Location: Pacific Northwest
Posts: 16,683
Likes: 0
Received 137 Likes on 76 Posts
The CEL isn't there if you don't have your reader plugged in. It's a communications problem with your device only.
RIWWP is offline  
Old 10-01-2015, 02:01 PM
  #13  
New Member
 
Join Date: Oct 2015
Posts: 1
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by RIWWP View Post
I had 3 different OBD2 readers while I had my 8, and all 3 of them showed U codes when connected. None of the 3 showed the same U codes as the other 2, and which U codes any one would show, were always shown by that one.

My OBD II reader
Mini ELM327 OBD2 V1.5 Car Bluetooth Scanner Android Auto Scan Diagnostic Tool UK | eBay

I've tried use TORQUE PRO on my sony Z3 compact but something failed.
My ABS and TC are ON at the dashboard now. So I have connected different OBD II model 2000 (not on Bluetooth) it showed me fault codes:
U0121 (Lost Communication With Anti-Lock Brake System (ABS) Controle Module)
Also
U0155 (Lost Communication With Instrument Panel Cluster (IPC) Controle Module)

I've erased errors. Everything seems back to normal.

So witch OBD II on Bluetooth should I use to communicate with TORQUE app with my phone sony z3???

Or how to fix communication with OBD Bluetooth i have got.

Test going thru to the point, rx8 is left with errors.

Any ideas?
mikuGo is offline  
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
mdl0209
Series I Trouble Shooting
14
05-23-2019 05:46 PM
Shankapotamus3
Series I Trouble Shooting
26
11-06-2016 08:26 AM
TotalAutoPerformance
Vendor Classifieds
3
10-14-2015 12:29 PM
Eliseo Esquivel
RX-8 Discussion
2
09-30-2015 08:28 PM
Evan Gray
Series I Trouble Shooting
0
09-26-2015 12:30 PM


Thread Tools
Search this Thread
Rate This Thread
Rate This Thread:
You have already rated this thread Rating: Thread Rating: 0 votes,  average.

Quick Reply: CEL Codes U0073 and U0155


Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

© 2019 MH Sub I, LLC dba Internet Brands

We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.