2007 Chevy Equinox 3.4 V6 CAN Communication Errors

Hello All,

I am very new to working with CAN, I've only worked with OBD and OBD2 and lots of the old school pre-electronics era. I read the codes from my daughter's Equinox and this is what I see... this is a pared down list as there were a slew of duplicates, apparently each module reports it's own set of codes, I whittled it down to remove all of the duplicates but I still have the original list as well.


Airbag Code Scan Results
B0081 Passenger Presence System 1 Erratic (Symptom 0F) - History DTC.
U0140 Lost Communication With Body Control System (Symptom 00) - History DTC.

ABS History Codes
C0040 Right Front Wheel Speed Sensor Circuit Fault (Symptom 00) - History DTC, Warning Indicator Requested.
C0040 Right Front Wheel Speed Sensor Circuit Fault Signal Amplitude < Minimum (Symptom 18) - History DTC, Warning Indicator Requested.
C0551 Option Configuration Error Vin Not Programmed (Symptom 47) - History DTC, Warning Indicator Requested.
C0561 System Disabled Information Stored Invalid Serial Data Received (Symptom 71) - History DTC, Warning Indicator Requested.
C0899 Device # 1 Voltage Low (Symptom 00) - History DTC, Warning Indicator Requested.
U2107 Lost Communication W/Body Control System (Symptom 00) - Current DTC, History DTC, Warning Indicator Requested.
U2107 Lost Communication W/Body Control System (Symptom 00) - History DTC, Warning Indicator Requested.

Body Control Module Code Scan Results October 02, 2016 Body Control Module Code Scan Results
B1000 Electronic Control Unit (ECU) Performance ROM Failure (Symptom 35) - Current DTC, Test Failed Since DTC Clear, History DTC, Test Not Passed Since Power Up, Current DTC Since Power Up.
U0131 Lost Communication With Power Steering Control Module (Symptom 00) - Test Failed Since DTC Clear, History DTC.
U0184 Lost Communication With Radio (Symptom 00) - Test Failed Since DTC Clear, History DTC.
U0214 Lost Communication With Remote Function Actuation (Symptom 00) - Test Failed Since DTC Clear, History DTC.

Engine Code Scan Results
P0300 Engine Misfire Detected (Symptom 00) - Test Failed Since DTC Clear, Test Not Passed Since Power Up.

Passenger Presence System Code Scan Results
U0140 Lost Communication With Body Control System (Symptom 00) - History DTC, Test Not Passed Since Power Up.


I looked on Mitchell1 ( I have a subscription only to this Equinox on the DIY site) and it wasn't much help to me. Could be I don't know what I am doing with that either. Seems like it jumps around a lot. The wheel speed sensor is on order, I tested it according to what ScannerDanner showed in a video for them and it seems to be truly a bad sensor so that much I was able to do. I know Ethernet LAN extremely well and I have worked with PLCs that talk over SERCOS and Profi-BUS and the like so conceptually I know what is happening on the CAN-BUS but I don't have any idea where to start on the communications issue. It seems like the BCM is the common thread and I know it is in the dash kinda under/behind the radio.

The ABS light is on constantly and the Stabilitrak (Traction Control?) is off intermittently, I shoulda put that in the subject line, I will try to edit it.

Thanks in advance,
Gary

Weeeeee, gotta love the pages and pages of codes you get with systems like this, eh?

So, just to be clear, the only symptom right now is the ABS and Stabilitrak lights, correct? I ask because, aside from all the other codes, the lights can easily be explained by the WSS issue alone. All the other codes may be 'chaff', false codes set by stuff like low battery voltage.

Are you able to communicate with the BCM currently? Rather, are there any modules you can't communicate with?

To be completely honest, I never hesitate to clear all codes and recheck in situations like these. Chase the codes that return. It may seem crude, but it's the easiest and fastest way to separate hard faults from false codes.

ABS History Codes
C0899 Device # 1 Voltage Low (Symptom 00) - History DTC, Warning Indicator Requested.

Unless B+ voltage truly is low at the ABS module, then this suggests a battery issue at some point in the past. Again, possibly the catalyst for the rest of the communication codes.

B1000 Electronic Control Unit (ECU) Performance ROM Failure (Symptom 35) - Current DTC, Test Failed Since DTC Clear, History DTC, Test Not Passed Since Power Up, Current DTC Since Power Up.

I would be very interested to see if this one comes back after clearing.

Tyler,

Sorry to be such a newbie, I really don't know how to tell which modules I can/cannot communicate with. If you can give me some hints I will see what I can do. I got those codes with a Verus that I had limited access to but it is back with the owner again so until I can get something of my own I am working blind.

