Jump to content

Recommended Posts

Posted (edited)

Have this now and noise has been reduced 95%. Just installed so no telling how long it will last. The remaining 5% noise could be from the lower leaf still slapping or something else.

IMG_5656.JPG

Edited by Logroller
Posted (edited)

another view. I did not clean and lubricate this time, just put in cut tubes from the dirt bike. Placed between top an middle leaf and middle and bottom leaf at both ends. That is 4 pieces per side. 

IMG_5654.JPG

Edited by Logroller
Posted
20 hours ago, jay webb said:

as a tech at a gmc dealership i see this very often. this is what we do, we spoke with an engineer. there are updated leaf spring pads the dealership can install in replacement of the old ones. the old ones are rectangle in shape between the leaf springs. the new ones are like the round ones on the lower leaf spring. there is no actual bulletin or anything that calls for this. but gm has been approving the warranty claims for this. it typically takes about 30-1hr to complete. not a very difficult job. i did it 3 times this week at work. 

You have a part number by any chance?

Posted
28 minutes ago, Chad2815 said:

You have a part number by any chance?

not off hand. ill see if i can come across it on monday when i go back to work. if you look at the picture in the post above yours you will see the pad im talking about its the round one on the lower leaf spring. you get those and install them on the upper leaf springs 

Posted
21 hours ago, jay webb said:

as a tech at a gmc dealership i see this very often. this is what we do, we spoke with an engineer. there are updated leaf spring pads the dealership can install in replacement of the old ones. the old ones are rectangle in shape between the leaf springs. the new ones are like the round ones on the lower leaf spring. there is no actual bulletin or anything that calls for this. but gm has been approving the warranty claims for this. it typically takes about 30-1hr to complete. not a very difficult job. i did it 3 times this week at work. 

Glad to hear this.  My dealership is replacing both left and right spring packs with "NEW" designed ones with new insulators and insulator locations is what they told me.  I go in this Friday for the appointment.  The service adviser didn't even know about the new leaf spring configuration.  He was simply saying that replacing them would just be the same ones with the same problems.  But the tech comes out and says "new leaf springs on both sides".  The adviser kind of shocked asked the tech why if they are just the same leaf springs?  Tech said they are different and a fairly new addition to the fix GM is putting out.  

Here's to hoping it fixes my clunky rear end!!!! 

Posted
On 8/17/2019 at 9:56 PM, Praedator said:

Glad to hear this.  My dealership is replacing both left and right spring packs with "NEW" designed ones with new insulators and insulator locations is what they told me.  I go in this Friday for the appointment.  The service adviser didn't even know about the new leaf spring configuration.  He was simply saying that replacing them would just be the same ones with the same problems.  But the tech comes out and says "new leaf springs on both sides".  The adviser kind of shocked asked the tech why if they are just the same leaf springs?  Tech said they are different and a fairly new addition to the fix GM is putting out.  

Here's to hoping it fixes my clunky rear end!!!! 

Man I sure wish i got that kind of service from the dealer I bought from, I just got the service adviser telling me that it is my fault and there is no solution. May have to escalate the matter with a phone call to GM/Chevy.

Posted
On 8/17/2019 at 6:56 PM, Praedator said:

Glad to hear this.  My dealership is replacing both left and right spring packs with "NEW" designed ones with new insulators and insulator locations is what they told me.  I go in this Friday for the appointment.  The service adviser didn't even know about the new leaf spring configuration.  He was simply saying that replacing them would just be the same ones with the same problems.  But the tech comes out and says "new leaf springs on both sides".  The adviser kind of shocked asked the tech why if they are just the same leaf springs?  Tech said they are different and a fairly new addition to the fix GM is putting out.  

Here's to hoping it fixes my clunky rear end!!!! 

Post your receipt write up from the tech so we can see what they did and codes. 

Posted

I got a 2017 Silverado 1500 4x4 Z71. 24,xxx miles on it and just took it to the dealer for the same issue. At first, the dealer said the tech couldn’t get it to duplicate the issue (of course). Took it back same day & had the tech do a test drive with me in the truck and got the noise to happen. He said I’m going to have to leave and see what he could find, but that I “may” have to just deal with it until it gets worse. BULLSHIT!! So we shall see how long this process takes (after reading other posts) and see what the outcome is. Also, I don’t know if anyone has had the seat move while turning? Been at the dealer before for that issue and put the retainer clip on the front seat slide. Excited to see what “run a round” they give me with that issue. Wish me luck lol. 

Posted (edited)

Took mine in today 2017 Silverado Z71 , they said thier was not a fix. The tech showed me how to duplicate the noise. He started to shake the bed of the truck left to right and the truck started to clunk. He said it was the axle shafts beating around. He also showed me on a 2019 trail boss. LOL

Edited by Jh8473
Spelling
Posted
Here is the video 

 

That is the floating axles. If shaken a lot of trucks and the noise is all the same. Leaf spring clunk is different.

 

Sent from my XT1710-02 using Tapatalk

 

 

 

Posted (edited)

You can fight the dealership or upgrade your suspension which will not only get rid of the noise but help every facet of driving. Had them for years and forgot about this problem.  Roadmaster active suspension. Noise gone, wheel hop gone, that annoying squirrely backend when going over bumps/ curbs.  Drives like a caddy. Look all over the net only 5 star reviews for a reason. 2015 ltz 6.2

By the way the noise is from leaf movement during axle wrap. I'm sure there are cheaper solutions, but these are worth every penny. No drilling required. 

Edited by Abiker21

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