Jump to content

Recommended Posts

Posted
17 minutes ago, alkrisma said:

 

E1EB9051-736F-4A50-950B-725826FC0180.jpeg

I'd love for you to show me in these screenshots from the manual where it specifically mentions Grade Assist Braking, which is 100% DIFFERENT from Hill Assist whats meant for steep slopes.  The mode I am referring to activates when I'm on the freeway going down a grade at 20-40 mph, not a steep gravel road.

Posted

There must be tow/haul grade braking and regular grade braking then because mine kicks in outside of tow haul mode also.

  • Like 1
Posted
9 minutes ago, Sir Dan said:

Check out this thread.  6 and 8 speeds are different also I believe.  

 

 

I just read through that thread... That talks about Turning the feature on and off.  I'm asking about how to manually activate it the same way it's triggered by light brake pressure and temp. I WANT to have it kick in on certain grades where it works well, but it only does when its hot out.

Posted (edited)

You can't just turn it on. The computers decide when it wants to turn it on. Sorry. You can always just use manual mode and down shift. 

Edited by Sir Dan
Posted
1 hour ago, Sir Dan said:

Grade braking is active by default. You hold in the tow haul button for like 5 seconds to toggle it on/off. It is then reset to on with every key cycle. The owners manual is great for things like this you know....

Don't tell me. I've only read a K2 owner's manual once, right before my purchase fell through. ?

Posted
1 hour ago, Sir Dan said:

You can't just turn it on. The computers decide when it wants to turn it on. Sorry. You can always just use manual mode and down shift. 

Bummer.  That's the problem I was hoping to avoid.  Grade Assist Braking doesn't require throttle modulation to keep a constant speed.  Using Manual Mode does.  

Thanks anyway.

  • 3 weeks later...
Posted

Has anyone figured out a way to keep the front Daytime Running LEDs active while also using the turn signal on 16-18 LTZ? I've had numerous people tell me I have a headlight burnt out because it disables the light when the blinker is active. I just tell them thanks as I don't want to explain what's going on:-)

 

Posted
Has anyone figured out a way to keep the front Daytime Running LEDs active while also using the turn signal on 16-18 LTZ? I've had numerous people tell me I have a headlight burnt out because it disables the light when the blinker is active. I just tell them thanks as I don't want to explain what's going on:-)
 
That does make your turn signal more visible, my old dodge did the same thing.

Sent from my SM-A705W using Tapatalk

Posted
1 hour ago, XPSer said:

Has anyone figured out a way to keep the front Daytime Running LEDs active while also using the turn signal on 16-18 LTZ? I've had numerous people tell me I have a headlight burnt out because it disables the light when the blinker is active. I just tell them thanks as I don't want to explain what's going on:-)

 

First time I saw it on my nephew's vehicle I almost said something to him, but I figured out.  Maybe people will learn eventually.

Posted
1 hour ago, XPSer said:

Has anyone figured out a way to keep the front Daytime Running LEDs active while also using the turn signal on 16-18 LTZ? I've had numerous people tell me I have a headlight burnt out because it disables the light when the blinker is active. I just tell them thanks as I don't want to explain what's going on:-)

 

Welcome to the site.

 

This is what mine looks like when I have the park lights on:

 

 

100-5.jpg

100-6.jpg

100-7.jpg

Posted
5 hours ago, XPSer said:

Hmmmm. How did you get them this way?

Park lights on (not headlights, but will work the same) and had the hazards on. 3 pictures in sequence from top to bottom.

 

I like the look of the yellow LED's on the LTZ, and was asking if anyone knew how to change the "hue" from white to yellow when the lights were on, no luck.

  • 3 weeks later...
Posted
On 4/14/2020 at 4:32 PM, XPSer said:

Hmmmm. How did you get them this way?

Those are LTZ headlamps. LT and the rest have a halogen lower element.

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