Jump to content

Who likes or dislikes the 2014 Silverado side steps in the rear bumper

PMattras

Recommended Posts

PMattras Enthusiast

PMattras

Posted
Posted

I personally do not like the side steps in the rear bumper. On a 4X4 these steps are quite high to use and I prefer putting a step in the trailer hitch which is a few inches (+/-) lower (which means a lot) than the bumper. This type of bumper with side steps isn’t a new idea because it was on other Makes/Vehicles over the years. The Chevy Avalanche /Nissan Xterra had it at one time and there was complaints the steps would rust out and collapse over time.

 

I don’t care for theses side steps and wish we had the option for the regular (w/o steps) bumper. I also think the regular bumpers looks so much better. Just something I wouldn’t use too much.

 

Have people been actually using these side steps in the rear bumper or just like them for the looks?

  • Replies 76
  • Created
  • Last Reply
Jay700 Enthusiast

Jay700

Posted
Posted

I like them and use them all the time. When I ordered the truck I was going too get a regular bumper and then changed my mind and got the steps glad I did.

soltys Enthusiast

soltys

Posted
Posted

When I first got the truck, I thought I'd never use them. Now, I use them all the time.

 

The hitch step may be handy, but what do you use when the tailgate is down. Around here, local laws don't allow for things to be left in the hidden hitch receiver on a regular basis because of rear end collisions.

jonny24 Enthusiast

jonny24

Posted
Posted

I love them. Haven't had to use mine much yet, but I remember it was like a year ago that I saw them on the new trucks. Ever since them every time I would step up on a bumper I would think "Gee, I wish this truck had those corner steps." Great idea.

PMattras Enthusiast

PMattras

Posted
  • Author
Posted

When I first got the truck, I thought I'd never use them. Now, I use them all the time.

 

The hitch step may be handy, but what do you use when the tailgate is down. Personally, local laws don't allow for things to be left in the hidden hitch receiver on a regular basis because of rear end collisions.

 

I have a step in the hitch that extends when the tailgate is down. Usually I don't drop the tailgate too much. Around CT a lot of people drive around with there ball hitch etc. in their receiver. I don't know of any local laws against it but I guess I should double check with the local police departments to make sure. Anyone in the US know about any laws of this type? Thanks for the heads up about this issue. I never thought about it.

 

 

 

Imcrazy Senior Enthusiast

Imcrazy

Posted
Posted

I love the step bumpers on my 4x4 sierra. I'm 5'11'' and the height is perfect for getting in and out of the bed.

Northside Enthusiast

Northside

Posted
Posted

While I don't think they look great, I like the steps for stepping into the bed.. They are just the right height for me. Stepping onto the top of the bumper is a bit of a stretch. I much prefer them to the fold out step in the tailgate of the F 150. Sometimes simple is best.

chuckl1218 Senior Enthusiast

chuckl1218

Posted
Posted

I use the steps all of the time - it really helps when the tailgate is down like others have said. I like 'em.

Spurshot Senior Enthusiast

Spurshot

Posted
Posted

I have a step in the hitch that extends when the tailgate is down. Usually I don't drop the tailgate too much. Around CT a lot of people drive around with there ball hitch etc. in their receiver. I don't know of any local laws against it but I guess I should double check with the local police departments to make sure. Anyone in the US know about any laws of this type? Thanks for the heads up about this issue. I never thought about it.

 

I couldn't find anything in the California motor vehicle code. local laws for motor vehicle equipment are not permitted in California and most other states. California code has nothing in the tow equipment section nor anything in the bumper section about leaving hitches in place. I have a forged steel step/ strap anchor i leave in place. It lets me know when ive backed into a parking spot against a wall at work and is a deterant in public parking lots. I love it.

SteveBBB Senior Enthusiast

SteveBBB

Posted
Posted

Like the steps? I love the steps, I even like the looks of them. Another small thing on the new trucks I really like is the driver side floor mat locked in place. I was always fooling with my mats to keep them in place.

Archived

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

Go to topic listing

  • 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,691 Guests (See full list)

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

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