Hummer Forums by Elcova

Hummer Forums by Elcova (http://www.elcovaforums.com/forums/index.php)

- General H2 Discussion (http://www.elcovaforums.com/forums/forumdisplay.php?f=6)

- - DTC U1000 (http://www.elcovaforums.com/forums/showthread.php?t=30955)

DTC U1000 Class 2 Communication Malfunction

Can anyone explain this to me? Where is the communication error (Between the programmer and the ECU, two sensors, components, etc.)? Is this a big deal that needs to get fixed ASAP or one of those DTC's that don't really do any harm?

Thanks.

Found this here

http://myweb.accessus.net/~090/dtcobd2n.html#typ

Hope it helps explain.

Easy Ed

This information applies to all GM vehicles Using Class 2 communication.
DTC U1000 or U1255 may set current or history, with or without other DTCs.
These DTCs set when the control module does not receive a message that it was expecting from another control module, and does not know which control module did not send the message.

If the DTC U1000 or U1255 is set in history with other DTCs set current or history, diagnose the other DTCs first.
If the DTC U1000 or U1255 is set current, this usually indicates a module that is currently not communicating or a configuration issue. For example, if the control module is configured for an option (i.e., OnStar, keyless entry, memory mirrors, etc.) that the vehicle does not have, it may expect to receive a message regarding this missing feature. This would usually occur due to the control module being recently replaced and incorrectly set up.
When the DTC U1000 or U1255 is current, the module that is not communicating may not even be listed on the Tech 2 on the Diagnostic Circuit Check /Class 2 Message Monitor list.
If the DTC U1000 or U1255 has set in history without other DTCs, replacing the control module that set the DTC is most likely NOT the solution. The module that has set the code is looking for an input from another module that is not communicating. Because the module did not receive an input that it is expecting to see, it sets a U1000 or U1255 which indicates there was a loss of communications. Look at the customer's concern (i.e., intermittent, erratic tachometer operation). This will probably be a better indication of the control module that is the source of the concern.

Quote:

Originally Posted by Easy Ed

If the DTC U1000 or U1255 is set in history with other DTCs set current or history, diagnose the other DTCs first.
If the DTC U1000 or U1255 is set current, this usually indicates a module that is currently not communicating or a configuration issue. For example, if the control module is configured for an option (i.e., OnStar, keyless entry, memory mirrors, etc.) that the vehicle does not have, it may expect to receive a message regarding this missing feature. This would usually occur due to the control module being recently replaced and incorrectly set up.
When the DTC U1000 or U1255 is current, the module that is not communicating may not even be listed on the Tech 2 on the Diagnostic Circuit Check /Class 2 Message Monitor list.
If the DTC U1000 or U1255 has set in history without other DTCs, replacing the control module that set the DTC is most likely NOT the solution. The module that has set the code is looking for an input from another module that is not communicating. Because the module did not receive an input that it is expecting to see, it sets a U1000 or U1255 which indicates there was a loss of communications. Look at the customer's concern (i.e., intermittent, erratic tachometer operation). This will probably be a better indication of the control module that is the source of the concern.

Ed seems to have all the answers.:D :D

Just bored today and have access to the net :jump:

Quote:

Originally Posted by Easy Ed

Just bored today and have access to the net :jump:

I wasn't knocking you man, I was just stating that you seem to have a wealth of Hummer knowledge, or know where to find it.:beerchug:

jmsspratlin, I know what ya meant bud, not a problem :beerchug:

Easy Ed

Thanks for the response... Well I'm not subscribed to OnStar... Maybe that is it then.

Typically you can ignore any u codes if they are set in history. If it is A current code you need to try and communicate with all modules using a scan tool, if you find a module you cannot communicate with check the data line, power and grounds to that module. If those circuits test ok the module is bad.

The only tool I have is the Hypertech programmer. I had a scan tool for my previous car but it is a specialized computer software only for that.