burgers22

Sounds like you are adding the MUT table to the very top of the xml, try adding it between some existing maps, rather than at the top or the bottom.

MB

ITP

Ok. Looked through to make sure I wasn't missing any coding. I also took a stock rom, copied to notepad, did not mod it. And saved it. Still wouldn't open. Grr! So why would both computers be having a an issue after a simple copy/paste/save as xml? Annoying!

ITP

I will try. Thanks.

Until I get this issue worked, would someone be kind enough to add MUT table to 96420007 and post it. I can do the rest from there.

I think I have something funky going on here. As I have had no issues in the past with this. I did just update ALL my computers recently. Ugh! Hope thats not it.

ITP

Here is a stock xml for 96420007.

ITP

Fixed the issue. While in Notepad,I removed all the minus signs form the left side of the page. Seems silly but worked.

ITP

So, I got the MUT table up and changed the hex for 2byte load,rpm and airflow to the ones for 96420008. Doesn't log correctly. Load is stepped. not flowing. RPM read about 22000 all the time. And airflow is backwards. I am using Evoscan 2.2. Maybe I need to change something in the xml for evoscan. But the last car I used 2byte on, it worked fine. Any thought?

PeteyTurbo

iTrader: (9)

Anyone have 2byte info for 96420011, are any other roms compatible with this 04 ecu??

RazorLab

iTrader: (8)

Did you try the 96420008 2bytes?

PeteyTurbo

iTrader: (9)

No I didn't, I thought the version 15 rom would work but the car did not want to start with it so I ended up building off of the stock rom using load calc. ect.
Have you had any luck with the 08 patches on this rom?

AlwaysinBoost

iTrader: (17)

I've got a tephra v5.xx (whatever the most recent version is) patched ROM for 964200011

PeteyTurbo

iTrader: (9)

Does it have 2 byte patched for airflow,rpm, and load?

~BoOsTeR~

iTrader: (24)

I'm working with an 88590015 and a 88590013.

I had to change the security permissions on each ROM just to save changes to the xml - figured that out. I changed the metadata directory in EcuFlash to the exact address because it was referencing a different location?!? wth?

Both ROM ID's inheret (include,) an "Evo9 base" xml that includes all the scalings. I cannot get the tables to appear unless I include them in the base file, which then, of course, doesn't have the right table address for each individual ROM ID. The exact code looks like this: <include>evo9base</include>

Can I add the "Evo 9 base" scalings to the '15 or '13 xml's individually and delete the "include" portion of the code and save them as new '15's or 13's and then add the MUT mod with the appropriate table address per each rom, save '13, (since there's no known addy yet..)? Why won't it work on the children files (the actual ROM ID's) as per the instructions? I'm frustrated.

~BoOsTeR~

iTrader: (24)

If someone can chime in, this would really help!

I can't get any of the children to display the tables. EcuFlash isn't reading the tables, according to the log window. No matter what, for example it says: 88590015 - 73 tables read, 75 for Evo9base. I add the tables to the child '15 - same thing.

EcuFlash 1.34, btw.

Should I completely uninstall it and then reinstall?

~BoOsTeR~

iTrader: (24)

Well, uninstall and reinstall didn't work.

Will upgrading to 1.40 make all of the MUT3d2byte unecessary? Does it have all the encoding already and all I have to do is add the addresses?

mrfred

iTrader: (50)

Sounds like there are duplicate xml files. The one you are modifying is not the one being used by ECUFlash. Did you by chance rename some of the original xml files and not move them out of the "rommetadata" folder? If yes, then ECUFlash will still read these tables even if the file name has been changed. ECUFlash uses the name in the first line of the file for differentiating xml files.