Weird Issue u0100 u0122

[Riftur]

Originally Posted by FRSBRZGT86FAN

It's totally the first one:
Amazon.com: BAFX Products 34t5 Bluetooth OBDII Scan Tool for Android Devices: Automotive

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.

Thanks for the info. ordering it now.

[phantasticity]

Originally Posted by 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?

I also got the same codes after 2 days of on OFT stage 2 E85. Have you figured out whats wrong or its just something normal from the tune? Someone lemme know about this ASAP please. Some says those codes are really important, so I'm tripping lol

[steve99]

Originally Posted by phantasticity

I also got the same codes after 2 days of on OFT stage 2 E85. Have you figured out whats wrong or its just something normal from the tune? Someone lemme know about this ASAP please. Some says those codes are really important, so I'm tripping lol

U0100 and U0122 have nothing to do with tune. Both those codes are due to communication errors or interruptions on can bus that modules like ecu traction stability dash cluster use to exchange information.

The most likely cause is stuff you plug or unplug into car obd port. Only do that when ignition is off. If you leave oft plugged in make sure cable is sceure its likey your bumping it causing loss of connection for short periods

[Riftur]

Originally Posted by phantasticity

I also got the same codes after 2 days of on OFT stage 2 E85. Have you figured out whats wrong or its just something normal from the tune? Someone lemme know about this ASAP please. Some says those codes are really important, so I'm tripping lol

I never figured it out. It hasn't caused me any issues though. The codes go away after a while. Everything I read says its a communication error or disconnecting the cable to soon. I didn't do either of those things so that's not what caused it. Everytime I apply a new tune it happens again. Do you smell a burning smell coming from the connector on the cable after applying a tune? I did and am curious if you do also.

