Jump to content

Recommended Posts

Posted

Good morning guys. First time poster but have lurked for a while. I searched for this topic and did find some information but not for this body and year so I figured I’d ask here. 

I want to install power steps to my 2019 SLT Crew Frost White 4WD. I would like the chrome power steps and can not seem to find any aftermarket other than black. I’ve seen some on a local white vehicle and to me the black stood out a lot when folding up and I did not care for the look. I’d like it to be more clean/sleek looking. 
 

Are there aftermarket chrome powers that I’m overlooking? 
 

My salesman told me that the Denali powers can not be put on the SLTs because it doesn’t have the RPOs? I’m certain that someone has a work around for this. 
 

Has anyone done this? What special wiring is needed? What is the part number for the Denali Power Step package?

 

Any and all photos and information are welcomed. 
 

 

 

 

C1B177C9-246E-43BD-8E21-FA756D74FC9D.jpeg

Posted
2 minutes ago, Unwrntd said:

I’ll sell you my oem steps, not sure what it would take to make them work though 

How much? I don’t see why they wouldn’t work same as aftermarket if wired the same way. But that’s just me thinking. I really have no clue. 

Posted
On 10/14/2021 at 7:08 PM, Nasen Soileau said:

How much? I don’t see why they wouldn’t work same as aftermarket if wired the same way. But that’s just me thinking. I really have no clue. 

$700ish  for the pair I think. Only issue is the wiring harness is too difficult to remove, so it wouldn’t come with.

Posted
On 10/9/2021 at 9:43 AM, Nasen Soileau said:

Good morning guys. First time poster but have lurked for a while. I searched for this topic and did find some information but not for this body and year so I figured I’d ask here. 

I want to install power steps to my 2019 SLT Crew Frost White 4WD. I would like the chrome power steps and can not seem to find any aftermarket other than black. I’ve seen some on a local white vehicle and to me the black stood out a lot when folding up and I did not care for the look. I’d like it to be more clean/sleek looking. 
 

Are there aftermarket chrome powers that I’m overlooking? 
 

My salesman told me that the Denali powers can not be put on the SLTs because it doesn’t have the RPOs? I’m certain that someone has a work around for this. 
 

Has anyone done this? What special wiring is needed? What is the part number for the Denali Power Step package?

 

Any and all photos and information are welcomed. 
 

 

 

 

C1B177C9-246E-43BD-8E21-FA756D74FC9D.jpeg

There is a switch in the center stack that allows you to extend, extend to tire, and disable the boards. It would be pretty involved if you are going that far.

Posted
2 hours ago, gemarsh said:

There is a switch in the center stack that allows you to extend, extend to tire, and disable the boards. It would be pretty involved if you are going that far.

Couldn’t it somehow be wired like the Amp aftermarket? I’m more about the chrome look (over the black) than the functions that the Denali has with these steps. Just want to open and close with the doors. Thanks for the feedback so far. 

Posted

They are very easy to wire. I installed them in my 2019 sierra slt. I had a hard time finding the parts but the harness Dr provided all connectors. I have prints if anyone needs them. I also got the center stack switch. 

Posted
26 minutes ago, Mora84 said:

They are very easy to wire. I installed them in my 2019 sierra slt. I had a hard time finding the parts but the harness Dr provided all connectors. I have prints if anyone needs them. I also got the center stack switch. 

I would definitely appreciate any and all parts, numbers, prints etc that you have!

Posted
17 hours ago, Unwrntd said:

$700ish  for the pair I think. Only issue is the wiring harness is too difficult to remove, so it wouldn’t come with.

Where are you located? I’m in south central Louisiana. 

Posted (edited)

AirForceAngler, Care to explain why they are garbage?

Edited by RAYS B4U
Posted
2 hours ago, AirForceAngler said:

FYI..Factory power steps are garbage.

Why’s that? Before I go through any trouble I’d live to hear your opinion. 
 

I really just want a chrome power step. I can’t seem to find the aftermarket. 

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,694 Guests (See full list)

  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...