Jump to content

Recommended Posts

Posted (edited)

Today’s the first of two. Medium sized today. Super Sized Saturday. Traditional today. Ham, cheese potato, macaroni and cheese and baked beans on Saturday. Then Sunday decorate the church. Monday drive to Oklahoma to help my cheap a$$ brother in law. First unload his latest haul to his new house. Then some painting. Both things I paid to have done when I needed it done. My wife is in total amazement that I said yea I’ll help. She painted the living room during the freeze two years ago while I watched. I just can’t so no to her brother. The man has talent in spades. Can’t wait until he finally retires and starts on his Firebird. Well I hear the wife now, my work is about to start. Happy Thanksgiving!

Edited by KARNUT
  • Like 1
  • Thanks 1
  • txab changed the title to Happy Thanksgiving 2024
Posted

Round Two done. Thirty people. Five crockpots. Three gallons of tea. Plenty of desserts. Getting ready to watch the Aggie game. Dishwasher going.

  • Like 1
Posted
2 hours ago, KARNUT said:

Round Two done. Thirty people. Five crockpots. Three gallons of tea. Plenty of desserts. Getting ready to watch the Aggie game. Dishwasher going.

Stan I’m too tired to come visit you. I nap all

the time now. Know how much you miss me. No need to lament it. 😭

  • Haha 1
  • 11 months later...
Posted

This year round 1 is Sunday just 20 people. Turkey day just 10. One brother in law is going out of town. The other now retired is having his family over at the new house. No painting there this year. He’s been remodeling though. I’ll be going up soon. Who knows what’s in-store. Haven’t been since the Aggie season started, he’s been coming here to go to home games. What a season they’ve had. 

  • Like 1
  • txab changed the title to Happy Thanksgiving 2025
Posted

The father in law is coming to visit, and we're hosting Thanksgiving. I enjoy him, so it's a welcome occasion. I'm looking forward to NOT having to travel this year, and also having it at our house for a change. Everyone is in good health and spirits, this is going to be a good one.

  • Like 3
Posted

Hey if you have an Sig Sauer P320 be careful. It might fire in holster on its own. Could ruin your Thanksgiving. 
 

 

Posted (edited)

After its all said and done it was enjoyable. For about 15 years now since my wife had years of surgery I’ve helped with the cleanup after these events. In my growing up years men didn’t go in the kitchen. For the first 35 years of our marriage it was that way in my house. I take care of the outside the inside is the wife’s domain. She was raised that way too. She’s mostly recovered from the first botched surgery. I still help with domestic ( inside the walls) of the house. But being a touch OCD I do most of the clean up after big meals. I prefer more individual meals like we do during the year. One family at a time. My wife likes them all at once. I have to be honest. I’m glad it’s over. Christmas is more spread out. They trickle in and it’s more of a crock pot affair, spaghetti and meatballs. The next big and last for the year is Super Bowl and hoagies. My son took over New year's. Thank goodness. Then NASCAR and baseball. Yeah!

Edited by KARNUT
  • Like 2

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...