[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.

I was just about to switch my car over to e85 and was trying to run the gas all the way down. I was monitoring the fuel level with torque and I was doing some full throttle passes when the u0100 and u0122 codes popped up. I am sitting at the e85 pump looking up the codes and freaked. If i put e85 in the car and something happens to the communication to the ECU when flashing I would have a bricked car. I have been planning on putting e85 in my car for a month now. I end up putting in 93 and I just got to work. I did a google search for the codes and this thread which I totally forgot about pops up. <facepalm> The app runs every single day and tells me the codes verbally whenever anything happens. I have not gotten those codes since this thread. Now I have to wait again through another tank! Its such a pain in the butt trying to be by an e85 station when I am completely empty.

[steve99]

Originally Posted by Riftur

I was just about to switch my car over to e85 and was trying to run the gas all the way down. I was monitoring the fuel level with torque and I was doing some full throttle passes when the u0100 and u0122 codes popped up. I am sitting at the e85 pump looking up the codes and freaked. If i put e85 in the car and something happens to the communication to the ECU when flashing I would have a bricked car. I have been planning on putting e85 in my car for a month now. I end up putting in 93 and I just got to work. I did a google search for the codes and this thread which I totally forgot about pops up. <facepalm> The app runs every single day and tells me the codes verbally whenever anything happens. I have not gotten those codes since this thread. Now I have to wait again through another tank! Its such a pain in the butt trying to be by an e85 station when I am completely empty.

Id say your connection to obd port is suspect or the cable isn't plugged into oft correctly. They are comms codes usually caused by intermittent connection. The connection probably goes down when your driving and the cable get bumped by your knee or going over bumps.


a lot of 2013 or earlier cars has dodgy obd ports on the car

[Riftur]

Originally Posted by steve99

Id say your connection to obd port is suspect or the cable isn't plugged into oft correctly. They are comms codes usually caused by intermittent connection. The connection probably goes down when your driving and the cable get bumped by your knee or going over bumps.


a lot of 2013 or earlier cars has dodgy obd ports on the car

Its actually a bluetooth adapter that uses the torque app. I am pretty sure that's what caused it. It must have been loose I am thinking.

[steve99]

Originally Posted by Riftur

Its actually a bluetooth adapter that uses the torque app. I am pretty sure that's what caused it. It must have been loose I am thinking.

sometimes if you start/stop the torque app (or other similar software) abruptly during its interrogations/operation it can cause those can buss error codes


Always best to start/stop software or plug/unplug obd devices when ignition off if you want to avoid those errors. Can (control area network) buss is the communications buss between most of the cars control modules and the obd port sits directly across this shared buss.

[guybo]

Originally Posted by 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?

Are you sure those aren't pending codes? If you didn't get a CEL and the car isn't in limp mode I wouldn't worry about it. Sometimes you can get a pending code that never turns into a real code, never trips a CEL and it's nothing to worry about.

I have a El-Cheapo OBD2 reader and Torque Pro and the biggest issue I have with it are the cheap assed pins on the reader itself. If you look at them they are not even length and they aren't perfectly straight so sometimes they don't connect well and I have to play with it. The occasional CEL for loss of CANBUS communication is not motivation enough for me to spring for a better reader though.

[Riftur]

Originally Posted by guybo

Are you sure those aren't pending codes? If you didn't get a CEL and the car isn't in limp mode I wouldn't worry about it. Sometimes you can get a pending code that never turns into a real code, never trips a CEL and it's nothing to worry about.

I have a El-Cheapo OBD2 reader and Torque Pro and the biggest issue I have with it are the cheap assed pins on the reader itself. If you look at them they are not even length and they aren't perfectly straight so sometimes they don't connect well and I have to play with it. The occasional CEL for loss of CANBUS communication is not motivation enough for me to spring for a better reader though.

I am not sure of anything at this point. I have been getting P000a and P0011 codes which do not trip the CEL. The are the cam shaft position codes. The code pops up on torque app every few weeks when driving the car hard in sport mode. I do feel like the car is performing any differently but sometimes it feels like the transmission stays in gear to long after i let off the gas (like the car is in sport mode when its not). This only happens occasionally. Dont know if its related.

[Spacepeanut34]

I was driving down the highway I was going 65mph at the time I stepped on the gas got up to 75mph my rpm sat at 6.5 and my car started to sound like a vacuum I let off the Gaston a split second then stepped on it again I had no reaction I pulled over to the should and tried to start my car and but it would only crank it wouldn’t turn over I got it towed back home and that’s when I hooked it up to an odm and it gave me a p0700 and u0100 code for the past few days I’ve been trying to figure out what wrong with my car but I’m stuck with no where to go I put the stock header back on and it still won’t turn on anyone have any idea of what’s going on (it’s an automatic with no tune)

[DarkPira7e]

It's easy to get lost and scared with a "won't start" condition. Remember that to run, there are 3 primary needs- fuel, oxygen, and spark.

Test each of these to mark sure you have everything required before jumping all over the electronics and ECM.
Try starting the car by holding the gas to the floor right after it starts cranking. Check your oil to see if it smells like gas if you've been cranking a while. Listen for the fuel pump. Check your ignition and fuel related fuses. Check for vacuum leaks.

[Spacepeanut34]

Originally Posted by DarkPira7e

It's easy to get lost and scared with a "won't start" condition. Remember that to run, there are 3 primary needs- fuel, oxygen, and spark.

Test each of these to mark sure you have everything required before jumping all over the electronics and ECM.
Try starting the car by holding the gas to the floor right after it starts cranking. Check your oil to see if it smells like gas if you've been cranking a while. Listen for the fuel pump. Check your ignition and fuel related fuses. Check for vacuum leaks.

I tried all that my fuel pump and everything else is fine I also heard a pop the last time I tried to start it

[tomm.brz]

those codes are missing communications between the ECUs

for example, the U0100 is pretty insignificant, with ecutek you get it all the time and it won t go away but it s no problem

i suspect anyway an electrical problem or a faulty link or cable somewhere