Jump to content

Recommended Posts

Posted

Mine was done on 8/28 when the truck was in for transmission service and induction cleaning.

No issues before the recall and no issues after. Btw the truck shifts and runs better tho after my services :)

Posted

The current steering recall is the only steering recall I know of for '14-'15 LD trucks. Except for a very limited steering motor recall on '15s. No recalls for cables.

I know what the recalls are. What I'm saying is that was what's happening to mine. No recall for the 15s but the issue recalled for the 14s is what I'm experienceing. It wasn't the cables at all or the battery. They said there was an update available for my truck for the steering and that's what they did.

Posted

Had mine done on Wednesday this past week. No issues before the update and so far no issues after the update. I am coming up on 89k miles on the truck. I did mention that I thought there was an issue with the steering rack. They came back with the shock on the passengers side front/strut is leaking and needs replaced. I guess it's time for a new set of Bilstein's all around.

Posted

Has this fixed the issues with the steering loss and truck turning off? My steering has been going out and vehicle dying at least three times a week for the past month. Im also getting the "steering assist reduced" and "parking assist off" warnings on my screen. Any feedback is appreciated. Thanks. [emoji106]

 

 

Sent from my iPhone using Tapatalk Pro

Posted (edited)

I have been dealing with the glitch for around 6 months. First it was a ground wire, then it was the power steering motor and now the recall. I took it in two weeks ago to get the recall done thinking that was going to solve the problem as I was experiencing all the EPS issues but seems like the issues have gotten worse. The majority of the time it was happening while turning at a slow speed. Now all systems in the truck go off for a few seconds then kick back on while driving at any speed. Seems to do it a lot while in traffic as well, truck will just lose all systems. I was able to get a video of it yesterday and hopefully the dealer and GM will be able to get this fixed.

IMG_0914.MOV

IMG_0914.MOV

IMG_0914.MOV

IMG_0914.MOV

Edited by Joshj
Posted

Has this fixed the issues with the steering loss and truck turning off? My steering has been going out and vehicle dying at least three times a week for the past month. Im also getting the "steering assist reduced" and "parking assist off" warnings on my screen. Any feedback is appreciated. Thanks. [emoji106]

 

 

Sent from my iPhone using Tapatalk Pro

 

 

I have been dealing with the glitch for around 6 months. First it was a ground wire, then it was the power steering motor and now the recall. I took it in two weeks ago to get the recall done thinking that was going to solve the problem as I was experiencing all the EPS issues but seems like the issues have gotten worse. The majority of the time it was happening while turning at a slow speed. Now all systems in the truck go off for a few seconds then kick back on while driving at any speed. Seems to do it a lot while in traffic as well, truck will just lose all systems. I was able to get a video of it yesterday and hopefully the dealer and GM will be able to get this fixed.

 

Have your dealer check PIT5405 (you can search these forums for a copy of it). It walks the tech through 4 or 5 things they need to check. The main things include the positive battery cables and the G218 BCM ground behind the dash. Many people on this forum got their electrical problems resolved by fixing these. The G218 ground is easy and you can fix it yourself if you don't want to take a trip to the dealer.

Posted

Dealer just flashed my 2014 - no issues before, hope nothing new happens now. ~35K miles on truck, so everything should start going to "H" soon. I have only been driving the truck for ~4 months now and to the dealer twice now.

  • 1 month later...
Posted

So I started having the issue about a month before GM released acknowledgement of the issue.  Once the recall fix was available, I scheduled my service.  For a week or so, everything seemed fine after the fix.  Then it started doing it again.  Not as bad before on most cases, however I noticed that the loss of power steering at slow speeds was worse than before.  Any ideas?

Posted
2 hours ago, 97SierraSLT said:

you'd think NHTSA would be all over this.  This is a serious safety issue.

Unfortunately, it will take people dying like with the ignition switch issue to escalate the concerns. 

  • 2 weeks later...
Posted

Add me to the list of trucks not fixed by the recall.  The behavior changed but I still lose power steering.  The reprogramming just makes it so that when the issue occurs it doesn't jerk the steering wheel out of your hand; you still lose power steering though.  The issue occurs in conjunction with another wierd electrical issue: activating a turn signal cancels the cruise control.  Neither issue occurs unless I have been driving for more than 45 minutes which tells me it's a temperature related issue.  I have corrected the G218 ground issue and it didn't change anything.  

Posted
22 hours ago, aflesch said:

Add me to the list of trucks not fixed by the recall.  The behavior changed but I still lose power steering.  The reprogramming just makes it so that when the issue occurs it doesn't jerk the steering wheel out of your hand; you still lose power steering though.  The issue occurs in conjunction with another wierd electrical issue: activating a turn signal cancels the cruise control.  Neither issue occurs unless I have been driving for more than 45 minutes which tells me it's a temperature related issue.  I have corrected the G218 ground issue and it didn't change anything.  

Try checking your battery terminals.  I brought mine in on Friday to have the dealership look at the continuing problem after the recall had been "fixed".  They said there was some issue with the battery terminals not connecting all the way.  Your issues after the "fix" are very similar to what mine was doing.  I hope whatever the dealership did Friday works.

Posted (edited)

Thanks @tistre1. I contacted GMC customer service this evening to document the issue and will be calling the dealership in the morning.  Did you have to pay for the additional repairs out of pocket?

Edited by aflesch
Posted

No, I did not pay.  When I called GM to open up a case, I stressed that I did not want to pay the diagnostic fee to get the issue checked.

Posted

Fixing the ground issue took care of the problem for me. I went ahead and went in for the recall anyway, fwiw.

 

I posted a message to the NHTSA website months ago. It's amazing that they decided to initiate a recall that doesn't fix the ground issue too. This is an accident waiting to happen if the recall doesnt actually fix the problem.

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...