Unable to hit commanded load

Enki

Enki

Motorhead
Platinum Member
Greenie Member
@steve@versatune
I really hate to bug you directly and publicly like this, but I've been trying to figure this out for months and even @mituc hasn't been able to help me figure it out.

2009 (08.5) MS3 big turbo, stock fueling.

Currently commanding 2.0 load in the low bat by gear tables from 3k to 5k RPM (2.5 or 3.0 literally everywhere else) tapering off. I'm hitting full boost by 4k, but only hitting 1.8 load (1.9 peak) and it's pulling WGDC. In order to hit my WGDC targets and/or load targets, I'm having to add between 0.15 and 0.2 load across the board and it's proving to be super annoying to get dialed in, as the number seems to increase with more requested load.

Oh, and I have IDC and boost limits well above what I'm actually hitting, and boost compensation is wholly disabled.

Is there some hidden checkbox somewhere I need to flip to get this to work properly? If I had any hair I'd already have pulled it all out by now.

If needed, I'll pull a new log with a new map, but I've sent a few to Mituc already and can just forward those to you if you want.

Thanks!
 
09 for me. I'll get fresh logs and a map and PM it to you later today.
 
My issue as of now has been resolved. It seemed like I was hitting some sort of load safety stuff even though it was set higher then I was actually seeing on the logs. I ended up bumping them to 3 and then I no longer saw strange afr's like the car was trying to adjust based on some limit I was hitting but not seeing. I changed the below tables and it worked so I left it. Eventually I plan to go back through and bring them down but I still have other limits in place so I am not super worried. Right now tuning is at a hault as I am out of fuel and it is too cold to do anything decent.

Load Limit Force Spark
Operating Load Limit 1
Operating Load Limit 2
Overload Protection Fuel Cut
APP Requested Load Normal Extended
APP Requested Load Overload Extended
 
I've heard that's a nightmare in and of itself.

I finally broke down and did the math (note that this is as of yet untested); I'd attach the spreadsheet but it's not an allowed extension.

upload_2020-4-27_11-44-54.png

Formula is as follows:
New Target Load = Target Load / (100 / (Target Load / Logged Load)) * 100
Scale = Target Load / Logged Load

Edit: For any numbers way outside of bounds (pre spool, etc) just use the target load value to avoid potential explodey issues.

Edit 2: Fixed math. Sorry!
 
Last edited:
First pull on first flash with new load values:

upload_2020-4-27_14-25-11.png

Compared to old map with straight up targets:
upload_2020-4-27_14-26-42.png

I didn't adjust *ANYTHING* else (tune wise, only changed the load by gears tables) so the initial load overrun (caused by high WGDC targets) is probably holding the curve down a bit further than normal; this might even out with successive pulls, but so far looks promising as a workaround until this is ultimately fixed.

Now that it's warmer out, I'm likely running into temp issues top of the curve (128 deg @ 1.5 load vs 146 deg @ 1.65 load).
 
Eroler1 said:
View attachment 14194
PS: Im not bashing on my wonderful tuner @Atvfreek . just a little bit of butthurt on my side since cant see the full potential of my setup with VT
Click to expand...
Hmmm, makes me less excited to start tuning mine for power on VT although I am not going for crazy power "5862"so maybe it will be ok and it is free to self tune so I got that going, really wish AP was not charging for their tuning software just adds even more to the cost.
 
You must log in or register to reply here.
Back
Top