Jump to content

Recommended Posts

Posted
1 hour ago, silveradonationfan15 said:

Any idea when the LT Trailboss will be available? I was going to make trip to the dealership next week about ordering one, Also first time I ever heard talk of a dealership wanting a down payment on a vehicle order.  usually its none  

We have two GMC dealers around here one requires a deposit the other doesn't.

Posted

I ordered an LTZ this morning. Did not need a deposit. It was also the only Northsky Blue the dealer had allocated to them, or at least I was told. This particular dealer had 60+ allocations. 

 

 

Posted (edited)

Ordered a 2019 Sierra Denali today. Dealer said order was accepted by GM. No pricing. Red with black interior. 6.2. Ultimate package, which pretty much takes care of everything. Disappointed in the interior color choices however. Wanted the tan like I have on my 17. Oh well...it will grow on me I guess.  

Edited by medic856
  • Like 1
Posted

Ordered my LT Trail Boss today. Found it odd that the Trail Boss only comes with 3.23 rear axle 8 speed tranny. Dealer said it matches the same output as the 6 speed 3.42 but will also be better in MPG. 

  • Like 1
Posted
16 minutes ago, packcrew said:

Ordered my LT Trail Boss today. Found it odd that the Trail Boss only comes with 3.23 rear axle 8 speed tranny. Dealer said it matches the same output as the 6 speed 3.42 but will also be better in MPG. 

As far as first gear goes, the 8 speed is almost an exact match for the 6 speed and 3.73 gears.  

 

But if you ever wanted 33-35" LT tires, the 3.23s won't be great. 

Posted

We just got our order number

   Order # WDPP57

Posted
43 minutes ago, Zane said:

We just got our order number

   Order # WDPP57

I heard you can track them on GMAuthority's site but I don't know how reliable it is.

  • 2 weeks later...
Posted
On 5/22/2018 at 7:47 PM, RJP44 said:

Has anyone heard an MSRP on a trail boss yet? 

 

X2, The trail boss looks sweet. Does it have a factory leveling kit?

Posted
On 6/2/2018 at 11:01 PM, shift_grind said:

When do the build and price pages start going online?

Should be the 18th ot this month I believe. That's when they are allowing the building for ththe sle and at4. I'm pretty sure pricing is out ththiththis month. 

Posted

I broke down and bought an 18 denali ultimate. It gives me most of the features I like about the new ones. I would like hud and 360 view. But the fact the engines changed imo for the worse with the unproven dynamic fuel management. I figure the 18 denali is already amazing. I'll wait for the new model refresh in 2 to 3 years and see what I think. I mean the truck was fresh off the trailer for 50k. 

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