Thanks for sharing the info.

I will try moving my boost source to the BOV line to see if I am able to smooth out some of the spike and achieve a more stable profile. I'll log it to see if that made any difference in the 2 byte load.

 

I have logged a run: on my 88840016 the difference between LoadCalc and LoadMUT2Byte is always under 5%.

 

peaking at 297 (27 psi peak boost on my VEI digital gauges)
probably even more now since I have fitted my 3" Miltek exhaust

 

i pulled some more logs i will post later.

mine is way over 5% al/lupo

 

+1. I think the difference between can possibly be affected by other factors while logging. I have always logged both of them and the difference can be as much as 10% (keep in mind I have a pretty much stock car with no injectors or intake to throw off the MAF and cause loadcalc to be even more off).

 

Stupid question but your not logging on an uphill are you? Had to ask.

 

nope but what difference should it make buddy!!
Even if i was going up hill my load calc is 270 and 2byte will be just over the 300.

don't know what there is such a difference.
at first i thought it was because i put in an intake but when i logged the normal load cal the numbers were the same.

the only thing that did change was that i was able to hold more boost up top and i am sure that is due to the apexi intake

 

Maybe Evoscan scaling issue...

 

The equation for LOADCALC is incomplete. Its juts a best guess that can be made by using known values such as IPW, injector size and scaling. The ECU actually uses a few more variables in calculating load such as the actual MAF frequency. If you have an aftermarket intake, that will affect the MAF frequency enough that it could cause an increase in what the ECU calculates as load. 2-byte load is the load value the ECU is actually using in table lookups, not LOADCALC.

I have actually logged 2-byte load as high as 400-something when messing around with different MAF inputs.

 

Thanks for this info
i am actually gonna do some testing if i get around to it.
i will put stock airbox in place and log the 2 byte again and see it hits over 300.
IF this is true how do you tune a MAP that does not have any load cells higher than 300.
Sure you can add more but if you say you hit 400 have you rescaled your ECUFLASH tables.

 

Estimating load from rpm and timing like Mellon said is a good way to check it.

If you were in 3rd gear for the log that you posted, then I'm estimating around 260 whp/tq which wouldn't suggest a load of 320.

Can you post your EvoScan "Data.xml" file?

 

sure ........

i will post it from my lappy when i get home.
I didn't hit 300 with normal Load calc , but with 2 byte it went over 300.

are you after the data.xml file in evoscan ?

thanks for all the help mrfred

 

Yep. Glad to be of help.

 

here is the log mr fred


and i have attached the EVOSCAN xml

i did notice even when i logged with my other laptop it was the same.

 

something wrong with your battery/charging system?

voltage looks a little low.