I'm just getting into logging and a bit confused on what load to actually log and how to get it to work with either LogWorks or Evoscan. It seems that ECU load is avaliable in stock form but I will need to modify the ROM in order to get 2-byte load and 1-byte load. What I would like to know is how can I get load numbers to correlate back to the load numbers in the fuel/timing maps so that I can be sure the log information is reflecting different load cells in the maps?

If anyone can point me in the right direction or have any advice on what I should do next that would great!

 

always good to start here
https://www.evolutionm.net/forums/ec...-tune-evo.html

a recent post Boosted Tuning made about different roms using different loads.
https://www.evolutionm.net/forums/ec...based-rom.html

evo ecu wiki
http://evoecu.logic.net/wiki/Main_Page

Here is where the info is for setting up your MUT table to log 2 byte, if your not running a V7 tephra rom, I dont think you can log 1 byte.
https://www.evolutionm.net/forums/ec...te-thread.html

I dont have the info on mut addresses for the various types of loads (baro and temp compensated) If I find it, I'll post it up.

 

Ok great so by the guide for 2byte when they mean MUT 03 - (some address) it means to edit row 0 column 3 correct? I just want to make sure this is the right convention they are using and the - are just filler spots.

 

So what am I logging when I use LoadCalc? Is this not good to use for tuning?

 

Yea I believe LoadCalc isnt as accurate I tihnk it might be based off of ECU load.

 

Were you able to get this to work? I tried editing my XML but when I open EcuFlash the 3-D Table shows up in blue and it wouldn't let me edit the values.

 

I think the new versions of ecuflash already have the MUT table defined in the xml. All you should need to do is edit it per your rom with the values in that thread. Yes, MUT03 is row 0 column 3.

You will also need to make sure your evoscan logging requests IDs match. Just make sure that the requestIDs in the data.xml for what you are logging matches the location that you put it in the mut table (02, 03, etc).

 

Mine didn't have the table defined but I figured out what I was doing wrong. I wasn't putting the "0x" before the numbers... I'm such a newb