I mapped out these maps for throttle filtering. Is this what is needed to make the throttle more responsive?
If so, which ones are needed and what do you set them to? Just zero them?
Thanks
Throttle filtering maps.jpg
I mapped out these maps for throttle filtering. Is this what is needed to make the throttle more responsive?
If so, which ones are needed and what do you set them to? Just zero them?
Thanks
Throttle filtering maps.jpg
Basically those are the time constants for the pedal filtering (think like an RC Curcuit). The time constant is typically ~1/4th the time for a system to reach the transient response, or in this case for the actual torque to equal requested torque. By setting those to 0 you are making the pedal to torque system react instantly, with no time delay. There should be 2 tip in as well as 2 tip out map for all gears, including reverse and neutral. One of those is open powertrain (TC unlocked) and one for close (TC locked) you need to zero all of them of you want no delay ever.
A lot of this can also depend on the pedal to toque map, if its pretty aggressive at lower pedal positions this can easily make the truck really jerkey. I actually made my pedal to torque a little less sensitive off idle and it helped, while keeping the instant response.
isnt that the same as ramp time? instead of zero wouldn't you want to make everything 1.0?
Have any of you guys done a 13-14 with an upgraded charger from a 15/16 truck?
I'm having some trouble getting off idle response where I'd like it. Any tips would be appreciated!
They are under "DRF" Driver request filter. The Maps are labeled "base time constant for reference filter in gear position 1 corresponding to engine speed and actual engine torque (tip-in)" and so on for the rest of the gears. Tip in and tip out for all gears, open powertrain (TC unlocked) and TC locked.
I have those mapped, but noticed little to no difference zeroing the maps. Maybe a touch more fuel being added, but I can't get the charger to come on sooner than 1800-2k rpm.
I'll double check my UDF file... maybe I botched something there. It sure seems like the inferred vgt position is just wrong.