Jump to content

Recommended Posts

Posted

Sharing experience for your info and any ideas you might have.  My shiny new 2021 GMC Sierra Denali 3.0 Duramax Diesel with 4900 miles on it has been losing its mind.  I get multiple, rotating DIC messages: “Service ESC”, “Service Parking Brake”,  Service ABS”, “Adaptive Cruise Control Disabled”,  Steering Assist Reduced Drive with Care”, . . . ). The error messages come with other “benefits” besides disabled cruise control. I also enjoy no GPS signal, no Blind Spot sensors, no collision avoidance sensors, and who knows what else.   

 

Fortunately, the diagnostic codes were stored so the tech could see them, and I provided video of the DIC messages each time, too.  They are on their 4th attempt to repair it now.  First time, they replaced the Exhaust Particulate Matter Sensor (4025920) .  Second time, they tried the same thing and replaced the Exhaust Particulate Matter Sensor, again.  The 3rd time, they inspected the engine harness but found no damage so they replaced the pigtail to the  Exhaust Particulate Matter Sensor and followed an 8 hr rest cycle and road test protocol.  It worked for about 2 hours after I picked it up, then everything lit up again.   This (4th) time, they are saying they will replace the entire wiring harness per GM’s direction.   I do not want to use Florida’s Lemon Law, but I am starting the process just to be safe.

 

BTW, I’m also getting the “long-crank/no-start” issue.  They just applied the ECM update per TSB for this problem, so we’ll see if that worked when/if I get to keep the truck more than a couple hours between service appointments.

 

I was having issues with the passive locking feature where the truck locks the doors a few seconds after I get out with the key in my pocket.  It would not  work even when set to on.  Now that they did the Infotainment software update (V155) this seems to be fixed.

 

I’m still having false messages that the SD Card for the Navigation System has been removed when it has not been.  GM has a bulletin out so they know about this issue, but it appears there is no fix action on this one yet.

 

After looking up each code listed on the repair orders (RO’s), I believe the main harness is a very likely cause of all the DIC error messages and system failures.  Otherwise, all those modules and sensors involved have gone bad simultaneously.  I suppose a power surge of some kind could do that, but then it seems the modules would not work fine in the short time between repairs.

 

Here are the codes the tech reported on the last two Repair Orders (bold codes where noted on both RO’s):

 

2/5/22:

B1A01

Speaker 1 General Electric Failure

B395B

Side View Camera Left

P1488

Particulate Matter Sensor Protection Tube Performance

U0020

Low Speed CAN Bus

U0022

Low Speed CAN Communication Bus (+) Low

U0077

Control Module Communication Chassis Expansion CAN Bus

U0121

Lost Communication with Electronic Brake Control Module

U0151

Lost Communication with Inflatable Restraint Sensing and Diagnostic Module

U0155

Lost Communication with Instrument Panel Cluster Control Module

U0184

Lost Communication with Radio Unit

U0415

Invalid Data Received From Electronic Brake Control Module

U0422

Invalid Data Received From Anti-Lock Brake System Control Module

 

2/10/22:

B0967

Parking Aid On/Off Switch Circuit Short to Ground

B1AO1

Speaker 1 General Electric Failure

P1488

Particulate Matter Sensor Protection Tube Performance

U0077

Control Module Communication Chassis Expansion CAN Bus

U0121

Lost Communication with Electronic Brake Control Module

U0131

Lost Communication with Power Steering Control Module

U0151

Lost Communication with Inflatable Restraint Sensing and Diagnostic Module

U0184

Lost Communication with Radio Unit

U0415

Invalid Data Received From Electronic Brake Control Module

U0421

Invalid Data Received From Suspension Control Module

U0422

Invalid Data Received From Anti-Lock Brake System Control Module

 

Posted

Has anyone checked the grounds? How about the underhood fuse box bolts?

 

 

 

 

 

 

Posted

With those dic errors, why did service start with the soot sensor??? Thinking it was grounding out can bus?

 

 

 

 

 

 

 

 

 

 

Posted (edited)

