Jump to content

I bought the wife a new ride


Recommended Posts

Posted

The old one had a run in with a tree. Not totalled but I have no intentions of ever riding in it again.

 

Old one

 

2c81d2094e96eb122b8626eb7a92cf6f.jpg

 

 

 

New one

 

bdf87ad205da58497aa85c27c2936232.jpeg

 

2017 Yukon Denali

 

 

Sent from my iPad using Tapatalk

Posted

Nice

 

Looks like the tree won the first battle

Posted

It was parked at the school she works at, while at a teacher work day prior to students returning from summer. It was there for 20 minutes after she got to work(per the school camera), then decided to roll down a big hill in reverse. Oak tree at bottom of the hill pretty much removed the drivers side of the truck.

 

 

Sent from my iPad using Tapatalk

Posted

Sorry about your Tahoe loss..

Still partial to those criters...

 

New ride is sharp..

 

Cheers----K

Posted

Mmmm that wheel on the Denali... :drool::drool::drool:

I was thinking the same thing.. that would look sharp on my truck.. :D

Posted

Well, that's one way to upgrade. Happy to hear that your vechile was the only one damaged... besides the tree that is. Congrats on the new ride!

Posted

She wouldn't have been able to remove the key unless it was in "Park". Any ideas on what caused this?

 

Over the decades, automatic transmissions have had problems keeping the parking paw engaged. Ford had some infamous problems that went on for many years.

Posted

She wouldn't have been able to remove the key unless it was in "Park".

 

That model of Tahoe has push-button start. My driveway is on an incline and I remember shutting off the truck w/o putting the gear in park and forgetting to set the park brake, the truck rolled. Very likely this is what she did, and on a big hill..., hello oak tree.

Posted

That model of Tahoe has push-button start. My driveway is on an incline and I remember shutting off the truck w/o putting the gear in park and forgetting to set the park brake, the truck rolled. Very likely this is what she did, and on a big hill..., hello oak tree.

 

Another "advantage" of push button ignition.

Posted

I went from a 2015 Denali XL to a 2017 a couple of days ago. Nicely improved. The ride is much more compliant and the trans is much nicer. Seats are softer too. Overall it is that little bit better that is making it a nicer truck. Congrats and good luck

Archived

This topic is now archived and is closed to further replies.

  • 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   5 Members, 0 Anonymous, 2,096 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...