Tephra himself is working on it. I have the same problem as you.

https://www.evolutionm.net/forums/ec...-issues-3.html

 

Which is your problem, the gear based boost, or the boost error not reading even when changing the hex addresses?

THanks again for the heads up.

 

I have both problems (gear is stuck at 1, and boost error is not reading right), and the hex address fix is the first attempt for solving the gear-based-boost-control function. I haven't had a chance to test the hex fix solution yet. I will do it tonight see if it solves the problem. You can try it yourself too.

 

Hi
First post here. I have been reading a lot though.
I have a JDM EVO VIII. I have crossed over to V7 96530706 in the last few days and before that 9626009 tephra v5
What I have understood reading my logs through Evoscan (logging 1 byte load) is that the ECU sees a lower load than the Evoscan sees, by a factor of 1.1 approx. I say that because I log advance and the ign advance in my map shows different values than the ones that I get.
For instance in 240 load and 4000 rpm I should have an advance of 2 degrees according to my map, but I log 6 degrees (which corresponds to a load of 220 and 4000 rpm)
I have started looking at older logs (96260009 with 2 byte load) and I see the same there.
What could be the problem and how can I fix it?
Thx in advance, keep up the good work

 

Did you setup your RPM/Speed to define all your gear crossover points?

Check out the wiki for help: http://evoecu.logic.net/wiki/Main_Page

 

I have an 04 VIII and the tables set similiar to

 

Any ideas?
Is there a chance my MAF readings are off? Wouldn't that affect my 1byte load as well?

 

So I have a problem; I successfully converted my 96940011 rom to a phenem V7 96530706 rom and got the car running well with the new rom. I did this last night but when I tried to open my saved V7 rom today, none of the V7 tables appear, only the tables I had on my stock 96940011. And when I open the tables all the axis and values are gibberish. I read the image off the ecu and got the same result. Also when I look under the ROM Id, it still says 96940011 after internal ID. What am I missing. Also car still runs with all the tephra options I had setup yesturday.

 

Sounds like when you were copying over all the tables you copied over the ROM ID to the v7 ROM. Change that back to 96530706 and save, then re-open and you should see all your data again.

P.S. - don't ever change the ROM ID unless we tell you to....

 

That fixxed it, Thank you very much

 

Bump for an answer
I know I am a newbie. I would really appreciate some ideas.
Thx

 

Theo, this is most likely due to the interpolation of surrounding cells ...

 

Thx Freddie, but I don't think so.
The map is pretty smooth and I see large differences in logging.
To test this I flashed the original rom back on the car (93660005) and logged today. I saw that that happened even with the original rom. I get more advance than what I have in the maps for the high cells (>200 load ) and less timing than the map for the low cells (<100 load).
How does the ECU decide what load to take in account in order to decide the timing? (I logged 1 byte load, load calculated, 2byte load and the result was the same). Because my timing is unpredictable.I end up with the timing for 230 load when in fact the load is 260.
Is there an error somewhere? I think I have tuned around it but something is not right I think

 

I think you can have issues with what is logged in load depending on the version of ecuflash and evoscan you are using. Do you have a recent evoscan and ecuflash? say 2.6 and 1.4xxxx

also, sorry for the thought, make sure its 1byte you are logging and not 1byte4 or whatever it is.

 

Also make sure that your 1byteload factor matches in ECUflash and Evoscan...