I am getting the Equinox back on the 22nd hopefully to change the wheel speed sensor and the CV shaft, I noticed that it must have a small tear in the boot cuz there's grease coming out of it Oh well, at least that is the kind of stuff I am good at and I have a really nice OTC front-end service kit so it is a treat to pop those tapered pins outta their sockets now. I used to HATE separating tie rod ends and the like but now it's like I get my revenge!

I have been reading and reading TSBs for that vehicle, there are like a hundred or more of them to wade through, but, there is one that specifies how much voltage is the minimum for the EBCM (or is it ECBM?). So you mentioned that too, I have it in mind to use my meter that has max/min and start to see how much it's dropping down to.

I worked on it a while back and had a sensor unplugged, forgot to plug it in, and set a code so I unhooked the battery and left the door open as I read to do. I don't recall if I grounded the battery leads, used a test light, etc between them but I left them off several minutes to clear the codes. Would that REALLY clear them or, is the kind of stuff I am seeing still going to be lurking around it there?

Also, I panicked when upon trying to restart after reconnecting the battery it did nothing, and I mean nothing except I think there was one red light on the dash for like a seat belt or something. No gauge check, no check engine light, no battery light, nothing. And to make matters worse, it would not release the key. I was furiously searching the InterWebs trying to figure out what to do and I read horror story after horror story about people having to have their cars towed to the dealer for a several hundred dollar reflash or a new BCM just because they unhooked their battery. After trying over and over, finally I literally bowed my head in prayer, turned the headlights on, then off, and it started. I have no idea if the Good Lord fixed it for me, if turning the headlights on/off did some good, or, as I seem to have read along the way, enough time had passed for some kind of relearn to take place. But, since that incident I have been really gunshy about working on this thing. What can you tell me about that deal? Is there are right way to do that without it crapping out on me like that?

Thanks Tyler, and it is cool to hear Paul giving kudos to you, Andy and Dylan (I hope I spelled his name correctly)
Gary

rn8849 wrote: Tyler,

Sorry to be such a newbie, I really don't know how to tell which modules I can/cannot communicate with. If you can give me some hints I will see what I can do. I got those codes with a Verus that I had limited access to but it is back with the owner again so until I can get something of my own I am working blind.

Ah, sorry sir, I probably should have backed up a couple steps :blush: Really, the fact that you got codes out of the BCM (and the other modules) is a good sign. Mostly, I was referring to using the scan tool to communicate with individual modules, i.e. pointing the scanner at the BCM directly (or any other module you were concerned about).

I worked on it a while back and had a sensor unplugged, forgot to plug it in, and set a code so I unhooked the battery and left the door open as I read to do. I don't recall if I grounded the battery leads, used a test light, etc between them but I left them off several minutes to clear the codes. Would that REALLY clear them or, is the kind of stuff I am seeing still going to be lurking around it there?

Unfortunately, these are the kind of codes you'll see at times after a battery disconnect. Some makes are more sensitive to this than others.

Just this week, I was working on an Infiniti G35 that got a battery and a starter. On the first key cycle after the new battery, the PCM spit out a P0603 ECM ROM Error Cleared it, cycled the key again, and all was well! Or, the Prius I was doing a wheel alignment on when the battery went low, and wouldn't shift out of park afterwards :blink: Low battery voltage does STRANGE things to modules.

After trying over and over, finally I literally bowed my head in prayer, turned the headlights on, then off, and it started. I have no idea if the Good Lord fixed it for me, if turning the headlights on/off did some good, or, as I seem to have read along the way, enough time had passed for some kind of relearn to take place. But, since that incident I have been really gunshy about working on this thing. What can you tell me about that deal? Is there are right way to do that without it crapping out on me like that?

:lol: I'm laughing 'cause I've been there! I'm not positive how the headlights are related, to be honest, but I can totally understand being nervous about work on it after an experience like that! I don't see that you did anything wrong to cause it. The best advise I can offer is to only disconnect batteries when absolutely necessary, and be prepared for weirdness afterwards.

Thanks Tyler, and it is cool to hear Paul giving kudos to you, Andy and Dylan (I hope I spelled his name correctly)

Thanks, sir! Noah is in there, too. We appreciate the shoutouts in the regular videos

Tyler wrote: So, just to be clear, the only symptom right now is the ABS and Stabilitrak lights, correct?

I'm sorry, I see that I never answered this question... I am not really sure, there is also that P0300 I see. I had that code some weeks ago, before beginning the ScannerDanner Premium videos, so I bought some plugs and wires. Wanting to know what was the actual cause I changed the plugs first, cleared the codes and had my daughter drive it for a week and it came back so I changed the wires and haven't had the code since, my lil Actron doesn't show even a Pending Code for it so hopefully it's taken care of. But, I would really like to know what is meant by, "Test Failed Since DTC Clear, Test Not Passed Since Power Up" in that list of codes, specifically, which power up? Since I reconnected the battery? The last key cycle? Some monitor it runs?

