Chevrolet U1000 Code: Class 2 Communication Malfunction
A module on an older GM's Class 2 data line couldn't communicate, so modules stopped hearing each other.
At a glance
Severity: Moderate
- Meaning
- Class 2 Communication Malfunction
- System
- Module Communication · Network
- Safe to drive?
- With caution
- Typical repair cost
- $0–$900
- DIY difficulty
- Moderate
Before GM moved to CAN networks, most of its vehicles tied their modules together with Class 2, a single-wire serial data line that runs at 10.4 kbit/s and pulses between 0 and about 7 volts. U1000 is stored when a module can't send or receive on that line properly, and it's typical of 1999–2007 Silverado and Sierra, 2000–2006 Tahoe and Suburban, TrailBlazer and Envoy, Impala, Monte Carlo, S-10 and Corvette of that era. Because all modules share one wire, a single shorted module, a chafed wire or a bad splice can bring the whole network down: the gauges quit, the scan tool can't connect and, on some models, the theft system prevents starting. Newer CAN-based Chevrolets report network faults with U0xxx codes instead, so U1000 on a late model may carry a different, model-specific meaning.
Can I keep driving? If the engine runs and the gauges work, drive carefully to a shop; you may lose the speedometer, fuel gauge and warning lights without notice. If the gauges are dead or the truck is hard to start, have it towed rather than risk getting stranded.
How to read U1000
- U Network
- 1 Manufacturer-specific
- 0 Module Communication
- 00 Specific fault
Symptoms
- Several gauges drop to zero or freeze at once
- Scan tool reports no communication with any module
- Crank-no-start or security light on after the fault appears
- Automatic transmission shifts hard or stays in one gear
- Door chimes, lights or 4WD indicators behaving erratically
- Fault comes and goes over bumps or in wet weather
Possible causes
Ranked by how often each cause is behind this code (editorial estimate).
- Chafed or broken Class 2 wire, often under the dash, at the door sill or near the fuse block
- One failing module pulling the whole Class 2 line to ground or voltage
- Corroded ground or splice pack connection behind the dash
- Aftermarket remote start, radio interface or alarm tapped into the data line
- Low battery voltage or loose battery cables during cranking
- Water intrusion at a module or connector (cowl or door leaks)
Diagnosis step by step
Check battery and main grounds
Make sure the battery rests near 12.6 V and the cables and body grounds are clean and tight. Class 2 modules misbehave when supply voltage dips, so rule this out before chasing wiring.
Tools: Multimeter
Check the data line at the DLC
On GM vehicles of this era the Class 2 line is pin 2 of the diagnostic connector under the dash. With the key on, a meter on pin 2 should show a small, constantly changing voltage; a steady 0 V points to a short to ground or no module transmitting, and a steady reading near battery voltage points to a short to power.
Tools: Multimeter, Flashlight
Look for aftermarket additions
Remote starters, stereo interfaces and trackers often splice into Class 2. Unplug or disconnect any such device and recheck communication before going further.
Tools: Flashlight, Screwdriver
Isolate modules one at a time
With the key off, unplug one module at a time (or remove the comb from the Class 2 splice pack where fitted) and recheck the line. When the line comes back to life after a module is unplugged, that module or its branch wiring is shorting the bus.
Tools: Multimeter, Screwdriver
Inspect known chafe points
Follow the harness at the driver's kick panel, door sill, steering column and underhood fuse block, and look for rubbed-through insulation, green corrosion or water marks. Repair any damaged wire with soldered, sealed splices.
Tools: Flashlight, Pliers
Clear codes and verify every module talks
Once the line is restored, scan every module, clear stored U-codes and confirm gauges, chimes and the security light work. Codes in several modules that don't come back were just the echo of the network outage.
Tools: OBD-II scanner
Where the parts are
- 1Battery
- 2Alternator
- 3Engine computer (ECM)
- 4CAN bus
- 5Transmission
- 6Wheel speed sensor
- 7High-voltage battery
Repair options & costs
| Repair | DIY? | Estimated cost |
|---|---|---|
| Clean battery cables and main grounds | Yes | $0–$120 |
| Remove or correctly rewire aftermarket accessory | Yes | $50–$250 |
| Repair chafed Class 2 wiring or splice pack | No | $150–$450 |
| Replace a module that shorts the bus (with programming) | No | $300–$900 |
Rough US estimates for parts and labor; shop rates vary by region. Not a quote.
Emissions / smog test impact
Depends
U1000 alone doesn't always turn on the check engine light, but if the data line is down the testing station usually can't communicate with the PCM and the vehicle can't pass an OBD emissions test until the network is repaired.
Frequently asked questions
What does 'Class 2' mean?
It's the name of GM's older single-wire data network used on most of its vehicles from the mid-1990s into the late 2000s. All modules share that wire, which is why one fault can knock out many systems at once.
Why can't my scan tool connect when U1000 is present?
On these vehicles the scan tool talks to the modules through the same Class 2 line. If the line is shorted, no module can answer, so you often only see U1000 in history after the fault has been fixed or is intermittent.
Why does my truck crank but not start with this fault?
The theft-deterrent check between the body module and the engine computer travels over Class 2. With the line down, the engine computer doesn't get its password and may block fuel, even though nothing is wrong with the engine.
Could my remote starter be causing U1000?
Yes. Many installations connect to the data line to read door locks or tach signal, and a poor splice or a failing interface module can load down the whole network. Disconnecting it is one of the first tests.
Sources
- Manufacturer public service information (cross-checked)
- Methodology: How We Build Code Pages · Data Sources We Use · Editorial Policy