Jump to content

Recommended Posts

  • 2 weeks later...
Posted

I have a 2014 Chevrolet Silverado 1500 Z71 that was having the same issue. Complete power failure...it seems that if I leave the truck for 5 mins and then come back it will start right up with no issues. I tore apart the dash to fix the ground issue, but there's no ground in that location on my truck. Anyone have the same issue? Did Chev not put all the grounds in the same spot...

 

Thanks!

Posted

Hi, I have a 2014 Chev Silverado Z71. I'm having similar issues. I'll have complete power failure/engine shut down intermittently, once while I was driving. I took apart the dash to fix the ground. But my truck does not have a ground in that location. Also, it seems all I have to do it wait 5 mins and everything works like normal again. Does anyone else not have the ground in that location or know what else I should look at to fix it?

 

Thanks!

  • 3 weeks later...
Posted (edited)

With my 15 Silverado, my only electrical fluke was my forward collision alert sensors going nuts.  I posted a video of it somewhere in my album for it.

 

With my 18 LTZ ME, the Infotainment System would randomly reboot and my battery dying prematurely, a couple months ago.  Infotainment System hasn't rebooted, since I had the firmware on it flashed about a year ago, yet.  Would be my luck, it reboots on the way home from work tonight. 

Edited by Ravenkeeper
  • 2 weeks later...
Posted (edited)

While vacuuming I found two more hidden grounds, one under driver and passenger seats under the vents. Mine were clean and tight, no insulation to deal with.

IMG_20210121_143558324.jpg

Edited by beetle
  • 4 weeks later...
Posted

Thank you so much for this amazing detail!! I was able to follow the exact instructions, photos, service bulletin and the YouTube video you included that helped me get the job done myself in just a couple hours. 

 

To people reading this post currently: this only has to do with the vehicle shorting out when you hit a bump. This issue has been bothering me for about a year now and I have spent hours looking for answers. I have a 2015 Tahoe Z71 and it seemed to run better instantly after this change. 

  • 3 months later...
Posted

Good evening all,

 

it appears to be a widely covered topic across the forum but this appears to be the best established thread. I had initially had this issue and fixed according to this thread and all my problems were solved for months. Now it’s happening again...I’ve gone in and re did the ground and the issue still persisted. Went back in and sanded and cleaned and are still having the issue. 
 

very frustrating and want to get this fixed before I end up in an accident. 
 

If the G218 isn’t the culprit anyone have experience in where to go next?

Would it be dumb to run a wire from my negative terminal of battery to g218 ground post? Not sure if I would gain anything but something I thought of as my truck died again pulling into drive way...

 

thank you in advance for any help

  • 2 months later...
Posted
On 3/26/2019 at 10:28 AM, Jonnb said:

After washing my truck thoroughly 2 weeks ago, all these issues popped up on my 2017 silverado 1500 WT, 4X4 Crew cab. At first, it was intermittent and usually on a rough patch of highway. But the last week it was steady. I finally got to my service appointment 2 days ago. There were several communication errors between a bunch of sensors. My truck has 49000 miles, and was told none of it would be covered under warranty(complete and extended warranties were purchased). So i took it home and tried all these fixes,(I assume i still have a lot of wiring yet to check), but the issues are still there. Service stabiltrak, service trailer brake system, no cruise control, no TPMS, ABS light on, hit a bump and the power steering "grabs" for a split second. The only one of these fixes I didn't try yet was battery to ground cable replacement. Beginning tonight I will be tracing wires and ground points, so we shall see. I just wanted to share so maybe, someone watching these forums who may be taking note, realizes how far this problem goes. One of my coworkers had a couple sensor issues on his 2018 Chev 1500 LTZ he purchased in Nov/18 with only 3800 miles on it, but disappeared a couple days later and hasn't returned. It doesn't help that the 2 local GM dealerships in the area are not very helpful. ( whole slew of different stories on that topic lol)

Did you ever get this fixed? I am having similar issues specially  the mentioned communication issues.

Posted
15 hours ago, Omar Llamas said:

Did you ever get this fixed? I am having similar issues specially  the mentioned communication issues.

No. I got fed up and called GM head office. They bought the truck back and I purchased a 2019 Trail Boss. That one also had issues with the stabilitrak, and a couple other electronic things. Also, the front diff grinded from the start, transmission was always banging. # different dealerships wouldn't acknowledge there was anything wrong. Even had a tech drive with me and I pointed it out, he agreed. But when it came time to pick up the truck, they still said they couldn't find anythig wrong. SO after 80000kms, I sold it at a loss and got a Toyota Tundra. I called GM, and they kept wanting me to pay for a front end diagnostic immediately after getting it out of the shop, paying for a diagnotic. So I told them to shove it. 

  • Like 1
  • 2 years later...
Posted

Me too !!!!
       Hi. My name is Thomas and I have a 2016 Silverado LT Z71. I'm the original owner so I am aware of what the truck has been through and that is nothing that can explain why one day the HID headlights shut down and just regular old headlights now, fog lights stopped working, the horn, some trailer lights, the backup camera didn't work, then worked here and there and one day just began working again, plus there's a few other electrical issues too. I've been tracing them with Foxwell Diagnostic Scan Tool that has the complete Chevrolet software but I'm only an amateur tech and haven't had much luck and that I did is beyond my capability.  Have you had any luck with your problem Tony? I know that many times problems are similar and pervasive but can be solved by word of mouth.  I noticed, if I read it correctly they this post is from 2017 and see that 

several people responded which I'll read up on.   Thanks Tony  

 

 

 

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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...