Weird Issue u0100 u0122

[Riftur]

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?

[Tectoniic]

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

[Riftur]

Originally Posted by Tectoniic

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.

Last night I used Carista to turn off the seat belt beep and day time running head lights and a couple other settings. I wonder if one of those settings I changed could be causing this. I only changed options like those so i really don't think so.

[Tectoniic]

Originally Posted by Riftur

Last night I used Carista to turn off the seat belt beep and day time running head lights and a couple other settings. I wonder if one of those settings I changed could be causing this. I only changed options like those so i really don't think so.

Yeah, I wouldn't think those would have anything to do with it but I haven't messed with carista at all

[FRSBRZGT86FAN]

Originally Posted by Riftur

Last night I used Carista to turn off the seat belt beep and day time running head lights and a couple other settings. I wonder if one of those settings I changed could be causing this. I only changed options like those so i really don't think so.

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?

[Riftur]

Originally Posted by FRSBRZGT86FAN

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?

Yes cause I monitor the car with torque most of the time.

[FRSBRZGT86FAN]

Originally Posted by Riftur

Yes cause I monitor the car with torque most of the time.

That explains the U0 errors, I got the same along with some sort of startability error P1604 once with a bluetooth dongle OBD2, alot of them do that.

[Riftur]

Originally Posted by FRSBRZGT86FAN

That explains the U0 errors, I got the same along with some sort of startability error P1604 once with a bluetooth dongle OBD2, alot of them do that.

That's the first time it's happened and I have been using torque like this for months now. I am very glad you had this issue. I was about to flash back to stock and see if it fixed it but the car runs much better since I tuned it. Lol

[FRSBRZGT86FAN]

Originally Posted by Riftur

That's the first time it's happened and I have been using torque like this for months now. I am very glad you had this issue. I was about to flash back to stock and see if it fixed it but the car runs much better since I tuned it. Lol

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?

[Riftur]

Originally Posted by FRSBRZGT86FAN

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?

mini and cheap lol

[FRSBRZGT86FAN]

Originally Posted by Riftur

mini and cheap lol

That explains it , the BAFX one I have doesn't do that

[Wayno]

P0700 isn't from flashing, it's from connecting a device to canbus while it's not fully powered down.

Originally Posted by Tectoniic

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

[Riftur]

Originally Posted by FRSBRZGT86FAN

That explains it , the BAFX one I have doesn't do that

I assume one of these. Hope its not the second 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]

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]

[FRSBRZGT86FAN]

Originally Posted by Riftur

I assume one of these. Hope its not the second one.

Amazon.com: BAFX Products 34t5 Bluetooth OBDII Scan Tool for Android Devices: Automotive

or

Amazon.com: Bluetooth OBD2 Scan Tool by BAFX Products, PIC18F2480, For Check Engine Light: Automotive

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.