Jump to content

Recommended Posts

Posted

The downshift may have been fixed with a software update or relearn. Depending on the year, I see the early calibrations with much faster downshift times than mine. I moved mine closer, but it is still 0.100-0.200 seconds slower in spots.

 

I checked the torque on mine. The driver strut was not to spec and some of the LCA bolts were slightly under. I have issues replicating, but I guess that is good. I only notice it on sharp turns when I drive into it hard. It just bothers me it happened 2x this week.

  • 3 months later...
Posted
On 7/5/2019 at 9:48 PM, FIREBLADE74 said:

I took mine in today for the popping and harsh downshift.

 

I was told that they retourqued everything but still had the popping so they are going to replace the leaf springs eventhough I told them it was heard near the front.

 

They told me that the leaf springs could transfer through to the front, I call BS.

 

I ask what did they do for the hard shifting and he said the leaf springs are causing that too, I call BS.

 

Either way they are replacing the leaf springs once they come in. Ill be honest I haven't had a hard down shift after I took it in.

Did replacing the springs help with the popping? Been too 3 different mechanics. My spring make a lot of noise but I didn’t think I would be able too feel it up in my feet. 

  • 8 months later...
  • 1 year later...
Posted

Looking for a solution to this problem too. I get front end popping at slow speeds with sharper turns too, especially off-camber loading one side more than another. 

Posted (edited)

After having the same popping noise on my recently purchased 2014 GMC Sierra 1500 SLE I took it into the dealership who told me it was the struts due to a 3" leveling kit that was put on it. They recommended a bunch of repairs totaling over $3800. Not feeling satisfied in the answer I took it to another mechanic who told me I needed new tie rods/ball joints to get rid of the problem and it would cost $1700. Still not being satisfied I took it to yet another mechanic who told me It wasn't any of that. It was the Rack and Pinion that needed to be replaced and it would cost $2200 + an alignment. I didn't like any of those answers so I began researching myself and found this issue was the Rack and Pinion Dampner rings. The fix costed $40.

 

https://youtu.be/NFdokVsNgag

 

Moral of the story... Mechanics suck now days and are only looking to make a quick buck. You have to do it yourself.

 

 

SB-10072150-0335.pdf

Edited by Levity
Posted

I had the popping noise at low speed/sharp turns and side to side weight shifting (pulling out of my flat driveway goes to a slightly uphill road) I ended up loosening and re torquing the LCA’s to the above 129ft/lb. Popping gone for me. I noticed my drivers side front bolt was significantly more loose compared to the rest. 
 

2.5” level with Bilstien 5100’s and had 35’s on there until last week. 
 

Took ~30min with driving up on ramps, gathering tools, and drinking a beer. 

  • Like 1
Posted

Had this issue pop up last week. It was a bad sway bar link. Went ahead and replaced both sides. Took about and hour and 30 of that was rounding up tools and such. 

  • Like 1
  • 10 months later...
Posted (edited)

I have a 2015 GMC Sierra all-terrain 4x4 with a 4-in level. I've had that same popping or grinding sound and assumed it was the steering rack, but it is the crossmember that's loose. I have tightened the crossmember to torque specifications four times. It lasts for about 4 days and then as loose again. Do I need to get different bolts for this thing or should I just weld the crossmember in place?

Edited by lschafroth
  • 2 years later...
Posted

My 2016 Silverado 1500 LT Z71 5.3L does the same exact thing. My first time actually googled it and right from the very first result on down I seen many people are having the same issue. iOS am not a certified tech but much of what I have been reading is in agreement with the knowledge and experience I do have assuming you’re hearing the same noise from the same location appears it could most likely be in ascending order the CV joint, ball joint, strut, brake caliper, motor mount. If it were a wheel bearing other symptoms and noises would be present and precede the clunk.  

 

  • 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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   6 Members, 0 Anonymous, 1,450 Guests (See full list)


  • Latest Articles

  • Posts

    • 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?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.
    • $2.20 E-85 down from $2.59 Around $3.80 for regular and about $5 on average for Premium.  Propane $3.99 a gallon. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...