It's a little odd to see you talking about your ECU being locked by Works and then in your sig you state you are ECUFlash self tuned!

 

Deatchwerks 800's with 0 fuel trims!!
been like this since a week after Mitsu gave me the car!

 

Yes mine is self tuned. I didn't say MY personal ECU is Works locked. I was trying to connect to another ECU that is Works locked... What did I lie about now? I said I have a ECU in my possession that is...not my personal car is. I will never run anything Works on my car...

 

I'm not pointing fingers, just stating what appeared to be the obvious!

 

Ya, I don't feel like experimenting on a ECU that is not mine. I already feel like I'm taking a risk flashing my ECU after a few people bricked their ECU, and I'm learning tips, tricks and the whole self tuning business. So when I encountered an ECU with a Works flash I just wanted to know how ECUFlash would react to a write command. So there it all is. 2 separate ECU's and 2 separate cars....so anything else? RGuy? I don't like being accused of not telling the whole story....

 

I just downloaded the new version of the software. Does it appear to anyone else that you can only use 1 cable per car now?

 

I looked. Didn't find any. But I have one now.

 

I'm a little confused about what you are saying. Do you have mutiple cables? If so, maybe only the first one got the firmware update. You'll need to update the other firmware in order for it to work. An easy way to do this would be to uninstall ECUFlash > Reinstall > hook up the none updated cable/adapter to your car and PC > start ECU Flash > read ROM > and the update should begin.

 

Thanks for the rom Keepster13.

 

No worries about bricked ECUs. The long wait for a public release was so that this would be a non-issue. This version of ECUFlash has a recovery mode.

 

New EcuFlash works great on the 2009 Lancer Ralliart as well:

https://www.evolutionm.net/forums/20...-ecuflash.html

 

anybody found anymore since ecuflash is public?

Also razorlab how are the how-to's coming along

 

ya a new how to would be sick. I want to learn how to tune but have not found any more great info besides the how to we currently have (which is great).

 

Since this is the definitive thread on the X I thought I should post some questions regarding the boost tables:

1. There are three boost target engine load tables, one of them for low gear range, but the numbers in the cells are the same as the high gear range. Shouldn't the numbers be different?

2. The reactive solenoid base WGDC has two high gear tables and one low gear, but all three have the same numbers in the cells. Should they be different?

3. The most important thing that I do not get is the passive base WGDC map. What does that do? The other tables I understand since I have seen similar tables on the Evo 8/9. These tables confuse me. Anyone understand what they do?

 

I helped flush out those tables, so I can take a shot at it.

For questions 1 & 2, the answer is that WYSIWYG. Mitsubishi was apparently not interested in using this feature in the Evo 10 GSRs. They did this by making the low/high gear boost maps the same. This is true also for the Evo 8/9. Low/high gear range boost maps are active in those ROMs as well, but Mitsu makes them all the same because they apparently weren't interested in using that feature even though it exists. The only Evo 10 that makes use of the low/high gear range on the SST cars, so those cars are the only ones with different low/high gear boost maps.

Question 3: There are two BCS's in the Evo 10. They work in parallel to relieve boost pressure from the WGA. One solenoid is passive, i.e, the ECU does not attempt to adjust its duty cycle based on BDEL. So the only map that matters for that solenoid is the base WGDC map. The other solenoid is reactive, which means that the ECU will adjust the duty cycle in an effort to reach the BDEL. If the aim is more boost, cranking up the passive solenoid BWGDC would be one of several things I would do.