Pages: [1]
Author Topic: Skip KFMIRL and request torque model all together -> direct PED = torque  (Read 6158 times)
elRey
Hero Member
*****

Karma: +32/-1
Offline Offline

Posts: 565



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?
Logged
julex
Hero Member
*****

Karma: +79/-4
Offline Offline

Posts: 923



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?
Logged
elRey
Hero Member
*****

Karma: +32/-1
Offline Offline

Posts: 565



You tried yet or is this all theoretical?

theoretical
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12271


WWW

i like it.

does this also theoretically bypass all of the torque monitoring too?
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
matchew
Hero Member
*****

Karma: +47/-22
Offline Offline

Posts: 503



Good luck with getting a good idle with this.
Logged
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709



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?
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.017 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)