08-10 SS Turbocharged General Discussion Discuss the 2008 - 2009 Chevy Cobalt SS Turbocharged. On sale since the second quarter of 2008.

fed up with this...

Thread Tools
 
Search this Thread
 
Old 06-09-2012, 09:01 PM
  #1  
Senior Member
Thread Starter
 
steven2008ss's Avatar
 
Join Date: 06-03-09
Location: NY
Posts: 1,383
Likes: 0
Received 0 Likes on 0 Posts
fed up with this...

OK, I put my new o2 sensor in and I was one monitor away and as soon as I plg my scanner in it gives me the code U0073. WTF this is happening again!??!?!

Just to test it I erased it, drove home from my girlfriends house plugged the scanner in with the car on and the light came on as soon as I hit the sync button, WTF is up with this ****???

PLEASE PLEASE PELASE help, i have inspection due this month.
Old 06-09-2012, 09:03 PM
  #2  
Senior Member
iTrader: (7)
 
bratboy90's Avatar
 
Join Date: 06-12-11
Location: Elk River, MN
Posts: 1,118
Likes: 0
Received 5 Likes on 5 Posts
Seems like its part of owning an LNF. Sorry, I honestly have no valuable input.

So friendly BUMP.
Old 06-09-2012, 10:31 PM
  #3  
Senior Member
 
Chevrolet Cust Svc's Avatar
 
Join Date: 07-30-10
Location: Detroit, Michigan USA
Posts: 1,027
Likes: 0
Received 0 Likes on 0 Posts
I'm sorry that I'm not able to provide any technical insight into the code that your Cobalt is currently showing; hopefully a member of the SS community will jump on soon for you with more information. Otherwise, if I can check into warranty or recall info or if you decide to work with a dealership please send me a private message and I'll do my best!
Sarah
GM Customer Service
Old 06-09-2012, 10:38 PM
  #4  
Senior Member
iTrader: (1)
 
northvibe's Avatar
 
Join Date: 06-07-06
Location: Minnesota
Posts: 14,124
Received 11 Likes on 10 Posts
You know you have more than 1 o2 sensor?

Dude you didn't even take the advice from your first post.....
https://www.cobaltss.net/forums/08-1...-u0073-267815/

Go get a tch2 scan done, it's a comm error. May not even be a o2
Old 06-09-2012, 11:04 PM
  #5  
Junior Member
iTrader: (1)
 
Validater's Avatar
 
Join Date: 03-25-11
Location: Langley BC
Posts: 482
Likes: 0
Received 0 Likes on 0 Posts
I'm not sure how you read a U code. But if you do have one of those expensive scanners, I'm not sure why you weren't able to look the code up. Anyways, Here you go. Your welcome.



DTC U0073

Circuit Description

The GMLAN serial data circuits are controller area network (CAN) high and/or low speed serial data buses used to communicate information between the control modules. Typical data transmission speeds must be high enough to ensure that a required real-time response is maintained. There are two different types of GMLAN serial data circuits, the High speed 2-wire circuit and Low speed single wire circuit. Refer to Data Link References (See: Powertrain Management\Computers and Control Systems\Information Bus\Testing and Inspection\Initial Inspection and Diagnostic Overview) for the complete description of the buses used on this vehicle. The GMLAN serial data circuits also communicate directly to the data link connector (DLC). Messages are interpreted by the externally connected CANdi module which acts as a transceiver for the scan tool.

Modules connected to the GMLAN serial data circuits monitor communications during normal vehicle operation, where operation information is exchanged among the modules. All the modules on the GMLAN networks, maintain a transmit error counter (TEC) and a receive error counter (REC). The counter values increase with detected errors and will decrease with error-free messages. If the TEC value exceeds 255, the controller removes itself from the network and DTC U0073 will result.

DTC Descriptor

This diagnostic procedure supports the following DTC:

DTC U0073 Controller Area Network (CAN) Bus Communication

Conditions for Running the DTCs

Supply voltage to the modules are in the normal operating range.
The vehicle is in the RUN power mode.
Conditions for Setting the DTC

The module setting the DTC has attempted to establish communications on the GMLAN circuits for more than 7 times.

Action Taken When the DTCs Sets

The module suspends all message transmission.
The module uses default values for all parameters received on the serial data circuits.
The module inhibits the setting of all other communication DTCs.
Conditions for Clearing the DTC

A current DTC clears when the malfunction is no longer present.
A history DTC clears when the module ignition cycle counter reaches the reset threshold, without a repeat of the malfunction.
Diagnostic Aids

This DTC cannot be retrieved with a current status. Diagnosis of a current DTC is accomplished via the symptom, Scan Tool Does Not Communicate with High and/or Low Speed GMLAN Device. Refer to Control Module References (See: Testing and Inspection\Programming and Relearning) for the correct procedure for the specific module(s) and the busses they use to communicate.
An intermittent condition is likely to be caused by a short on the GMLAN serial data circuits. Use the Scan Tool Does Not Communicate with High and/or Low Speed GMLAN Device procedure in order to isolate an intermittent condition. Refer to Control Module References (See: Testing and Inspection\Programming and Relearning) for the correct procedure for the specific modules.
Old 06-09-2012, 11:07 PM
  #6  
