Does anyone know how the 'loadcalc' value in EvoScan 2.2 is related to the load values that the ECU is using for fuel and timing?

For instance a log value 4600 of 'loadcalc' would correspond to what load value in the fuel map?

 

Load is the horizontal axis (X) on your timing and fuel maps. As to why your load calc is a 4 digit number, I'm not sure. something is wrong with your definition file or the function in evoscan. The IX's OEM range is 0-300, scaled in kPa absolute manifold pressure, the OEM VIII maps are only scaled to 265.

 

I know what the load scale is on the fuel maps. What is confusing is which parameter in ES 2.2 corresponds to the load used by the ECU.

I was not able to find something that logged a value that corresponded to the fuel or spark maps. Maybe it's a problem with this new fangled version of EvoScan.

 

well yeah, I don't see 2.2 out yet, are you beta?

 

Bruce I downloaded it last night. It was the only option there was. I'm trying to get away from using UTEC for any tuning at all.

EvoScan 2.2 is what it says in the Start Menu. The creation date on the Application is 3/14/08. I punched the Buy Now button here: http://www.limitless.co.nz/Evoscan/

I can't get it to log any parameter that matched the the fuel or spark load value.

Load Calc
gRev
LbsMin
AirFlow

Each of those headings relate pretty closely to load, but none of them seem to have quite the right conversion factor to get to a load value in a map.

After reading about the 2byte load values I tried the logging 'LoadMut2byte' but it just reports a constant 2741.875.

I'm going to get an older copy of the software and try to a figure out if the math is just off or what. I'm going to read that 2.1 thread again too.

Trent

 

Your ECU ROM file also needs to be changed using ECUFlash. Did you do that?

 

I have not seen any versions of evoscan other than 2.2. Do earlier versions have "load calculated"? if so can someone post a definition?
edit: yes and no need

I did find that the sample logs supplied with the Evoscan 2.2 download seem to show load calculated to be correct, and afr wrong, or atleast I think it is.
When I open one of my logs I see AFR map shows between 14.7 and 9 or so on a particular log and like mentioned earlier the load calculated is upto like 4600. Sample logs show load around 255 and AFR map 178. it must be 2bytemods. If some one could explain the differnce I am seeing I would appreciate it. I hope I am not being to much of a newbie here.

 

I'm going to return to this today and try to fix it. I'll report what I find out. I hope I'm not reinventing the wheel.

 

OK altering the XML definition file with the bit of code found in the Official 2Byte Thread + the ECU ID#, then opening in EcuFlash and altering the MUT0-5 bytes in hex.

Official 2 Byte Thread is here:
https://www.evolutionm.net/forums/sh...d.php?t=327185

Then EvoScan 2.2 loaded @2Byte Load and RPM just fine.