Trouble Codes HELP
#1
TECH Enthusiast
Thread Starter
iTrader: (4)
Join Date: May 2005
Location: Sugar Hill, GA
Posts: 650
Likes: 0
Received 0 Likes
on
0 Posts
Trouble Codes HELP
P0300 - Engine Misfire Detected (Old) (History) (Immature)
P0748 - Pressure Control Solenoid Circuit Electrical (History) (Immature)
U1000 - Class 2 Communication Malfunction (History) (Immature)
U1064 - Loss of Communications with DIM (History) (Immature)
Anyone know what this means? this is the DTC off HPTuners.
P0748 - Pressure Control Solenoid Circuit Electrical (History) (Immature)
U1000 - Class 2 Communication Malfunction (History) (Immature)
U1064 - Loss of Communications with DIM (History) (Immature)
Anyone know what this means? this is the DTC off HPTuners.
#3
TECH Apprentice
iTrader: (1)
Join Date: Nov 2005
Location: Daytona Beach
Posts: 310
Likes: 0
Received 0 Likes
on
0 Posts
Hpt doesnt clear any codes other than pcm tcm. You are and most everyone here is getting Network codes "underbody" Uxxxx that wont clear. Its normal and no further diag should be wasted. This usually indicates a module that is currently not communicating. For example, if the control module is configured for an option. i.e., OnStar, keyless entry, memory mirrors, or a ton of other things that the vehicle does not have, it may expect to receive a message regarding this missing feature and set these codes.
#5
TECH Enthusiast
Thread Starter
iTrader: (4)
Join Date: May 2005
Location: Sugar Hill, GA
Posts: 650
Likes: 0
Received 0 Likes
on
0 Posts
actually I was running 2.11, which was a 2.12 beta. Yeah, after doing some research I determined that. Thanks for the info everyone.
Anyone have any ideas why I would be pulling a misfire code randomly every 1k miles ish?
Anyone have any ideas why I would be pulling a misfire code randomly every 1k miles ish?
#6
TECH Enthusiast
Thread Starter
iTrader: (4)
Join Date: May 2005
Location: Sugar Hill, GA
Posts: 650
Likes: 0
Received 0 Likes
on
0 Posts
Ok, So On my way home from work today I threw another P0300. Now, with that, I am starting to look for what is causing the problem...Random Multiple Misfires two times in two outings is not cool. So I think I am gonna check my MAF and o2 Sensor Connections, maybe look for a melted wire. Then, I am am going to clean the MAF with electrical contact cleaner and see if that helps.
BTW, the Code has only appeared when I am cruising easy in the truck and it seems to run fine when I am running it hard. I am thinking I have a loose o2 connection or a melted wire.
BTW, the Code has only appeared when I am cruising easy in the truck and it seems to run fine when I am running it hard. I am thinking I have a loose o2 connection or a melted wire.
#7
Moderately Differentiated
iTrader: (4)
Originally Posted by 1slowsilverado
Hpt doesnt clear any codes other than pcm tcm. You are and most everyone here is getting Network codes "underbody" Uxxxx that wont clear. Its normal and no further diag should be wasted. This usually indicates a module that is currently not communicating. For example, if the control module is configured for an option. i.e., OnStar, keyless entry, memory mirrors, or a ton of other things that the vehicle does not have, it may expect to receive a message regarding this missing feature and set these codes.
Trending Topics
#8
TECH Apprentice
iTrader: (1)
Join Date: Nov 2005
Location: Daytona Beach
Posts: 310
Likes: 0
Received 0 Likes
on
0 Posts
Well yes it is common especialy the generic serial codes U1000 or U1255. (generic loss of communication) Witch is basicaly saying there is a problem with a module (Noid) in the Class 2 data line but we're not sure which one. Most common cause would be a moduel looking for a SOH Message that doesnt exist. Now I have a high end scan tool I use that can look for active modules to see if this is false or if further diag is needed. With HPT we cant real do anything except read the codes, Witch some think is cool but there are other functions that are needed to make this useful IMO. Not all Serial codes are BS, They do have a use in diagnostics if you are having issues, But its n ot uncommon for them to set.
Last edited by 1slowsilverado; 07-10-2006 at 10:52 PM.
#9
TECH Apprentice
iTrader: (1)
Join Date: Nov 2005
Location: Daytona Beach
Posts: 310
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Injected1
Ok, So On my way home from work today I threw another P0300. Now, with that, I am starting to look for what is causing the problem...Random Multiple Misfires two times in two outings is not cool. So I think I am gonna check my MAF and o2 Sensor Connections, maybe look for a melted wire. Then, I am am going to clean the MAF with electrical contact cleaner and see if that helps.
BTW, the Code has only appeared when I am cruising easy in the truck and it seems to run fine when I am running it hard. I am thinking I have a loose o2 connection or a melted wire.
BTW, the Code has only appeared when I am cruising easy in the truck and it seems to run fine when I am running it hard. I am thinking I have a loose o2 connection or a melted wire.
#10
TECH Apprentice
iTrader: (1)
Join Date: Nov 2005
Location: Daytona Beach
Posts: 310
Likes: 0
Received 0 Likes
on
0 Posts
Also another thing about serial codes, They will set during programing. When the ignition switch is in RUN, each module communicating on the class 2 serial data line sends a state of health (SOH) message every two seconds to ensure that the module is operating properly. When a module stops communicating on the class 2 serial data line, for example if the module loses power or ground, the SOH message it normally sends on the data line every two seconds disappears. Other modules on the class 2 serial data line, which expect to receive that SOH message, detect its absence; those modules in turn set an internal DTC associated with the loss of SOH of the non-communicating module.