Junior Member
iTrader: (1)
 
Validater's Avatar
 
Join Date: 03-25-11
Location: Langley BC
Posts: 482
Likes: 0
Received 0 Likes on 0 Posts
I just read that fully. All I can say is, I hope you have warranty!
Old 06-09-2012, 11:17 PM
  #7  
Senior Member
 
Sonicyeller's Avatar
 
Join Date: 05-30-11
Location: Cheyenne, WY
Posts: 545
Likes: 0
Received 0 Likes on 0 Posts
Here's my question to the original poster -- when did the problem start occuring? Any mods done that immediately afterward caused a fault?
Old 06-10-2012, 11:46 AM
  #8  
Senior Member
Thread Starter
 
steven2008ss's Avatar
 
Join Date: 06-03-09
Location: NY
Posts: 1,383
Likes: 0
Received 0 Likes on 0 Posts
it only happens when i plug in my scanner never happens any other time, and I know my old post and the dealership charges you just to hook the shitty scanner up
Old 06-10-2012, 11:58 AM
  #9  
Platinum Member
Platinum Member
 
09CobaltSS1's Avatar
 
Join Date: 04-12-09
Location: Connecticut
Posts: 4,910
Received 15 Likes on 13 Posts
Originally Posted by steven2008ss
it only happens when i plug in my scanner never happens any other time, and I know my old post and the dealership charges you just to hook the shitty scanner up
It's not so shitty of a scanner when it fixes your issue..
Old 06-10-2012, 12:06 PM
  #10  
Senior Member
iTrader: (1)
 
nhanson's Avatar
 
Join Date: 05-07-08
Location: Minnesota
Posts: 6,428
Likes: 0
Received 2 Likes on 1 Post
Tech 2s are shitty scanners?

Maybe its a problem with your scanner that causes the issue. try another scanner?

Why would you think a "U" code would be an O2 sensor?
Old 06-10-2012, 02:23 PM
  #11  
Senior Member
iTrader: (1)
 
northvibe's Avatar
 
Join Date: 06-07-06
Location: Minnesota
Posts: 14,124
Received 11 Likes on 10 Posts
Non dealers have tech2's also........
Old 06-11-2012, 11:05 AM
  #12  
Senior Member
Thread Starter
 
steven2008ss's Avatar
 
Join Date: 06-03-09
Location: NY
Posts: 1,383
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by nhanson
Tech 2s are shitty scanners?

Maybe its a problem with your scanner that causes the issue. try another scanner?

Why would you think a "U" code would be an O2 sensor?
I'm thinking its my scanner too, I was only checking my o2 because I replaced it and I am trying to ready all of my monitors for inspection.

Originally Posted by 09CobaltSS1
It's not so shitty of a scanner when it fixes your issue..
You know what I meant smartass.. =]

Originally Posted by northvibe
Non dealers have tech2's also........
Not that many apparently...plus the code hasnt come back I am not hooking my scanner up anymore, cause I honestly think thats the problem, it never comes up on its own when I drive, its only I connect so yea I'm done using it.
Old 06-11-2012, 12:15 PM
  #13  
Senior Member
 
Stamina's Avatar
 
Join Date: 02-09-09
Location: Tejas
Posts: 4,377
Likes: 0
Received 5 Likes on 5 Posts
I had a problem with a U0073 when my Dashdaq cable going to the OBDII port went bad. It developed a short, causing things to freak out due to intermittent communications over the network caused by the short. When using a different cable for a scanner or yet another cable for the Dashdaq, it never popped up with either of them. Your cable may be bad.

Errors popping up due to network communication issues:
U0073 - YouTube

Codes cleared and then car freaking out again at idle:
U0073 (Part 2) - YouTube

The idle was completely constant in this video, but the gauge was freaking out.
Old 06-11-2012, 01:36 PM
  #14  
Senior Member
 
FasterIsBetter's Avatar
 
Join Date: 05-15-10
Location: South Charleston, WV
Posts: 3,997
Likes: 0
Received 2 Likes on 2 Posts
Try not plugging in the scanner with it running. Just put the key in the run position without it being started.
Old 06-11-2012, 01:49 PM
  #15  
Nothin Stock
iTrader: (46)
 
gotboost?17's Avatar
 
Join Date: 12-10-09
Location: Windsor ON/Detroit MI
Posts: 4,918
Likes: 0
Received 2 Likes on 2 Posts
Sub'd
Old 06-12-2012, 03:03 PM
  #16  
Senior Member
Thread Starter
 
steven2008ss's Avatar
 
Join Date: 06-03-09
Location: NY
Posts: 1,383
Likes: 0
Received 0 Likes on 0 Posts
Thanks for all the info guys! I passed inspection today, so I dont give a **** anymore if it comes up lmfao....

I love passing without cats =]
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Hutch
Canadian Mid East
4
04-06-2006 09:23 AM
Cobalt443
Turbo Tech Racing
4
01-27-2006 02:18 PM



Quick Reply: fed up with this...



All times are GMT -4. The time now is 12:21 PM.