![]() |
Weird Issue u0100 u0122
I just did my first tune using OFT 3 days ago. Everything seemed fine but I decided to check fault codes and I had a u0100 and u0122 through the torque app (no CEL ever came on or anything other warning light). I am using a bluetooth adapter for the torque app. I tried clearing the codes but they come right back. Once I got home from work and hooked up my OFT it did not find any codes. i switched back to the bluetooth adapter and torque and it found the codes again but OFT does not see them still. I dont understand whats going on. I never had any fault codes in torque until I did my first tune. Any idea?
|
From what i can find those codes are triggered whenever the car loses communication with the ECM(u0100) or other systems(u0122: possibly vehicle dynamics control?). As long as the car is operating ok you should be fine. Make sure you are continuing to log to see if anything is out of whack.
I know every time I flash a different tune I get a p0700 which signals that it lost communication with the TCU but as soon as I clear it it does not come back until I flash a different tune. I use the OFT for flashing and logging so i have not checked with torque to see if I get those u codes as well but in my unprofessional opinion that code was generated due to the split second the car loses communication with whatever system during a flash. EDIT: Doing a bit more digging and came across this http://www.obd-codes.com/u0100 It does seem to go towards the worst possible scenario but it did say the u0100 would probably have a CEL with it |
Quote:
|
Quote:
|
Quote:
I use carista all the time and ran the beta for some time, no issues and no canbus codes like you're getting. Do you leave the adapter in all the time? |
Quote:
|
Quote:
|
Quote:
|
Quote:
The more expensive OBD-II dongles don't do that I believe otherwise this wouldn't be a widespread issue, is your a mini one? |
Quote:
|
Quote:
|
P0700 isn't from flashing, it's from connecting a device to canbus while it's not fully powered down.
Quote:
|
Quote:
[ame="http://www.amazon.com/BAFX-Products-34t5-Bluetooth-Android/dp/B005NLQAHS/ref=sr_1_1?ie=UTF8&qid=1461887769&sr=8-1&keywords=BAFX+obd2"]Amazon.com: BAFX Products 34t5 Bluetooth OBDII Scan Tool for Android Devices: Automotive[/ame] or [ame="http://www.amazon.com/Bluetooth-Products-PIC18F2480-Check-Engine/dp/B01BX3PW9G/ref=sr_1_4?ie=UTF8&qid=1461887769&sr=8-4&keywords=BAFX+obd2"]Amazon.com: Bluetooth OBD2 Scan Tool by BAFX Products, PIC18F2480, For Check Engine Light: Automotive[/ame] |
Quote:
It's totally the first one: [ame="http://www.amazon.com/BAFX-Products-34t5-Bluetooth-Android/dp/B005NLQAHS/ref=sr_1_1?ie=UTF8&qid=1461887769&sr=8-1&keywords=BAFX+obd2"]Amazon.com: BAFX Products 34t5 Bluetooth OBDII Scan Tool for Android Devices: Automotive[/ame] I had the first one after I bought one of the mini units off eBay for super cheap. The mini ones tend to cause these U0 issues as I said before also one morning I got a P1604 although the car has not once missed a beat on start up. After getting and using the BAFX one I had 0 issues with erroneous codes. |
| All times are GMT -4. The time now is 12:06 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
User Alert System provided by
Advanced User Tagging v3.3.0 (Lite) -
vBulletin Mods & Addons Copyright © 2026 DragonByte Technologies Ltd.