Holy Cow.... That's a lot of errors !!   Did you take delivery before the microchip shortage thing began? I'm wondering if the "newly processed" chips were  manufactured poorly. When was your build date? (I've been asking that a lot).

Edited by thekcwolf
Added content
Posted

I couldn’t say if the tech checked the fuse box bolts, but I’ll ask.  The first time this issue was addressed, it was a simple CEL.  They did the first exhaust particulate matter sensor replacement then.  I don’t know why they did the same exact thing the second time and expected a different result.   It is really looking like a damaged, or likely an improperly installed and then damaged, wiring harness to me when I study those DTCs.  

 

I took delivery in June 2021 having waited for the truck to finish its cruise from the assembly plant in Mexico to the port here in Jacksonville, FL.  I don’t know how long it sat there after assembly before being loaded on the ship.

  • 1 month later...
Posted

Update:  I still do not have my truck back.  The service advisor reports the grounding, fuse box bolts, etc. were all verified per GM specs.  They also replaced another wiring pigtail, but the issue persisted.  At least this time it didn't wait until I picked it up to go haywire again. Action has been on hold since late last week awaiting the GM engineer to travel from Atlanta.  

 

Yesterday, the GM engineer was on site to make a last ditch effort to fix the truck.  He believes he found two bad components attached to/associated with the body control module. (The advisor tells me these tests are beyond normal dealer service department troubleshooting.)  The body control module passed the tests, but 2 of the 4 "terminals" are showing bad voltage levels if I understood the advisor correctly.  They ordered the 2 terminals for overnight delivery and are installing today.  They say the GM engineer usually departs once he completes the diagnosis, but this time they are making him come in this afternoon to certify the repair as GM approved and fixed.  If the repair does not work, the dealer says they will engage with GM on my behalf to do a buy back and get me into a new, new truck.

 

I've owned this truck for 9 months.  In that brief time, the truck has been in the shop for 6 full weeks so far.  Not the "professional grade" experience I expect from GMC.  Sad.

  • 4 weeks later...
Posted

I'm on the road again!  The GM FSE (Field Service Engineer) was in a number of times, and he determined there was a loose terminal pin on the SDM x1 connector located under the center console.  Inspection and replacement involved removing the console, seats, carpeting.  So far, all appears to be fixed. 

 

The long-crank, no-start issue MIGHT be fixed.  The software update mentioned earlier is supposed to be a fix.  So far, it hasn't happened, but it was a very intermittent problem.

 

Everything appears to be working nominally.   I'm cautiously optimistic that all is good.  

  • Like 1
  • 4 months later...
  • 5 weeks later...
Posted
On 8/15/2022 at 12:14 AM, Jen1 said:

I’m having the same issue.  My dealership wants to replace the battery.  Are you still having issues? 

Sorry for the delayed response.  Yes, the DTC issue appears to be fixed.  The Long-Crank, No-Start problem happened again (once) since they applied the software patch that was supposed to fix it.  But, the pid in the SDM under the center console seems to have been the problem with the crazy error codes and system failures.  I hope you have already gotten resolution!

  • 1 year later...
Posted

Hi 👋🏽 I have 2021 GMC Sierra X31 and had the service engine light come and go after a week the service trailer brakes, service power steering and service ECM among other codes. But it’s intermittent. It kinda seems when I steer faster than it pops and sometimes the rear camera comes on when this happens. It doesn’t matter if I am in drive or in park. Battery is good. Today I took the 3 wire harnesses off the power steering module and put them back on, cleared the codes and then disconnected the battery for about 10-15 minutes and when I turned it on everything seemed to work. I took it down the road and back. All good. Then I tried another test drive and by the time I got back I completely lost power steering and all the other stuff came back. I would really like to fix this myself since the dealership is about 3 hours away and I need my truck. I was reading this forum and someone had mentioned the bolts that hold down the fuse box by the battery. Just wondering what that was all about? Also if anyone has any suggestions, I’d greatly appreciate it. 

Posted
5 hours ago, Pat0110 said:

Hi 👋🏽 I have 2021 GMC Sierra X31 and had the service engine light come and go after a week the service trailer brakes, service power steering and service ECM among other codes. But it’s intermittent. It kinda seems when I steer faster than it pops and sometimes the rear camera comes on when this happens. It doesn’t matter if I am in drive or in park. Battery is good. Today I took the 3 wire harnesses off the power steering module and put them back on, cleared the codes and then disconnected the battery for about 10-15 minutes and when I turned it on everything seemed to work. I took it down the road and back. All good. Then I tried another test drive and by the time I got back I completely lost power steering and all the other stuff came back. I would really like to fix this myself since the dealership is about 3 hours away and I need my truck. I was reading this forum and someone had mentioned the bolts that hold down the fuse box by the battery. Just wondering what that was all about? Also if anyone has any suggestions, I’d greatly appreciate it. 

Also check the ground strap behind front right inner fender well.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...