Jump to content

Recommended Posts

Posted
On 3/11/2019 at 9:18 PM, Jcharley said:

It had 31 miles on it. (Great idea) I live 1 hour south of Chicago so they do salt the roads but I have a heated garage and keep it clean year round. I will take pics tomorrow and put them up for everybody to see. 

I know it doesn’t help the situation but your not alone and GM is not the only manufacturer with rust issues. Look at Ram. Still I’d be pissed too.. 

Posted

My 14 Silverado with 32k miles on it also has the rockers and cab corners bubbling up pretty bad.  Probably rusting from inside out the same as my 04 did with around 40k miles but just over the 6 years.  Hopefully my 14 will be covered under warranty.  Very disgusting for a $45k truck 

  • 3 months later...
Posted (edited)

Just looked yesterday at my 14 and it is bubbled worse than this clear down the rockers. 60k miles Hopefully they cover it.

Edited by jsouth
Posted (edited)

My 14 brownstone Silverado did the same thing on both sides.  Took it to dealership and they replaced both rockers and cab corners under warranty.  Took 2.5 months but gm covered it.  Rusted from the inside out.  They said something about the foam inside was holding all the moisture in.   I just got it back last week.  It had 33k miles on it

Edited by Shiloh74
Addition
  • Sad 1
  • 2 months later...
Posted

I have a 14 Sierra crew cab, I'm in MA so plenty of salt, and my rockers looked worse than that last summer (2018), but at 110k at that time GM wouldn't cover it.  My last truck (05 1500hd) bubbled like this at 7yo about 170k.  

Seems to me the quality of the steel is continuing to get worse. 

There all made out of recycled Pepsi cans now!

  • Sad 1
Posted (edited)

I think with any type of metal, it’s over recycled. 

I think that has a huge part of why things are rotting. Then again, if proper metal prep procedures are done prior to painting, this shouldn’t happen...

 

goes with steel, iron, copper, etc. the quality isn’t there anymore. 

 

Edited by Jgreen2193
  • 2 years later...
  • 3 weeks later...
  • 11 months later...
Posted
On 3/12/2019 at 4:09 PM, wforrest08 said:

So half the bill is 1800 bucks? So 3600 to replace rockers? Probably to late now but I definitely would have checked around with some independent body shops might have got it done for less than the 1/2 your paying. Also since you were literally 60 miles over it might be worth reaching out to GM corporate and seeing if they might offer some relief. I don’t have personal experience with this but I’ve read more than a few threads on here where guys have got this to work for them. Also does your dealer (assuming that’s who’s doing it) guarantee it for life? The dealer that has painted my passenger side one twice now does. Also there’s a pinned thread on here about frame rust on these trucks didn’t know if you have checked that one out and/or checked yours out? Only reason I mention it is because it might not be worth hanging onto that truck long term if the frame is going South. I’m currently looking for a replacement for my 01 HD do to  it’s structural rusted frame.

 

Thread about frame rust.

1/1 Skip Ad Continue watching after the ad Visit Advertiser websiteGO TO PAGE
 
 
 
 
 
 
9.png

 

 

 

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