2007 Suburban No Obd Communication. Not A Fuse!

[[email protected]]

The vehicle: 2007 Chevy Suburban LT3, 2WD, 5.3L, 3GNFC16J17G132690

 

The problem: Bought this vehicle used out-of-state. When it arrived, check engine light was on (constant). Took it to one friend, scanner would not communicate. Checked for power-- no fuses blown, good ground on pin 5 (think it was 5), +12V on 16. Took it to another friend, no communication with the scanner. My friends work at large shops, with decent scanners.

 

Consensus was either a broken wire to the computer, or the computer is faulty and went into 'limp mode' and turned the mil on.

 

Curious as to what the GM Tech thinks? I have an appointment with the local dealer on Wednesday. If a computer is required, would this be a warranty repair? Vehicle is just over 2 years in service and has 39,600k miles.

 

EDIT: Forgot to mention that the vehicle runs fine, no problems. Just like new.

 

Thanks,

Tim

[minibike132]

The vehicle: 2007 Chevy Suburban LT3, 2WD, 5.3L, 3GNFC16J17G132690

 

The problem: Bought this vehicle used out-of-state. When it arrived, check engine light was on (constant). Took it to one friend, scanner would not communicate. Checked for power-- no fuses blown, good ground on pin 5 (think it was 5), +12V on 16. Took it to another friend, no communication with the scanner. My friends work at large shops, with decent scanners.

 

Consensus was either a broken wire to the computer, or the computer is faulty and went into 'limp mode' and turned the mil on.

 

Curious as to what the GM Tech thinks? I have an appointment with the local dealer on Wednesday. If a computer is required, would this be a warranty repair? Vehicle is just over 2 years in service and has 39,600k miles.

 

EDIT: Forgot to mention that the vehicle runs fine, no problems. Just like new.

 

Thanks,

Tim

 

Are you saying you can't communicate with any module?

[[email protected]]

Are you saying you can't communicate with any module?

 

On the first try I saw the screen and it was just a big red 'X' and said something to the effect of "cannot communicate, check cable"

 

I wasn't there the second time but my friend said the scanner would light up but would not communicate.

 

I am thinking this means it cannot communicate at all, with any module. But I'm not too familiar with obd.

 

Could it be the scanners are not CAN compatible? I thought the purpose of obd was to be universal, so I am assuming that any obd-ii scanner should work? Again, not really familiar with this, but one friend works for a municipality and has a scanner there, another for a bus garage. I;m assuming their equipment is compatible.

 

Tim

[minibike132]

I thought the purpose of obd was to be universal, so I am assuming that any obd-ii scanner should work?

 

That is the purpose for obd. However we have moved on to the Controller Area Network or CAN on everything 06 and newer. The tech-2 needs a CANdi module installed between the scan tool and the truck. I assume that the other scan tool manufacturers have a similar module that needs to be added to the tool itself before communications can happen with your truck.

 

 

 

http://en.wikipedia.org/wiki/Controller_Area_Network

[[email protected]]

I thought the purpose of obd was to be universal, so I am assuming that any obd-ii scanner should work?

 

That is the purpose for obd. However we have moved on to the Controller Area Network or CAN on everything 06 and newer. The tech-2 needs a CANdi module installed between the scan tool and the truck. I assume that the other scan tool manufacturers have a similar module that needs to be added to the tool itself before communications can happen with your truck.

 

 

 

http://en.wikipedia.org/wiki/Controller_Area_Network

 

 

I assumed the scanner was compatible as the municipality has a police fleet and dpw fleet, all of which receive several new vehicles each year.

 

 

I ordered an Actron 9185, so I am going to see for myself.

 

Thanks for your help. Hopefully it's just a protocol problem. I'll know for sure on wednesday!

 

Tim