could you walk us through this please

 

open your 3d mut table
should have a bunch of FFFF's followed by 4 hex

find MUT41 (assuming you are happy to use MUT41)
so row 4, column 1 - hopefully your 3d mut table is labelled properly

now don't change the FFFF bit, change the hex number after it to 0x840B.

Now log MUT41 (by using the xml above) and that should give you your 2byte load, but as 1byte.

The default factor is 1.2, but for smoggy since he hits high loads he will need 1.5x.

Why all the bother, logging 2bytes takes more resources and also produces some spikeyness when the bytes get misaligned. 2byte->1byte just divides the 2byte load into 1 byte, and then evoscan multiplies it back out... thus you only need to log 1byte.

Only side affect is you loose resolution with bigger factors...

 

thanks tephra, that what I needed ( I am just getting back into this and completely spaced the mut tables)

 

hopefully u will see what I mean once you get your 3d mut table up n running

no worries!

 

Log worked great. 1 byte load looks awesome and matches 2byte. Will post log asap.

 

cool - put up some graphs so ppl can see

now u dont need to log 2byte, which saves you a bit in logging

 

Doin' it right now. Unfortunately, I can't post timing and AFR, but I'd be happy to answer any questions about timing or afrs. Also, I definitely need to log more parameters, but this is a start....

 

Here are a couple of highlights from my drive to work this morning. Sorry it is so hard to read. If anyone has ideas on how to better post logs, let me know.

Edited: See grahps below....

 

graph it in excel hehe

 

I'm happy to send the whole log to you or the other gurus if you want to work with it and post it up here.

 

I don't see a 3-D MUT table after loading v5.8.

Regarding the change to 1-byte load, you allude to changing this scaling factor (tagged as "EVAL=X.XXX" in Evoscan) to match the ECUFlash XML, but this seems cryptic and unclear. Are you saying there needs to be a change in the ECUFlash XML code as well as the EVOScan datafile? If so, what and where?

I changed my EVAL factor in EVOScan to "1.5*x" to reflect the extent of my load table (375 max) as per your scaling factor instructions, and I'm getting nothing usable.

 

Smog,

I thought you weren't going to post AFR and timing?

12.4 AFR on 100 with a 35R, you are a brave man.

Is this the AFR it was tuned on before you swapped roms? Did you turn off your lean spool on the new rom?

 

Bryan,
LOL. I didn't even notice that AFR and timing were posted. I did the "hide" function on Excel but when I tranferred the Excel with copy and past, it must have unhid it automatically. Thanks for pointing that out. I've made so many changes to the map at this point that I don't really think I'm violating any policy though. I've made several adjustments to the fuel tables and consistently get no knock or 1 count with this tune and have logged it over 25 times in the last couple of weeks. Anyway, I'm posting up some 2byteairflow and 1byte load graphs in a minute. Could you comment?

 

Here is an airflow and 1byte load graph from my way to work this morning:

 

379 load with 19psi? Does not compute

Rest of the stuff looks pretty close to what I have seen out of a 2.3L GT35R.

This isn't the tune that made 584whp is it?