Jump to content

Recommended Posts

Posted

Hey guys, new to the forums here. Finally had to reach out after being confused for a while.

 

Have had a weird issue going on lately with my truck. Or at least just started noticing it. 

 

During acceleration from a stop, either from a typical stop light, or perhaps stop sign, I am getting a pop or bump in the back under the truck. Almost feels as if I have left something in the bed and it slid and hit the tailgate. Or perhaps a spare tire that was loose that swung and hit the bumper. It has been baffling me for a while now. I've tried slow accelerated starts which seem to not be as persistent. Perhaps 25-50% of the time. But if I hit it slightly harder it's more pronounced and happens about 95% of the time. I've tried to see if I feel it in reverse too, but it just doesn't seem to replicate as easily in that fashion. But, I'd go out on a hunch and say that I've felt it a couple times while accelerating backwards into my upward facing driveway. 

 

The truck in question is a 2015 Chevy Silverado LT 2WD 5.3L with 88.5k on the dash. Has never towed anything besides a uhaul trailer for moving years ago. So far this truck has been amazing without any major issues. Fingers Crossed.

 

Last transmission flush was done about 12k ago. But I really don't think that is the problem as it shifts and moves into reverse and other gears smoothly. Is there anything that would be causing this particular issue? Being that it is a 2WD, I don't have a transfer case I do not believe, where splines could be an issue. Is this something that U-Joints could create? Truck is in stock condition and nothing has been altered or changed. 

 

I appreciate everyone's response in advance, as there are far better folks out here whom will be able to assist in this than I will ever be qualified for. 

Posted

Check the tire pressure in the spare and tightening up on the jack screw that holds the spare up. Just a thought.

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

    • This video may not be the exact content for the joke thread but its a lot of laughs so here it is, I've only watched a portion of it so far but if anyone is looking for some light hearted good soap box driving action, its here. As a note in the upper left of the screen it shows the number out of 100 to refer back to any particular vehicle for comment !.    https://www.facebook.com/reel/1351928276956715
    • 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.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...