Jump to content

Recommended Posts

Posted
On 2/11/2019 at 1:48 PM, Booger T said:

Thanks for the response, I may have dealer talked into replacing the caliper next to see if that fixes it.

Booger T I see you posted this back in February. Are you still having this issue? What was the fix if the problems gone? 

Posted
5 hours ago, Eds240z06 said:

Booger T I see you posted this back in February. Are you still having this issue? What was the fix if the problems gone? 

Yes the problem still exists. In fact it has gotten much worse. Mainly does it first thing in the morning when backing out of garage. Also does it when first going forward after reverse. Does it at all temps but definitely worse when cold. I am done with this truck, new one was built this week and is in transit on a train somewhere. Should get it in a couple more weeks. I think my dealer is still waiting on GM to say there is a problem and what the fix is. In all fairness to dealer they did replace both rear rotors, calipers and brake pads to no avail.

Posted
20 minutes ago, Booger T said:

Yes the problem still exists. In fact it has gotten much worse. Mainly does it first thing in the morning when backing out of garage. Also does it when first going forward after reverse. Does it at all temps but definitely worse when cold. I am done with this truck, new one was built this week and is in transit on a train somewhere. Should get it in a couple more weeks. I think my dealer is still waiting on GM to say there is a problem and what the fix is. In all fairness to dealer they did replace both rear rotors, calipers and brake pads to no avail.

Thanks for the reply but not what I wanted to hear. Good luck with the new truck!

Posted

Hopefully I won't get another one with the same problem. I've owned 15 new GM trucks over the years and have never had one make this kind of noise. A small squeak or squawk here and there can be expected but the wounded elephant sound is just too much to put up with day in and day out. I was wanting the new 3.0 diesel  any way so this was a good reason to get rid of it. Don't know what dealer plans on doing with it. Don't really care.

Posted (edited)
On 2/6/2019 at 7:28 PM, Booger T said:

HI, am having issues with one of  the brakes on my TB dragging/squalling. Took to dealer and they determined it was the left rear making the noise, said that there was dust on rotors/pads. They decided to change pads on back brakes as a place to start. Had them done last Thursday. Still making noise, the colder it is the louder the noise. When first starting out from setting for a short period of time if you apply slight pressure to brakes it makes it all the time. Starting to get really annoying when I take off from stop sign or parking lot and my new truck makes a god awful noise and everyone turns and stares to see where it is coming from. Called dealer the day after they replaced pads and they basically said that they were waiting on someone else having the same problem and maybe GM would issue a bulletin  on what the fix is. I'm leaning toward a problem with the calipers or rotor but haven't got dealer convinced of that yet. Anyone else having any such problem?

Yup. Same problem. Could just be a little rust from moisture though. It goes away after a minute of driving. Gonna get an oil change soon. Gonna ask the service department about it. But yeah it is annoying as hell especially early on the morning when neighbors might still be sleeping.

Edited by Jaime Datuin
Posted
23 hours ago, econometrics said:

What a crock. All vehicles do that, my tuchus. I'm sure the rep at the dealer would be okay if their brand new vehicle did that? No way. Also, why does only ONE of my brake stations do this, and not all of them? Faulty/crappy pads, that's why (IMO). 

 

My truck is going to the dealer tomorrow for a host of repairs, this being one of them. If they feed me this line, I'm going to tell them to put some upgraded pads on the rear brakes and then tell me they "all do that". 

Any updates?

Posted
22 minutes ago, Jack Christensen said:

Any updates?

Went in for my scheduled appointment, but apparently the dealer did not have it confirmed. They didn't have any loaners available, so I'm going back next week. The main thing I'm going in for is the dreaded rear window leak, so I'm not in too much of a rush to get that process going. 

  • Like 1
  • 2 weeks later...
Posted
On ‎12‎/‎20‎/‎2019 at 7:15 AM, Jaime Datuin said:

Yup. Same problem. Could just be a little rust from moisture though. It goes away after a minute of driving. Gonna get an oil change soon. Gonna ask the service department about it. But yeah it is annoying as hell especially early on the morning when neighbors might still be sleeping.

Edited December 20 by Jaime Datuin

I don't believe that mine has anything to do with moisture and rust. I can drive to town and pull into a parking area and leave in 10 minutes and it still will make some noise.

Posted

I had them look at my rear brakes a few days ago when I was in for the rear window leak.

 

They fed me the line we’re all hearing here... “no visible signs of anything wrong after inspecting it, and could not replicate it. Be on your merry way, please, sir.” 
 

?

Posted

Has anyone tried lubing brake components? 10 years ago my Mazda had this problem and lubing the caliper pins stopped it. It was a known problem and I only heard it in the morning and backing out.

Posted
I thought about lubing my disc, but I heard that is not too smart. [emoji851]
 
Interesting advices, though. [emoji1360]


In the case of the Mazda it boiled down to one idiot on the assembly line who just didn’t care about his job. All of the cars off the line for almost a year had no caliper pin lube and created a big headache for Mazda. It happens.
  • Like 1
Posted

My 2020 High Country with 1400 miles on it has just started doing same thing, loud squeak backing out of the garage,.  Last week it was only backing up that made it squeak, now it’s doing it in drive as well.  Seems to go away after some driving,  but it’s painfully loud sometimes in parking garages etc.   turns heads for sure, going to the dealer next week to see what they can do.  Weak sauce if this was a problem that started in 2019 models, not to have a fix.

 

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