|
Title: Skip KFMIRL and request torque model all together -> direct PED = torque Post by: elRey on March 06, 2012, 04:35:57 PM Any tried skipping the whole requested torque model and use the PED = requested torque?
function MDFUE Set bit 2 in CWRLAPPL = 1 then set factor FWPEDRLS to reach your desired torque If PED max = 100 and desired max torque = 250, then FWPEDRLS = 250/100 = 2.5 Be warned, this by-passes max requested torque limits like LDRXN, KFLDHBN, etc Thoughts? Title: Re: Skip KFMIRL and request torque model all together -> direct PED = torque Post by: julex on March 06, 2012, 04:52:19 PM Any tried skipping the whole requested torque model and use the PED = requested torque? function MDFUE Set bit 2 in CWRLAPPL = 1 then set factor FWPEDRLS to reach your desired torque If PED max = 100 and desired max torque = 250, then FWPEDRLS = 250/100 = 2.5 Be warned, this by-passes max requested torque limits like LDRXN, KFLDHBN, etc Thoughts? Then you use KFLDHBN which is the way I control my boost anyway. I like it, if it works. You tried yet or is this all theoretical? Title: Re: Skip KFMIRL and request torque model all together -> direct PED = torque Post by: elRey on March 06, 2012, 05:29:27 PM You tried yet or is this all theoretical? theoretical Title: Re: Skip KFMIRL and request torque model all together -> direct PED = torque Post by: nyet on March 06, 2012, 06:01:34 PM i like it.
does this also theoretically bypass all of the torque monitoring too? Title: Re: Skip KFMIRL and request torque model all together -> direct PED = torque Post by: matchew on March 06, 2012, 08:40:39 PM Good luck with getting a good idle with this.
Title: Re: Skip KFMIRL and request torque model all together -> direct PED = torque Post by: phila_dot on March 08, 2012, 01:06:28 PM Then you use KFLDHBN which is the way I control my boost anyway. This skips rlmax entirely. KFLDHBN is not considered. i like it. does this also theoretically bypass all of the torque monitoring too? It bypasses the torque path entirely in the calculation of desired load. I don't think this will disable torque monitoring or torque monitoring level two, but it basically disables all forms of load intervention. It looks like all other forms of intervention via the torque path will still apply. I like inventive solutions, but I wouldn't use this. Does anyone really have a problem with desired load? |