I've done a lot of reading. first time logging. Everyone seems to have their own opinion on logging load. I have the latest EcuFlash and EvoScan.

Some use LoadCalc, some use 2byte Load and some 1byte load. A description in EvoScan says to log 1byte Load if am using tephra moded rom which I do. (v5.10 90550001). 1byte load reads about 35 load on idle 272cams at 1k rpm.

Just to confirm what am going to log, If there's anything am missing out, advice would be most appreciated. Thankyou.

Load?
RPM
Timing
knock sum
AFR
Octane
MAP sensor (psi omni 4bar)
IPW
Injector duty
coolant temp
Air temp

I know it's quite alot. First time logging to see how the car is doing. I know when logging for tuning purpose theres only few things need to log realy.


Posted from Evolutionm.net App for Android

 

1 byte load for Tephra roms.

 

in my case 1 byte wasn't accurate, now I log 2 byte and all is good (9653 v7 rom)

 

Did you have the multiplier configured the same in your logger as you did in your rom? ie tephra load mod x 1.3 in the rom, and 1.3 multiplier in ecuflash?

 

yes, I had same 2byte to 1byte factors both in my rom and evoscan and my logged timing never matched to my map timing (timing trims were zeroed out) due to wrong load I think
so I logged 2 byte, (it registered less load than 1byte) and everything is correct when comparing to map

 

2byte is more accurate on 90550001

 

I can't see Load 2Byte. Only thing close to that I can see is,
'Load MUT 2Byte Mod' in EvoScan.

Do I need to select anything on the rom. 2byte to 1byte load factor, shall I leave that deselected?

 

In EvoScan 2.9 this is what I see.'Load 1Byte'*Request: 41Function: 1.2*xUnit: LoadNotes: Load 1 Byte (Load1B) is only available if you are running a Tephra Modified ecu rom. Check the tuning guide on*www.evoscan.com*on how to do this.This Load value is calculated by the ecu internally, and is based on AirFlow (MAF) Sensor and Crankshaft Position Sensor (RPM), i.e. more air flow and less crankshaft speed will give you higher Load values. i.e. going up a steep hill with your foot to the floor. Load is effectively similiar to this calculationcurrent airflow / peak airflow) * (Baro And AirTemp Compensation) * 100%.Load1B doesnt use the injector scaling value on the main evoscan screen, this value is already available internally to the ecu code.I can't see Load 2Byte. Only thing close to that I can see is,*'Load MUT 2Byte Mod'Request: 00Function: 0.3125*xUnits: LoadNotes: Depreciated now, use Load1Byte instead, it has faster updates.** Load MUT 2Byte will only work if you have reflashed tephra mod rom to your Evo ECU via EcuFlash and an EvoScan Openport 1.3U USB Cable.

 

Load MUT 2Byte Mod is 2Byte load

 

Everything you need for 2 byte is here:

https://www.evolutionm.net/forums/ec...te-thread.html

FYI I'm not running a Tephra rom and I'm using OpenPort 2.0 cable and it's logging fine.

 

Am using 1.3u cable. I know most people seems to use the tephra 90550001 rom on evo 7s. What other roms is good, just to log and map a car on the s205 turbo that might be hitting 340 load on my evo 7 EDM. Not to bothered with tephra mods or so many variables or options.

 

90550001 is the best evo7 rom 340 load or higher isnt an issue