Jump to content

Your least reliable vehicle ever.

KARNUT

By KARNUT
in The Off-Topic Bar

 Share

Recommended Posts

tsdrumm Enthusiast

tsdrumm

Posted
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
JimMLINY Enthusiast

JimMLINY

Posted
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

TheGeek Enthusiast

TheGeek

Posted
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.
OnTheReel Senior Enthusiast

OnTheReel

Posted
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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...