DTC codes out the ying yang
#1
Thread Starter
Moderately Differentiated
iTrader: (4)
Joined: Nov 2004
Posts: 27,563
Likes: 3
From: Maryland
DTC codes out the ying yang
My battery died on me the other day. My fault. But I found out the hard way by trying to do a remote start. Well, she went hay wire. Once I got it started, it would never shut off. LOL freaking fracking piece f#$^$% ^%^&%%$#. ANyway, I kinda figured I'd get a module code of some sort, but check these babies out.
B2960 - Sec Sys Sensor Data Incorrect but Valid (History) (Immature)
C0281 - Brake Switch Circuit (History)
B2961 - Unknown (History) (Immature)
P0102 - Mass Air Flow (MAF) Sensor Circuit Low Frequency (SES) (Pending) (Old) (History) (Current) (Immature)
U1096 - Loss of Communications with IPC (History) (Immature)
P0121 - TP Sensor Circuit Insufficient Activity (Old) (Immature)
P0135 - HO2S Heater Performance Bank 1 Sensor 1 (SES) (Pending) (Old) (History) (Current) (Immature)
P0155 - HO2S Heater Performance Bank 2 Sensor 1 (SES) (Pending) (Old) (History) (Current) (Immature)
U1064 - Loss of Communications with DIM (History) (Immature)
P0103 - Mass Air Flow (MAF) Sensor Circuit High Frequency (SES) (Pending) (Old) (History) (Current) (Immature)
Holy freaking crap. Now the MAF codes are supposed to be there. And the P0135 and P0155 are due to headers. (I had them on ignore, but with the 2bar update I forgot to set them back)But the TP Sensor? Brake switch circuit? WTF? You think the actual relay/modules got F-ed up during all this for the "U" codes? Tp sensor? I did tap into the TP wire awhile back for my Wideband 5v input for TPS. I make my gauge yell at me at a certain TPS % and anything above 12.1AFR.
Anybody got any troubleshooting experience with the "U" code crap. How about that security code, "incorrect BUT valid" LOL
B2960 - Sec Sys Sensor Data Incorrect but Valid (History) (Immature)
C0281 - Brake Switch Circuit (History)
B2961 - Unknown (History) (Immature)
P0102 - Mass Air Flow (MAF) Sensor Circuit Low Frequency (SES) (Pending) (Old) (History) (Current) (Immature)
U1096 - Loss of Communications with IPC (History) (Immature)
P0121 - TP Sensor Circuit Insufficient Activity (Old) (Immature)
P0135 - HO2S Heater Performance Bank 1 Sensor 1 (SES) (Pending) (Old) (History) (Current) (Immature)
P0155 - HO2S Heater Performance Bank 2 Sensor 1 (SES) (Pending) (Old) (History) (Current) (Immature)
U1064 - Loss of Communications with DIM (History) (Immature)
P0103 - Mass Air Flow (MAF) Sensor Circuit High Frequency (SES) (Pending) (Old) (History) (Current) (Immature)
Holy freaking crap. Now the MAF codes are supposed to be there. And the P0135 and P0155 are due to headers. (I had them on ignore, but with the 2bar update I forgot to set them back)But the TP Sensor? Brake switch circuit? WTF? You think the actual relay/modules got F-ed up during all this for the "U" codes? Tp sensor? I did tap into the TP wire awhile back for my Wideband 5v input for TPS. I make my gauge yell at me at a certain TPS % and anything above 12.1AFR.
Anybody got any troubleshooting experience with the "U" code crap. How about that security code, "incorrect BUT valid" LOL
#2
I'll almost bet that you can trace most of those codes directly back to the remote start. I know that the remote starts use the brake signal as a shut off, and the security sytem code is almost a no-brainer....probably a module that's needed to make the remote starter compatable with the factory sec system. I think you may have answered your own question with the TPS code.
#3
Thread Starter
Moderately Differentiated
iTrader: (4)
Joined: Nov 2004
Posts: 27,563
Likes: 3
From: Maryland
I checked the tps, still a nice clean connection. no corrosion or any reason to believe it should F up. hmmm
i didn't install the remote start, I guess I should get the instructions and back tract the modules and what not.
i didn't install the remote start, I guess I should get the instructions and back tract the modules and what not.
#4
You probably have the latest version of Hptuners right? I had the same codes and posted up and they all said it was do to the new software reading the bcm codes now too.
http://www.hptuners.com/forum/showth...highlight=hell
http://www.hptuners.com/forum/showth...highlight=hell
#5
Originally Posted by joshluther
You probably have the latest version of Hptuners right? I had the same codes and posted up and they all said it was do to the new software reading the bcm codes now too.
http://www.hptuners.com/forum/showth...highlight=hell
http://www.hptuners.com/forum/showth...highlight=hell
#6
Thread Starter
Moderately Differentiated
iTrader: (4)
Joined: Nov 2004
Posts: 27,563
Likes: 3
From: Maryland
Originally Posted by Nickvrebel
that was my first thought when I read this... try setting the O2 sensor codes where you need them, along with disabling the SES for the MAF (at least temporarily) and see if the SES light illuminates. If not then those codes don't pertain to your vehicle and you can ignore them.
Thread
Thread Starter
Forum
Replies
Last Post
creekrat
Tuning, Diagnostics, Electronics, and Wiring
2
09-10-2015 01:59 AM