Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB - CEL U0155

- Issues | Warranty | Recalls / TSB (https://www.ft86club.com/forums/forumdisplay.php?f=72)

- - CEL U0155 - Lost comm with cluster (https://www.ft86club.com/forums/showthread.php?t=18511)

CEL U0155 - Lost comm with cluster

This morning I reset my ECU because well, I felt like it. My car had been running just fine but I was curious how long the BRZ takes to go through it's readiness monitors, etc. I have almost 3k miles on the car.

After I reset, I drove about 15 miles and plugged in my code reader while driving. All but 2 readiness monitors had finished by then. I was happy to see the car goes through them pretty fast.

5 miles later, I was at a light. Plugged in my code reader again. WHILE I was plugging in the code reader, a CEL came on. U0155. WTF? So I tried driving and the car was in limp mode. Lame. Pulled over and googled to find that it indicates lost communication with instrument cluster.

I reset the code and drove another 20 miles. So far so good. The CEL has not come back. I'm wondering if it was some sort of a fault I caused while plugging in the code reader? I've never had a car with an OBD2 that was sensitive to being plugged in while driving, maybe this one is?

Anyone else care to chime in?

My bluetooth ODB reader kept causing this code and the gauges to die. It just doesn't like some. Turns out my unit was completely dead as it wouldn't work on other cars anymore either. I assumed the failure was due to it being bad but or yours it continued to work?

what odb2 reader do u use?

Quote:

Originally Posted by Kido1986 (Post 465586)

ok, good to know. I had a feeling I caused this. Yes, my reader still worked after this.

I can't remember what reader I have, but it's a decent one. Like $150.

I was using the Blue and Orange Bluetooth ELM327 (not the solid blue one, know issues with that one)

Yes certain, OBD2 readers cause this code to come up and other codes like U0073.
And it usually happens with the reader plugged in during startup.

This happened to me today, too, when I plugged in my openflash tablet. I used the tablet to erase the code and drove 300 miles. It didn't never came back.

Same with open flash tablet and extension from Amazon. It reads fine but didnt like to write using cable

Sent from my SM-N900T using Tapatalk

Codes U0155 and U0073 happen to me on occasion if I leave my bluetooth reader plugged in.

Fix: Don't leave it plugged in

Just got a U0073 when I left torque pro open and running while I ran into a local store. The car was off but torque pro kept talking to the ecu. I guess the ECU doesn't like this. OBDLINK LX was used. I can get this to repeat if I leave the app open with the car off. I need to check to make sure it's going to sleep.

This happens to me all of the time with Torque Pro and Nexus 7(2013).

SYMPTOMS: Sometimes my car will start but promptly stalls out and will not start until I pull the battery cable and reset the ECU.

SUSPECTED REASON: Forget to close out TORQUE PRO before turning off my BRZ.

This is super annoying but what other options are available for monitoring the ECU?

Thanks for this, put me at ease since I had my first CEL. Indeed I have been leaving my ODBII reader plugged in for months, never had this come up though... I typically close Torque when I leave the car because it stays in my notification bar otherwise and I didn't this weekend which boom resulted in CEL.

I just had this happen a minute ago.I left Torque Pro on and engine off to change clothes and when I jumped back in the car voila, cel U0155 code.Used Open Flash Tablet, cleared code, reflashed same CPB tune and now no cel.Apparently my 15 Scion FRS doesn't play well with Torque Pro or OBD Link lx

Quote:

Originally Posted by whatsupemt (Post 3212482)

I just had the exact same thing happen to me in my 2017 BRZ. Last night I turned my car off with Torque [Lite] still running in the background and then this morning when I started my car the check engine light came on and I have the U0155 error code.

How did you guys clear the permanent DTC/has anyone tried the below? I'll give this a go myself when I next get the chance and advise how it goes.

Quote:

Originally Posted by https://www.autoserviceworld.com/carsmagazine/taking-a-first-look-at-permanent-dtcs/

Universal Trip Drive Pattern

So, how to clear a Permanent DTC? By performing a Universal Trip Drive Pattern that meets the strict criteria in the repair manual, to prove to the computer that the fault has indeed been repaired and no one is trying to cheat on an emissions test. After performing this Drive Pattern, if the code doesn’t clear it’s usually because the strict criteria were not followed exactly. It’s a pain, but that’s the way it goes.

Typically, this Universal Trip Drive Pattern starts off by clearing all the DTCs so that only the Permanent DTC remains (always refer to service information for applicable information and procedures).

Then turn the ignition ON, start the vehicle and let it idle for at least 30 seconds. Then, without cycling the key, drive the vehicle for at least five minutes at more than 40 km/h. Then (again without cycling the key) let the vehicle idle for at least 30 seconds before shutting it OFF. The whole drive cycle must take at least 10 minutes. After performing a Universal Trip Drive Pattern, the computer clears the code, since it’s “seen” that the problem is fixed and not reoccurring. Sounds simple enough, and most problems have apparently come from not performing the Universal Trip Drive Pattern correctly, but time will tell if these new DTCs will be problematic.