Any idea why i am seeing 7500+ load calcs while cruising @ 3200 rpm and 13000+ while starting from a stop?

 

More info.. Which app, etc..

 

i'm getting it in evoscan, mitsulogger, and ECU edit.

It goes lean for a sec then spikes the af at 10.0.

 

Sounds like you have to take a look at your cruise fuel trims I guess..

Load is not really calculated correctly at cruise and part throttle due to closed loop operation.. However the 1C ECU Load is correct at closed loop..

You might have to post the log for us to see for sure, Usually when I get that error, its because invalid data somehow got into one of the load calc columns, either due to a dropped request, or a late response in a previous request..

If all three apps do it, then its definitely related to the output of the ECU, only now we need to see what it is its logging for IPW and AFRMAP I figure one of those two values is throwing off the value..

 

Running evoscan .97 I saw a peak load calc of 337 during a pull tonight. That seems very high to me considering I'm stock turbo, stock motor at 23-24psi peak boost. is the load calc in evoscan inaccurate?

 

Wow I dont think I have ever seen peak load above 280....337 seems way high....Maybe you were going up a crazy steep hill in 6th gear....

 

Calculated load is a calculated value. Assuming that EvoScan has the correct formula, then its possible that the ECU was outputting inaccurate values for either IPW, AFRMAP or battery voltage. You can try to determine the highest load cell accessed in your timing map during your run by looking at the timing numbers and RPM from your run.

From what I've seen, load corresponds roughly to torque on a DD dyno. I think that with your mods, 337 wtq is a bit high on that dyno. More typical is right around 300. I'm also wondering if TTP rescaled all the axes on your maps because the stock Evo IX map scaling goes only to a load of 300.

 

You should also check if your injector size or Injector Voltag latency values were altered from stock for any reason.. If they were, and the load calc formula was not changed (its a fixed value in Evoscan) then that can explain your inaccurate value.

Now.. With aftermarket Intakes and Filters, there is the possibility you can get an improper reading due to turbulence in the MAF itself, sometimes they read higher (generally aftermarket intakes cause the MAF to read lower though)

 

His latency on stock injectors was not modified.

His load scaling is stock.

In my experience I have been seeing many loadcalcs that are off. My consensus is that the loadcalc is not accurate.

 

I'm actually inclined to agree with you if your not interpolating the battery voltage and latency accordingly..

I'm seeing the same thing (being about 10% off) from the ECULoad value before it clips..

 

ok finally found the problem being in the maf scaling, the one cruising log i have with the stock turbo show about 200htz at cruise under 120 load, the 37r is causing it to read 794htz at criuse causing my rich condition, i just have some re scaling to do to get it upa nd running again :-)

 

Heh thats part of the problem with using a stock MAF.. Even if the airflow is recirculated its still higher than normal, the blowthrough on my car helped alot in that, but its not "perfect"

 

Nice datawhoring research...