How does one log load accurately?
Mar 31, 2009, 05:22 PM
#1
How does one log load accurately?
Forgive me if this has already been asked but I searched and searched and searched and didn't pull up anything.
What is the most accurate way to log load using Evoscan? How do I do it?
Keep in mind that I would like to learn how to log load in order to know which map point to modify in Ecuflash.
Whoever answers this question for me accurately, will be compensated to the tune of 20 bucks over paypal.
Thank you for your time,
Rob@modularturbo.com
What is the most accurate way to log load using Evoscan? How do I do it?
Keep in mind that I would like to learn how to log load in order to know which map point to modify in Ecuflash.
Whoever answers this question for me accurately, will be compensated to the tune of 20 bucks over paypal.
Thank you for your time,
Rob@modularturbo.com
Mar 31, 2009, 05:55 PM
#2
Rob,
There are at least 3 ways to log load:
1) calculated load, obviously the quickest, but not the most accurate. As the name suggests its "calculated" from other parameters, IPW, injectorscaling, rpm etc etc
2) 2byte load, requires setting up your MUT table with the appropriate memory locations - Look for the "2byte" thread. This will give you a better load, although not 100% (as different routines use different compensated (temp/baro) loads)... Also 2byte load has a problem is High/Low byte mismatch, which results in weird peaks/throughs in the logs.
3) 1byte load, in TephraMod V5.10. Same deal as #2 but doesn't have the problem of high/low byte mismatch.. Also its only 1 byte so its twice as fast as 2byte load.
HTH's
D.
There are at least 3 ways to log load:
1) calculated load, obviously the quickest, but not the most accurate. As the name suggests its "calculated" from other parameters, IPW, injectorscaling, rpm etc etc
2) 2byte load, requires setting up your MUT table with the appropriate memory locations - Look for the "2byte" thread. This will give you a better load, although not 100% (as different routines use different compensated (temp/baro) loads)... Also 2byte load has a problem is High/Low byte mismatch, which results in weird peaks/throughs in the logs.
3) 1byte load, in TephraMod V5.10. Same deal as #2 but doesn't have the problem of high/low byte mismatch.. Also its only 1 byte so its twice as fast as 2byte load.
HTH's
D.
Mar 31, 2009, 08:14 PM
#4
search for the 2byte thread... Jack_of_trades is the author.
make sure you have the MUT_TABLE defined in your ecuflash - if not define it (2byte thread should have help there)
change the MUT entries for 00 and 01 (or 02 and 03 - whatever evoscan is using) to the 2byte load from the afore mentioned thread
flash+log..
make sure you have the MUT_TABLE defined in your ecuflash - if not define it (2byte thread should have help there)
change the MUT entries for 00 and 01 (or 02 and 03 - whatever evoscan is using) to the 2byte load from the afore mentioned thread
flash+log..
