Jump to content

Recommended Posts

Posted

I got my 2016 GMC 2500 about a year ago and when I took it in for service last week the techs called me be cause I needed to see what they had found. They showed me welds on my front cross member brackets. Passenger side looked ok but the driver's side looked like it had begun to split. They weren't sure why someone would cut these. I started doing research and I think that the previous owners had the truck lifted and then removed the lift prior to trading it in. 

My question is, is there a way to get this repaired properly? What suggestions do you guys have?

IMG_20210125_090900368.jpg

IMG_20210125_090954905.jpg

Posted

That’s definitely a cut from a prior lift install that has been removed and then welded back. The only way to fix it is to reweld the area. 

Posted

You'd need to find a welder that would do things for cash, I'm sure they are out there.

 

Only thing that bugs me is that the engine and drivetrain is installed, so you couldn't weld the frame with no stress on any of it. I've seen worse repaired that's for sure, it'll probably be just fine is it's fixed the way it is.

Posted

Did you get a warranty when you bought the truck?  Would be a tough fight but maybe you have some type of recourse. 

Posted

Thanks for all the suggestions guys. After I got my truck back from the shop repairing the damage that a squirrel caused I took it to the dealership where it was purchased. I spoke with the general manager and the service manager and they have agreed to do a full frame replacement and change out all the after market parts that were used and bring it back to factory. I was not expecting this but I'm so glad that they stood by their product and are willing to make it right for the customer.

  • Like 2
Posted

[emoji122][emoji122][emoji122][emoji122]

 

I applaud this dealer.

Who is the dealer.?

Sent from my Pixel 3 using Tapatalk

 

 

 

 

Posted
On 2/3/2021 at 6:05 PM, Carlos Cadenas said:

Thanks for all the suggestions guys. After I got my truck back from the shop repairing the damage that a squirrel caused I took it to the dealership where it was purchased. I spoke with the general manager and the service manager and they have agreed to do a full frame replacement and change out all the after market parts that were used and bring it back to factory. I was not expecting this but I'm so glad that they stood by their product and are willing to make it right for the customer.

You do realize they literally buy a frame, set it next to the truck then move everything from the old frame to the new frame? I got rear ended a little over a year ago and the body shop was telling me what would happen if the frame was bent (it wasn't).

Kudos to the Dealer for stepping up on this one but I'd also be looking for an extended warranty to cover any issues from the frame swap as well.

Posted

 

 

 

Chances are you'll be replacing the crossmember and/or possibly even the frame,

 

I have to hand it to you timmy you were right.

[emoji24][emoji24][emoji2957][emoji2957]

 

Sent from my Pixel 3 using Tapatalk

 

 

 

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,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 2,066 Guests (See full list)

  • Latest Articles

  • Posts

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...