Jump to content

Recommended Posts

Posted (edited)

2007 GMC Acadia.  Brand new platform and first year.  We special ordered it was soon they were taking orders.  Waited months to get it.  From a design and features standpoint it was perfect for our family.  
 

problems from day one.  Transmission programming, sunroof leaks, squeaky brake pedal, moaning steering.  The dealer really tried, replaced the steering rack, pump, column, master cylinder, and performed numerous TSBs. It made so many awful sounds we named it Mona. 
 

Final straw was when the water pump failed, it overheated, shutdown and left my wife and son stranded on the road.  
 

Traded it in with only 41,000 miles on it, and she’s been in a Yukon and Tahoe ever since.  Still to this day she says that was her favorite car from a design and fitting her needs standpoint.  But she refuses to get another because of the experience with that one. 

Edited by tsdrumm
Posted

1968 FIAT 850 Coach

75 HP rear mounted engine

needed to take off distributor cap and spray it with dry-all to start in rain.

when it ran and it was usually better down hill it did get 50mpg

Posted

I would have to say, my '81 Harley.  It was the first year Harley took the company over from AMF, and let me tell you, what a POS. 

  • txab changed the title to Your least reliable vehicle ever.
Posted

My current 2019 Silverado probably. 8 warranty service visits in around 2 years.

-rear window leak 2x

-oil cooler line leak (last month)

-total brake failure

-rear brake squeal (current)

-parking sensor module failure

-steering column replaced for loose shifter

-3 phantom check engine lights, one flashing

-2 phantom service ESC lights

-third brake light filled with water

-various software bugs (some still persist)

 

It’s never stranded me though. The brake failure and flashing check engine almost did, but they occurred close to home and fixed themselves on the next key cycle. 

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