Jump to content

Recommended Posts

Posted (edited)
7 hours ago, ColoradoCub said:

That’s not a very logical response. Customer has problem A, GM says repair B fixes it. Repair B is completed and customer still has problem A. Your logic is that the repair was not done correctly?? And remember he’s not just one individual, he is THE individual that the TSB was created for, pictures on the bulletin are of his engine!!! Geez!! And what about all the trucks that don’t have a bent trigger wheel after being inspected but have the same crank no start, are you implying that a problem plaguing many 2021 trucks identically is being caused by multiple things?

FWIW my opinion is that GM knows they have some trucks with defective timing trigger wheels that could cause serious engine failures.   One symptom of a bent wheel could be the failure of the ECU to see and fire the ignition pulses correctly thus long cranking episodes.   So the TBS to inspect and replace bent wheels makes some sense.  The interesting thing is that upon inspection they find no problem with the wheel they have no next step.    

 

My guess is that a majority of the trucks having this problem also have straight timing wheels.   Some episodes are likely caused by folks accidently resting their foot on the gas peddle.   Others maybe related to the fuse panel working loose causing some relay in the start logic to not operate exactly when it should and there is no code set for the improper action.   There was a TSB for the loose fuse panel.  If this is a root cause for most of the long starts, GM is looking at a massive recall, ie every Silverado and Sierra since 2019.    They are probably testing fixes to find something relatively inexpensive to fix the problem.   Time will tell since Consumer Report has already labelled these trucks as  electrically  unreliable, GM has to find an answer.

 

 

 

Edited by GJR1212
verb tense wrongg
  • Like 1
Posted

I had my truck for 20 days and in that time it happened 2 times. 2021 silverado RST 3.0l diesel. So far the truck has been in the garage for 48 days, ive been driving a 17 silverado the dealer just got traded in. They have been waiting on parts to fix the exciter wheel, last week the parts came but one was damaged when they got it, im thinking they received another bent exciter wheel. I requested a new truck and that was "being worked on" by GM but when they heard the parts where in they threw that out the window and are planning on making my payments for some time, the manager at the dealer told me maybe 6 months payments. If that is the case I wont be entirely disappointed with the service but from what I am seeing this may not even fix the problem, besides the fact I will have no trust left in the truck after being completely tore down to do the job. For now I am very frustrated but being patient because at least I have a truck to drive. Depending on what they do for me when i get the truck back and if the problem is fixed in the end it might not be such a bad thing. Time will tell. 

  • Like 1
Posted

Things will get interesting when more guys get the exciter wheel replaced and they still have the crank no start. But seeing as a member here was ground zero for this TSB and had all the parts in the back of the engine replaced including the trigger wheel, timing chain, gears and sensors and it didn’t take a week to have the problem occur again I am not in the least convinced this is the fix.

Posted

There’s no way I’d be without my new truck for 48 days , it would have been traded in by now. But I do appreciate those of you enduring this ****** show for the rest of us that aren’t willing to!

Posted
2 minutes ago, ColoradoCub said:

There’s no way I’d be without my new truck for 48 days , it would have been traded in by now. But I do appreciate those of you enduring this ****** show for the rest of us that aren’t willing to!

Id love to trade her in a get rid of her but for me (without losing thousands of dollars) there's really no choice but to stick it out at least until i can break even on a new one. 

Posted
31 minutes ago, 3.0duramax said:

Id love to trade her in a get rid of her but for me (without losing thousands of dollars) there's really no choice but to stick it out at least until i can break even on a new one. 

 

Not sure where you live but here you can get a sales tax credit and pay/refund the difference of the truck you traded in vs the one you purchased but only within the first 45 days I believe. Just thought I'd share.

Posted

Just had this issue with my month old truck with 750 miles on it.  Looking through forums it seems several people are having this issue so going to assume GM will have to figure something out soon.

Posted

Anyone with this issue on higher mileage diesels (greater than 5k)?

 

Mine had three instances all under 1100miles. Currently at 5500 miles and no instances since 1100

Posted (edited)
1 hour ago, MNJoel said:

Anyone with this issue on higher mileage diesels (greater than 5k)?

 

Mine had three instances all under 1100miles. Currently at 5500 miles and no instances since 1100

Yes there have been owners that it happened to several times early on when newer and then nothing for a while and then it comes back thousands of miles later..

Edited by ColoradoCub
Posted
On 7/13/2021 at 8:46 AM, Barrett10 said:

posted this earlier... \

 

Got my truck back from the dealer; 2nd time for the no starting issue--starter runs for 15-20 seconds, truck does not start.  Dealer checked fuel injector data, fuel pump high and low side PSI while attempting to duplicate.  Checked and re-tightened ground connections @ G130, 131, 132, 133 and 134. Checked fuel PSI regulator for loose pins. Checked fuel injector #1 and cam sensor. OK no problem found.  So, I do not think the service manager was convinced the issue is fixed, time will tell.  But if it goes in for the 3rd time...?  Total days in the shop-19 days; 3 days 1st visit, 16 for the 2nd visit.

Well, it happened again. Starter  ran for 20 seconds truck didn’t start. I guess the grounding issue did not fix it. I’ve been talking with GM and sending them all my information, very detailed information with videos attached of the truck not starting. They are reviewing the case right now, but going in the shop for the third time should help my case for reimbursement. Taking it to the shop tomorrow night and we’ll go from there.

  • Like 2
Posted
Just now, Barrett10 said:

Well, it happened again. Starter  ran for 20 seconds truck didn’t start. I guess the grounding issue did not fix it. I’ve been talking with GM and sending them all my information, very detailed information with videos attached of the truck not starting. They are reviewing the case right now, but going in the shop for the third time should help my case for reimbursement. Taking it to the shop tomorrow night and we’ll go from there.

Truck is currently at 3900 miles.

Posted (edited)
38 minutes ago, Barrett10 said:

Truck is currently at 3900 miles.

 

Think you could upload the videos and share? I haven't got videos of mine yet but would like some to show my GM dealer. I am trying to trade in and get out of the truck still though.

Edited by Jacob D
Posted
9 hours ago, Quentin Corbett said:

Just had this issue with my month old truck with 750 miles on it.  Looking through forums it seems several people are having this issue so going to assume GM will have to figure something out soon.

HAHA. You clearly never owned a GM 8 speed transmission, lol.

  • Haha 1
Posted
1 hour ago, Jacob D said:

 

Think you could upload the videos and share? I haven't got videos of mine yet but would like some to show my GM dealer. I am trying to trade in and get out of the truck still though.

I could only upload a short video. The real video is about 20 seconds longI could only upload a short video. The real video is about 20 seconds long

  • Like 1

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

    • I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...