Anyone start seeing throttle corrections on a custom map since latest update 3.09? I’ve had all throttle intervention bits toggled off for some time now without issue and haven’t changed anything related. I tried with/without lambda oscillation fix checked which was something new I had done but already had it baked into the tune. Could that have anything to do with it?
N54 MHD+ New Tables Talk
- Thread starter corbanistan
- Start date
How did you do that?
I can only manipulate it a little bit with Threshold value lowered.
The bits don’t really keep the throttle open in an overboost condition I was just stating they were off for troubleshooting. You have to move the load request out of the way to stop them so you run well below load target all the time. This stopped working for me at least with the last update. Is there a safe/preferred source for an earlier Android version APK? @Jake@MHD
I’m terrified of downloading an earlier version from a random source on google and bricking my DME. See attached photo load request-185, load actual-164, boost target-24, boost-23.9 = throttle closure? Boost ceiling set to 1.50 for a scaled 3.5 bar. Last pic is of V3.03 I was running prior spike to 24.5 with no intervention…
Attachments
Last edited:
Throttle will close for boost overshooting or traction control.
You can turn off throttle closure for overshooting boost by using the existing tables in the public XDF. The "Threshold (Major Throttle Closure)" can be lowered to something like 0.9 which gives you massive leeway for over boosting and "Throttle Angle Aggression in Overload" can just be set to 1.
Don't know why you'd want to do that though. You should be able to control boost.
You can turn off throttle closure for overshooting boost by using the existing tables in the public XDF. The "Threshold (Major Throttle Closure)" can be lowered to something like 0.9 which gives you massive leeway for over boosting and "Throttle Angle Aggression in Overload" can just be set to 1.
Don't know why you'd want to do that though. You should be able to control boost.
I know what can be done there. I’m just trying to understand why this update is suddenly causing throttle intervention well below load req and boost ceiling.
It can be caused by the transmission, traction control or other safeties. Post your full log up on here and I can take a look.
Hmmm I haven’t checked reported tq on the trans side in a bit. I wonder if anything has changed there for the jerkiness stuff people are talking about. I had been assuming that was all driver input related. Not much to see here on the log since I haven’t logged tq limiters yet so I will try that later. I always have DSC fully disabled with long press. Car is IJE0S xDrive with 8HP swap via CANTCU just for reference. Don’t mind the boost dip post shift I had been testing CAN triggers to boost solenoids before this update halted progress.
Last edited:
What do your "Threshold (Major Throttle Closure)" and "Throttle Angle Aggression in Overload" tables look like?
Also have you played with the boost target modifier tables? This might happen if you put values lower than 1 in there.
Also for the TCU swap. How are the torque reduction values managed? If the slow torque reduction value from the TCU is too low then you'll see the throttle close. This isn't normally a problem but for an 8HP swap you might have problems.
Also have you played with the boost target modifier tables? This might happen if you put values lower than 1 in there.
Also for the TCU swap. How are the torque reduction values managed? If the slow torque reduction value from the TCU is too low then you'll see the throttle close. This isn't normally a problem but for an 8HP swap you might have problems.
Threshold is .985 and aggression goes from .5@0 [email protected] and .99 thereafter. Boost target modifier is 1.0 flat. Same as I’ve run for years. I fully understand I can numb these further and get rid of this. I just want to know what is causing it. The TCU is an oem integration it is running its respective XHP stage 3 tune. Typically the request from the trans is 275nm or so which is still showing similar in the log. It will do the same on a minor overboost mid gear as well so I doubt it’s trans related.
Edit: I should note that I played with a new table when I did the initial long write for the update. KF_FWGZUEKOR “Wastegate correction factor for ignition angle interventions” starting address 5D98E but I returned it to stock immediately when I saw the throttle correction thinking it had something to do with it. If you know any further info on that table that would be helpful to me on my side quest as well
Last edited:
He's right, with those tables your boost mean will cause throttle closures. You are at 26.2boost 24target (0.916), your threshold is at 0.985 so anything over 24.3psi will cause closures.
It's nothing to do with load limit or boost ceiling.
Hmmm I haven’t had them for a very long time now with much worse. Attached is a spike from MHD v3.03.
Update: Added a couple more snips digging through older logs. One multi gear from the when I ported to map switch. And another when I was testing the new commanded wgdc strategy. Both on the original MHD v3.0
Update: Added a couple more snips digging through older logs. One multi gear from the when I ported to map switch. And another when I was testing the new commanded wgdc strategy. Both on the original MHD v3.0
Attachments
Last edited:
I'm facing the same since v3.09. 335i rwd 07 i8. All my tunes even the old ones now have throttle corrs and weird boost target. @Jake@MHD
Also similar problem since last update. Boost target no remains .6 psi under what's set in the new boost control table.
Similar. I will try v3.05 tomorrow and update. Sheesh, thought I'm f*dup something.
I did aswell. Finally had time to test some things and moving the boost setpoint closer to 1.000 brings the target closer to whats set in the boost tables.
Similar threads
