123 Hp pm a car that makes 140 hp bone stock!!!!!!! Something is definitely wrong!!!! Man I hope it gets sorted out in your favor...../:/

 

Numbers don't matter because they will vary from one dyno to another. What you need to look at is differences before and after modifications are done. You'll see 123whp on one brand of dyno, and take that same car to a different one and get 164whp.

My intention here is to show gains or losses, not max hp numbers.

 

I would say it's pretty darn consistent. I don't remember how many times I flashed it back and forth and verified it on the dyno but the numbers were pretty easy to reproduce. Any computer guy can tell you that it doesn't matter - as long as the data is written correctly to the ECU and verified. The whole "lost forever" idea is not correct at all. The very first thing I did when the ECU arrived was read the map out and verify it against my master which it did verify 100%. I ran it on the dyno as well as some later rom versions. Same results.

In the meantime I've been working my butt off getting this software ready for release. This way you can happily flash your ECU with your performance map or back to stock as you wish.

-Michael

 

I have but one question , is the past reflash any better or worse than the new one since the software change???

 

^ what your actually wanting to ask is whether, now that a new reflash is available, hackish will update ecu's with the old(er) reflash or not. No?

 

Well depending on the results , yes and no I'd like an updated reflash if the quality has been enhanced but i'm just getting my car back from the bodyshop this week so I'm not really up for her being down again...

 

I don't mean any disrespect. We've been going back and forth with this for the past 5 months, so you have to understand my side.

I promptly paid $450 for your service. I provided info on it not working (twice), and even though I wasn't happy about it, I've complied to your terms. From what you and Brent have told me, what you're doing now with the reflash is different than how my reflash was done. If it's reflashing the same, no matter how many times you do it, why don't I still have my ecu? Will I be getting that software you're going to release along with my ecu? If I am, then I have nothing more to complain about and you will have met my satisfaction since the results will be based on how I tune, not how you sent it. If I'm not, then I will have to run the same tests, using the same car, and compare them to the previous reflash.

Another thing you've mentioned is me not having my car. Whether or not I sold my car is not an issue. I can't use the reflash, but I can't sell it either because of the results. So, it's been about 5 months since we started on this...

I hope the wait is well worth it...

-Carlos

 

I feel your pain man , I hope it works out for you soon...

 

Great news!!, I got the 2005 4G69 Lancer RalliArt MH8303F reflashing to work with OpenPort 2.0 and ECUFlash, here's a how to guide I wrote up... we just need some ecuflash xml files made up by someone."
http://www.evoscan.com/technical-veh...hi-lancer-4g69

 

The 2006 Mitsubishi Colt 1.5L Turbo 4G15 reflashing isn't working yet, but it should work ok soon. I'll update this page when it is: http://www.evoscan.com/technical-veh...-ralliart-colt

 

will this work with the 2006 ralliart?

 

I'm guessing you didn't read the webpage then.

 

We have done the first successfuly read and write to a 4G69 Lancer (Australian model) ecu. Works a treat.

I am working on the drive by wire maps now to remove the flat spots. Good times ahead, and all can be done on the ECU on the vehicle, no more sending ECU's out for reflashing.

 

using ecuflash x.x.3095 and openport2.0 I presume? did you have to feed the reflash pin into the back of the OBDII port? or does that model have a 12pin connector specifically for this? what year lancer did you reflash? did you change the fuel map and the checksum seemed ok, i.e the car started

 

ummmm...yeah all what he said