Jump to content

Recommended Posts

Posted (edited)

I currently own a 2017 2500 HD Duramax Diesel LTZ. It has the peddle adjust feature which is extremely important to me since I have very long legs.  I was going to trade it in but found that the 2020 version of this truck did not include the peddle position adjust.  This was really key to my decision in purchasing and based on them not having this function, I delayed my decision hoping this feature would be in the 2021 truck.  Does anyone else feel they need to add this feature back into the truck for the next model years?

Edited by Joseph Dymond
Posted (edited)

Not as long as the seat can be pushed far enough back for the legs, and the steering column can then be extended enough to suit the arm length. 

 

 

I always figure pedal adjust was more useful for those with short legs that wanted to be further from the dash.

The firewall doesn't move, and with 'non-moveable' pedals, wide open throttle is with the pedal against the firewall. 

Edited by redwngr
Posted

I've driven vehicles with adjustable pedals.  I don't see any need for them.  The 2020 pedal placement is right on the money for me.  

Posted

I had that feature on my Dodge Ram.  In 16 years, I never used it.

 

Posted

Guess it's a personal preference and where you prefer to be positioned in the cab. I'm 5'10 and I never used the adjustable pedals in my old truck. 

 

I do however, hate that my fully loaded AT4 doesn't have electric tilt/telescoping steering column like on my 2018 Denali. I love the feature of the seat going all the way back and the steering wheel moving up upon entry/exit

Posted

my issue is relationship between gas and brake....brake pedal is like 3 inches closer (to the seat) than the gas, i would love to get them more even with each other....maybe get brake pedal pushed closer to floor a few inches.....my toyota was almost dead even

  • Like 1
Posted

Wondering if you test drove the new one very far? These cabs are bigger. Sorry I can't speak for adjustable pedals, but for an example. I'm not huge, but I'm 6-1 and don't have full use of my right leg after a cycle accident years a go. In my 05 crew cab, I had usually had to tilt the wheel to get in and out, even with the seat all the way back. I also had to tilt the wheel in a position that was less comfortable to cruise with, to fully see the guages. In my 20 Custom CC, I was concerned about losing power adjustments. But with a roomier cab, I have them set where I like and don't need to touch anything to get in and out. Sucked losing the airbags, though. Maybe a mod later.

Posted
On 8/13/2020 at 3:50 PM, Dunn said:

my issue is relationship between gas and brake....brake pedal is like 3 inches closer (to the seat) than the gas, i would love to get them more even with each other....maybe get brake pedal pushed closer to floor a few inches.....my toyota was almost dead even

I was driving down the road today thinking the same thing. I almost get my foot caught on the brake while transitioning. You can’t leave your heel on the floor and rotate anymore. I suppose I’ll get used to it but would be nice if there was an adjustment for the two pedals to be more “flush” with each other. 

Posted

I missed it initially. I had a fully loaded 2017 Duramax and loved that I could adjust the pedals to where I needed them. I have short legs and long arms and like my arms stretched out when driving. So I would adjust the pedals closer to me. I noticed it right away on my new truck, and it pissed me off that they didn't include this feature, but coming up on a year now of owning it, I forgot its not there. 

Posted
On 8/17/2020 at 8:25 PM, Pastusak.t said:

I was driving down the road today thinking the same thing. I almost get my foot caught on the brake while transitioning. You can’t leave your heel on the floor and rotate anymore. I suppose I’ll get used to it but would be nice if there was an adjustment for the two pedals to be more “flush” with each other. 

or get seat position to be comfy with both pedals.....one pedal is either too close or too far no matter how seat is adjusted.....there is a company called ultimate pedals but i dont think they offset the pedals as much as is needed

  • 1 year later...
Posted

I have 2018 Silverado. I was going to trade it for a 2020. I had to walk away the day we were signing the documents. I won't settle for a truck without adjustable pedals. I'm 5'1. The adjustable pedals allow me keep distance between me and the steering wheel. It allows me to sit in seat and reach the seat belts. Sounds like I won't be purchasing a 2021. 

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

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