Newer versions work fine with your cable and yes the newer ecuflash is required.

 

I havent spent much time in this thread l8ly, but was in process of switching over all of my maps and noticed a couple things (Im sure it has been caught by now) but I havent found the fix, yet...

1. Wheres the rest of the MUT table. Looks like 1/2 of it is missing. I just copy/pasted what I could from mine. (the bottom half is missing) and all of the "FFFF"'s

2. NLTS rpm drop is missing somethin....


TIA

 

I agree, this may be the reason why it's not working for me right now. I had my values jacked real high in order for it to meet the criteria described. I'm going to lower my values and see if I can get NLTS to work.

If it's an issue where there is a def missing for the "new" base XML; can we post an updated XML to correct?

 

Sorry, I was referring to the original tephramod file. There are still some errors that need to be fixed in Phenem's/others XML. This is why I usually prefer to build my own XML (and you learn a bit in the process).

The item you are referring to is detailed in both the first post and the ECU Wiki: http://evoecu.logic.net/wiki/TephraMod#NLTS_Settings

Make sure you have the correct scaling and that you are not conflicting with a v5/v6 definition. I think we went over this a couple of times, but if you have conflicting definitions you should go back and start over since you do not know what you have changed...

 

I got NLTS working today, but I'm not sure which change fixed it. I went back to my original evo7base xml and also adjusted the values in Ecuflash to read "above" for the inputted values. Either way, that was the last outstanding thing I needed to resolve to be 100% happy

 

Ok so using the v7 can I just tick the 1byte load in evoscan?

 

That's my understanding. Check to be sure the factor is 1.2 in both FLASH and SCAN.

My question is: Why is LOAD CALCULATED not working in V7? It is simply an equation, but it only returns "0". I wanted to see a side-by-side of LOAD CALC and 1BYTE LOAD.

 

well, built a new .xml for the 88590715 rom, from stock, and took care of the NLTS issue, TY
but Im still getting the same MUT table posted ^^^... any ideas?
Edit, again: Just noticed that if I take the "Tephra v7" .xml out, and open up a NON tephra rom, the MUT table is fine...

Note: I have taken out the .xmls from both locations, both times now, before making any changes.

and for the NLTS speed threshold, under issue, I believe u can just click on edit/edit map def. and theres a note, just change it to OVER, no?

edit: and NLTS load threshold?

 

did u check your MUT table value for the evoscan request ID? Maybe when switching to V7 it changed?

 

Ok I know its 1.2 in flash I will check scan to be sure its the same thanks. Have you tried just logging load calc to see if it works by itself?

 

load calc requires IPW and maybe other stuff, just copy/paste the eval in here...

maybe you aren't logging the right stuff?

 

I think I did; I'll try it again. I thought perhaps I was logging too many different variables.

 

ok I thought maybe I needed to install a fresh version of ecuflash, and loaded up the v7 rom, and am still getting this half a$$ed MUT table I posted ^^^.

I havent loaded v5.10 .xml's. Just the stock(modified), and the v7. I havent created a desktop shortcut, so theres only 1 location, and the .xmls are switched, before loading roms... only playing w/ v7.

Now if I load a stock rom, the MUT table is fine. Before I un/re-installed, I loaded up v 5.1 and was fine. If I throw that v7 .xml in there it screws somethin... WTF?

tried swapping the def. for the MUT table w/ stock, compared the scalings etc, and seemed to match, but no go...

 

load up your stock rom and tell me what address the MUT_TABLE is registered as (right click- > edit map)

then do the same for the bogus rom and post your results here (with ROMID's)

 

address for both is 3ee84, w/ my own .xmls, romID's for v7 are88590715/88590015/evo9Base_20081101

and stock are 88590015/ evo9Base_20081101

I have tried using recompiles .xmls/rom and same...

Im not quire sure WTF is going on here, as I have run this rom before w/ out this issue, (using recompiles DL)