need help: new xml files for upcoming ECUFlash release
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Wierd. I didn't mean for it to be like that. It doesn't happen that way for me. If I select "beginner", I see what you posted, and if I select "Developer", then I get everything except the stuff I mentioned before.
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
I've got a evo7base.xml file partly done as part of some work I'm doing for an Evo 7 owner. I could post it up this weekend, but it would take too long to make all the individual ROM xml files, so none of the Evo 7/8 stuff would go to Colby until two ECUFlash versions later.
Ok that is working. What a pita to go through every one. Why is it like this?
its level not scaling
Last edited by Jorge T; May 31, 2008 at 09:46 AM.
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Yes, its too bad it looks like that because it is the most accurate scaling. When the throttle is closed, the TPS is at about 13% of its range. For some reason, Mitsu engineers ignore that.
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Hi MB,
Sorry but didn't have a chance to look at any Evo 7/8 stuff for this. Too busy with customer stuff and my own projects. I'll take a look soon.
Sorry but didn't have a chance to look at any Evo 7/8 stuff for this. Too busy with customer stuff and my own projects. I'll take a look soon.
Ok, no problem. Though I can't be 100% certain that there are no errors, they are better then those shipped with previous versions of ECUflash.
I've seen all sorts of maps defined but when you disassemble them you find no evidence of them doing what the definition describes. Take for example static rev limit, its in lots of deff files but the area shown has nothing to do with any rev limit.
Anyhow, if you like, please pass them on to Colby.
MB
I've seen all sorts of maps defined but when you disassemble them you find no evidence of them doing what the definition describes. Take for example static rev limit, its in lots of deff files but the area shown has nothing to do with any rev limit.
Anyhow, if you like, please pass them on to Colby.
MB
Finally got around to finishing 88580013 and 88580014.
One comment I have is "turbo boost jdm" perhaps should be called "Turbo Boost TwinBCS" as it's not specific to JDM and JDM ppl might get confusled
otherwise good work everyone
One comment I have is "turbo boost jdm" perhaps should be called "Turbo Boost TwinBCS" as it's not specific to JDM and JDM ppl might get confusled

otherwise good work everyone
ok ... so I starting working on the same project for evo7base + 94170015 before I knew about this thread.
so when I get home I'll read all through this. Hopefully some of the changes I have made won't clash too much with this. Especially with the user level ... I had an idea I'll float. If anyone is interested, I posted the start of my effort to the wiki thread at https://www.evolutionm.net/forums/sh...&postcount=127
I will say, I hope the structure of the base and rom file has been cleaned up. there is a lot of stuff that seems to be going into the rom file that only needs to be defined in the base file. keeping the structure definition in the base file and only the address definitions in the ROM file make for much cleaner definitions that are also easier to trouble shoot.
so when I get home I'll read all through this. Hopefully some of the changes I have made won't clash too much with this. Especially with the user level ... I had an idea I'll float. If anyone is interested, I posted the start of my effort to the wiki thread at https://www.evolutionm.net/forums/sh...&postcount=127
I will say, I hope the structure of the base and rom file has been cleaned up. there is a lot of stuff that seems to be going into the rom file that only needs to be defined in the base file. keeping the structure definition in the base file and only the address definitions in the ROM file make for much cleaner definitions that are also easier to trouble shoot.








