Jump to content

2021 Sierra 1500 Elevation Christmas Tree Dash - No Start

HollywoodBall
 Share

Recommended Posts

HollywoodBall Enthusiast

HollywoodBall

Posted
Posted

2021 Sierra Elevation 3.0 Duramax with just under 50K miles currently.  This issue has been plaguing me over a year/year and half and 20K miles.  Tends to happen in cold temperatures and always starts with a failed remote start.  

 

Remote start fails and upon entering vehicle to push button start, the dash lights up and every single warning message in the system pops up, one after another.  It's always happened in colder weather.  It left me stranded an hour and half away from home last winter, requiring a tow to GMC dealer and car rental to get home, and back to servicing dealer.  That dealer lazily misdiagnosed it as a bad battery.  Replaced battery under warranty and sent me home only for it to happen again a few weeks later.

 

Then local deal diagnosed it as a bad engine harness, which of course was on backorder.  It took awhile for that to come in and ever since it did the dealer's been dodging the repair.  I had it in for an oil change last week and brought it up at checkin or checkout, due to being concerned about cold weather again but the service employee deferred to "my" service rep, who was on vacation, and said he's call Monday.  Well sure enough, it left me stranded without a vehicle this morning.

 

Video attached.  

 

 

I have a hard time reconciling a wiring harness issue with cold weather, but what do I know?

 

Any thoughts from the masses?

 

Here's the video of what it does.  It eventually starts with CEL, but that CEL clears after  a few cycles.  Went to another dealer today begging them to just pull the code for future diagnosis and they basically said not possible, but we can check it out in 3 weeks.  I've escalated to GM and opened a ticket with corporate.

 

 

gemarsh Senior Enthusiast

gemarsh

Posted
Posted
1 hour ago, HollywoodBall said:

2021 Sierra Elevation 3.0 Duramax with just under 50K miles currently.  This issue has been plaguing me over a year/year and half and 20K miles.  Tends to happen in cold temperatures and always starts with a failed remote start.  

 

Remote start fails and upon entering vehicle to push button start, the dash lights up and every single warning message in the system pops up, one after another.  It's always happened in colder weather.  It left me stranded an hour and half away from home last winter, requiring a tow to GMC dealer and car rental to get home, and back to servicing dealer.  That dealer lazily misdiagnosed it as a bad battery.  Replaced battery under warranty and sent me home only for it to happen again a few weeks later.

 

Then local deal diagnosed it as a bad engine harness, which of course was on backorder.  It took awhile for that to come in and ever since it did the dealer's been dodging the repair.  I had it in for an oil change last week and brought it up at checkin or checkout, due to being concerned about cold weather again but the service employee deferred to "my" service rep, who was on vacation, and said he's call Monday.  Well sure enough, it left me stranded without a vehicle this morning.

 

Video attached.  

 

 

I have a hard time reconciling a wiring harness issue with cold weather, but what do I know?

 

Any thoughts from the masses?

 

Here's the video of what it does.  It eventually starts with CEL, but that CEL clears after  a few cycles.  Went to another dealer today begging them to just pull the code for future diagnosis and they basically said not possible, but we can check it out in 3 weeks.  I've escalated to GM and opened a ticket with corporate.

 

 

 

Has this been checked?...

 

Screenshot_20231116_154500_AdobeAcrobat.thumb.jpg.79cc4bfb371dc7973fa13a31865ef09e.jpg

 

My '21 had 600 miles when I checked the torque and all 4 loose.

 

Underhood fuse panel2.pdf

forest Enthusiast

forest

Posted
Posted

Ditto the fuse block bolts ... I had all kinds of weird stuff happening on mine including it dying on me while driving down the highway just to start up again on its own 20 seconds later ... happened multiple times.

 

I torqued down those fuse block bolts and problem went away ... worth a shot ... would do it yourself vs dealer ... .02

  • 4 weeks later...
  • 1 month later...
HollywoodBall Enthusiast

HollywoodBall

Posted
  • Author
Posted

See invoice for dealer tech diagnosis. Entire under hood fuse block was replaced. Sounds like there was a loose fuse connection in the start/run circuit. I’m 75% confident they got it, as it repeated the failure the morning they moved it from parking lot to shop (I delivered the night before so it would sit in the cold. Voila, it replicated for them).

IMG_1294.jpeg

IMG_1295.jpeg

Bikerjon Enthusiast

Bikerjon

Posted
Posted
8 hours ago, HollywoodBall said:

See invoice for dealer tech diagnosis. Entire under hood fuse block was replaced. Sounds like there was a loose fuse connection in the start/run circuit. I’m 75% confident they got it, as it repeated the failure the morning they moved it from parking lot to shop (I delivered the night before so it would sit in the cold. Voila, it replicated for them).

IMG_1294.jpeg

IMG_1295.jpeg

I hope they got it fixed for you.

HollywoodBall Enthusiast

HollywoodBall

Posted
  • Author
Posted

I feel like they did.  The saving grace was having the failure repeat itself at the dealer.  It's been in 3 or 4 times at the same dealer and another in Pittsburgh and each time was lazily and half-ass looked into each time.  I opened a case with GMC Customer Care and that seemed to light a fire under everyone's ass to resolve it.  The written diagnosis seems thorough and accurate and it hasn't repeated itself, but I often park in my heated garage.  So we'll see, but I feel good about it for the first time.

HollywoodBall Enthusiast

HollywoodBall

Posted
  • Author
Posted
On 11/16/2023 at 4:47 PM, gemarsh said:

 

Has this been checked?...

 

Screenshot_20231116_154500_AdobeAcrobat.thumb.jpg.79cc4bfb371dc7973fa13a31865ef09e.jpg

 

My '21 had 600 miles when I checked the torque and all 4 loose.

 

Underhood fuse panel2.pdf 337.34 kB · 10 downloads

 

You were close!  It was actually a "loose" fuse terminal in that box, according to them.  Specifically the fuse in the starting/ECM cycle.  They replaced the entire unit and reprogrammed the ECM.

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
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   5 Members, 0 Anonymous, 1,931 Guests (See full list)

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...