And I had to laugh when recently watching one of Paul's videos when he pulled the plugs outta some vehicle and like 3 were NGK and the rest were Delco, I think. Same deal for me, 3 were Bosch maybe, something other than Delco and three were Delco, three wires were aftermarket and three were OEM. I guess it was just too much trouble with those unimportant back three cylinders... :dry: So, they're all OEM stuff now.

So, about that battery reconnect, generally speaking there is not normally any lasting impact? Is that right?

I'd like to mention one scary thing I read on Mitchell for this Equinox... hard to believe this but here is a paraphrase since the quote would be copyrighted: If you disconnect the BCM ground with the battery connected you will cause internal damage to the BCM and connected modules. Gee whiz, that's awful, who would ever suspect that?

And I apologize to Noah, I submitted my last post and was reading some other and saw his name and realized I had forgotten to mention him. I really appreciate all of you guys taking time to help us so much. I'm hoping to contribute along the way too.

-Gary

.And I apologize to Noah, I submitted my last post and was reading some other and saw his name and realized I had forgotten to mention him.

Huh, what? Did I miss something? :huh: lol!

No apology nessecary! I'm just here to learn like everyone else.

rn8849 wrote: But, I would really like to know what is meant by, "Test Failed Since DTC Clear, Test Not Passed Since Power Up" in that list of codes, specifically, which power up? Since I reconnected the battery? The last key cycle? Some monitor it runs?

Ah yeah, that's a feature of GM's. They add those sub-descriptions to their trouble codes, expanding on what we know of as 'history' and 'current' DTCs.

Here's an example of a Saturn Vue I looked at last week:



The P0420 in the Engine module is both a Current and History code. The 'Test Not Passed Since Power Up' means it hasn't passed this key cycle. 'Test Failed Since DTC Clear' always sounded always sounded needlessly self-explanatory to me :huh:

The transmission codes, on the other hand, are History only. Note the U2116 in the HVAC module - the code is there, but no communication issue exists.

And I had to laugh when recently watching one of Paul's videos when he pulled the plugs outta some vehicle and like 3 were NGK and the rest were Delco, I think. Same deal for me, 3 were Bosch maybe, something other than Delco and three were Delco, three wires were aftermarket and three were OEM. I guess it was just too much trouble with those unimportant back three cylinders... :dry: So, they're all OEM stuff now.

:lol: I've always heard these called 'Sunny side tune-ups'. I sort of get it if an intake has to come off, but they're out in the open on this 3.4L *rolls eyes*

So, about that battery reconnect, generally speaking there is not normally any lasting impact? Is that right?

Absolutely right. Lots of cars get their batteries disconnected/reconnected and run like nothing ever happened.

I'd like to mention one scary thing I read on Mitchell for this Equinox... hard to believe this but here is a paraphrase since the quote would be copyrighted: If you disconnect the BCM ground with the battery connected you will cause internal damage to the BCM and connected modules. Gee whiz, that's awful, who would ever suspect that?

I hadn't seen that TSB before, but I do know from replacing other GM BCM's that the service info specifies the order in which the BCM connectors should be reconnected during module replacement. I always figured it had something to do with which connectors had the power/ground circuits, and connecting them last so that the module would see everything connected when it got powered up.

Like you said, though, you'd have no reason to think it mattered until you did the research.

Tyler wrote: :lol: I've always heard these called 'Sunny side tune-ups'. I sort of get it if an intake has to come off, but they're out in the open on this 3.4L *rolls eyes*

hahaha, I love it! Thanks for the information, too. What kind of scan tool were you using? Did it output those codes in that format or did you have to do it all manually?

Noah wrote:

.And I apologize to Noah, I submitted my last post and was reading some other and saw his name and realized I had forgotten to mention him.

Huh, what? Did I miss something? :huh: lol!

No apology nessecary! I'm just here to learn like everyone else.

yeah, well, I just rolled through all the notes you've entered for the Premium videos, great job and that has to be a lot of effort.

Thanks Noah!

rn8849 wrote:

Tyler wrote: :lol: I've always heard these called 'Sunny side tune-ups'. I sort of get it if an intake has to come off, but they're out in the open on this 3.4L *rolls eyes*

hahaha, I love it! Thanks for the information, too. What kind of scan tool were you using? Did it output those codes in that format or did you have to do it all manually?

That was a Modis Ultra, but I'm pretty sure any of the new Solus or Modis models will generate code scans like that. I think the Verus will make similar reports, too.