You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure why the coefficient here can go to 3 - I'd think it should only be possible to define a maximum of 1, which to my understanding would mean that 100% of the calculated charge temperature would be coming from the IAT.
Looking at speed_density.cpp it looks like rpmMin and rpmMax might be hard-coded to 500RPM and 8000 RPM respectively, so setting a number higher than 1 could allow the coefficient to hit 1 (and be clamped to 1) at a lower RPM than 8000 RPM. I'm not sure if this intended behavior but it may be better to expose the values for low RPM and high RPM as user configurable settings.
reference: fome-fw/firmware/controllers/math/speed_density.cpp: lines 25, 26, 103-106
The text was updated successfully, but these errors were encountered:
fome-fw/firmware/integration/rusefi_config.txt
Lines 1154 to 1157 in fabfd6a
I'm not sure why the coefficient here can go to 3 - I'd think it should only be possible to define a maximum of 1, which to my understanding would mean that 100% of the calculated charge temperature would be coming from the IAT.
Looking at speed_density.cpp it looks like rpmMin and rpmMax might be hard-coded to 500RPM and 8000 RPM respectively, so setting a number higher than 1 could allow the coefficient to hit 1 (and be clamped to 1) at a lower RPM than 8000 RPM. I'm not sure if this intended behavior but it may be better to expose the values for low RPM and high RPM as user configurable settings.
reference: fome-fw/firmware/controllers/math/speed_density.cpp: lines 25, 26, 103-106
The text was updated successfully, but these errors were encountered: