kdouthit83

I have the same values. I am using evoscan2.2 and I haven't uploaded the mod yet until I'm sure what I am looking at.

Anyone else able to verify the new (differnet) functions are correct with EV2.2 ?

Jack_of_Trades

iTrader: (17)

1000*x/256 is the correct formula for 2byte RPM. If your values are all out of whack, you aren't logging the correct address somehow. All of your other formulas are correct.

GTijoejoe

iTrader: (25)

That was my first thought, I did try that formula as well. Perhaps we can sort this out. My rom is 88590013... I did try the -0015 address like I stated before for load and airflow.

This is my MUT table, is this the correct association to the instructions?

Jack_of_Trades

iTrader: (17)

Yeah you did that perfectly. If you are getting false readings, the 013 ROM must have different addresses than the 015 ROM uses. You'll have to nag one of the ROM Disassembly guru's on here to help find the correct address' for you. If you do find out, post up the correct address' on here and I'll update them for anyone else in the future.

GTijoejoe

iTrader: (25)

Haha, that is what I was looking for you to tell me. I will try and find someone to help me sort it out. I will not continue tuning until I can datalog load more accurately.

Thanks for your help

tephra

iTrader: (6)

0xFFFF6B42 is correct for 88590013 for 2byte load

RazorLab

iTrader: (8)

Why not just swap to 015 rom?

tephra

iTrader: (6)

Also your MUT_TABLE definition is wrong, go check it - it should be 0x3ee64, not 3ee84

mx5tc

iTrader: (5)

Hmm, does anyone know if the 014 (88590014 ROM) uses the same MUT table start address location and 2 byte load values as the 013??? I've got the 014 and want to start logging the 2 byte load, trying to determine the right MUT/2 byte addresses before I make the .xml mods to the def file.

Thanks in advance,

Mitch

tephra

iTrader: (6)

upgrade to 15

mx5tc

iTrader: (5)

Tephra,

I'm only about 1 week into ECUFlash, so I'm not completely sure how I "upgrade" to the 015 ROM.

Is it as simple as:
1. Getting a copy of a stock 015 ROM
2. Updating the stock 015 ROM file with the 2 simple changes I've made to my 014 ROM
3. Flashing the updated 015 ROM into my ECU????

Any downsides to migrating from the 014 to the 015??

Anyone have a stock 015 ROM they can send me???

Thanks in advance,

Mitch

tephra

iTrader: (6)

yup basically.

what 2 simple changes have you made?

just go ahead and us my V5 88590015 if you want...

Jack_of_Trades

iTrader: (17)

Be sure you copy over your immobilizer and init code from your original rom. Thats the biggest rookie mistake, then you can't start your car and it can be a headache.

mx5tc

iTrader: (5)

All I've done on my 014 ROM is bump the idle timing from 5* to 7* (all 6 tables) and put in hybrid MIVEC map...should only take me a few minutes to cut and paste onto on 015 ROM.

Just have to remember to change the immobilizer code too before I flash it!

oldevodude

iTrader: (3)

Call me lame but i can't get the mut table to show up. I copied the xml data in and put in the address for my rom evo9 15 and i get an error right on the first line of code when i launch ecuflash. It references a column aside from the row that isn't even there. anyone have a working 15 xml for me to test? pm me with addy or i will pm back mine thanks. this is frustrating.

does the downloaded text file with XML data need any editing aside from the address for your particular rom?

Does it matter if you have 1D for RPM already defined?

this is something simple i know it


I tried on different computers and everything