Jump to content

Happy to be an HD owner!

corn18

Recommended Posts

corn18 Enthusiast

corn18

Posted
Posted

Hello!  New member and very happy to be part of the HD crowd.  I towed travel trailers for years with a 2005 Tundra and then a 2008 Tundra and always had them maxed out due to payload limits.  Been without a truck since 2016 and felt it was time.  Decided that this time around it would be HD.  Didn't have brand preference and gas is fine.  The weird part of my search was almost all the used trucks are white.  Anyway, ended up finding a 2015 2500HD WT with 52,000 miles.  It was just down the road and in immaculate condition.  The WT configuration is perfect.  Has everything I need and nothing I don't.  It does have a cloth interior which was a requirement.

 

Now I can start looking at travel trailers and not worry as much about maxing out the payload.   First mod will be a bed cover.  Probably Truxedo or the like.  And a bed mat.  

 

spacer.png

dplarson Enthusiast

dplarson

Posted
Posted

Welcome to the HD club. This is my first as well. I come from Suburbans before the truck.

'17 2500HD 6.0 gas WT (mine's a GMC so it's called "base" but same thing). I love the manual lever on the floor for the 4WD shifting.

About the color... White is right!

 

 

 

Sent from the demons in my head

 

 

 

79e8d3a519840714a35eae35d10511ca.jpg

i82much Enthusiast

i82much

Posted
Posted

white 2016 gas work truck here, i daily drive it and use it as the family vacationmobile.  snugtop canopy for the dogs and luggage.  i can’t imagine needing any more truck than this!

Big Whiskey Senior Enthusiast

Big Whiskey

Posted
Posted

Welcome! You'll enjoy having a real truck, haha. Mine is my first HD, and I don't think I'll ever go back to a 1500. 

  • 2 weeks later...
ewbldavis Enthusiast

ewbldavis

Posted
Posted

White Pow...nevermind.

 

Nice truck. Good luck on TT hunt! We really liked the Sport Trek's. 

 

Our next one will require a bed mounted accessory ?

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • 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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...