WORKS Brain Flash for '08 Lancer
This would be awsome, but there are some other things we need to go with it, like CAMS! It would be a lot of money to do a custom build and that might make it very, not worth it.
Don't do all this expecting massive numbers! Do this b/c you want an edge over a stock Lancer. Do it b/c its what u want!
Don't do all this expecting massive numbers! Do this b/c you want an edge over a stock Lancer. Do it b/c its what u want!
I wouldn't mind any company developing cams, pistons, head, ect.
Value is in the eye of the beholder. Some might think its worth it, others won't. Alot of people think buying a new Lancer is a waste when you can buy a used car thats much faster for $10k less.
But yeah back on topic, with the reflash, will it automatically disable the learning process the ECU has now? I would hate to get an aggressive tune, and let my my gf or mom or whoever drive it and have the car be slow again because the car thinks I want it to be slow.
Value is in the eye of the beholder. Some might think its worth it, others won't. Alot of people think buying a new Lancer is a waste when you can buy a used car thats much faster for $10k less.But yeah back on topic, with the reflash, will it automatically disable the learning process the ECU has now? I would hate to get an aggressive tune, and let my my gf or mom or whoever drive it and have the car be slow again because the car thinks I want it to be slow.
Got an email back from them today saying that if testing goes well they might be ready to start reflashing next week.
"We've been absolutely swamped with a recent move and new product development.
The new Lancer flash is EXTREMELY close. We may start flashing cars as soon as next week if testing goes well the rest of this week. We will certainly be posting to the forums once the flash is available.
Thank you,
WORKS Team"
"We've been absolutely swamped with a recent move and new product development.
The new Lancer flash is EXTREMELY close. We may start flashing cars as soon as next week if testing goes well the rest of this week. We will certainly be posting to the forums once the flash is available.
Thank you,
WORKS Team"
Like for instance?...
https://www.evolutionm.net/forums/sh...d.php?t=344537
https://www.evolutionm.net/forums/sh...d.php?t=344537
Greetings again! I'm happy to say the WORKS Lancer flashing program is a success, and as you've seen from Bill, the results so far have been good. I'd like to update you once again from the engineering side; I thought you guys might like seeing some of the in-house tools we've built and use for our flashes.

First and perhaps most importantly - I'm sure most of you have heard of the DTCs being thrown in the past - I'd like to show MapWORKS. MapWORKS is an interactive map flowchart engine and ECU simulator, which we designed to answer questions like, "under what conditions does the ECU use map X," "precisely how is the coolant temperature sensor used," and "how is DTC P1235 thrown?" MapWORKS interfaces with our sensor database that associates names (like "MAF air temperature sensor" or "drive timer") with maps, axes, and software conditionals, and uses its built-in ECU simulator to parse ROM images into flowcharts and to add important interaction/investigative tools for intuition and understanding.

DataWORKS is our logging and tracing program. It interfaces with our custom ECU tracing interface to display real-time traces over any maps currently opened. I'll have to get a screenshot of tracing in action, but for now imagine a stream of dots overlaid tracing a realtime RPM-load curve. The dot overlay, instead of cell highlighting, allows us to position traces between cells with the same accuracy as the ECU's own interpolation. Thanks to the ECU tracing interface, all sensors can be logged and traced in their raw form. This is crucial for tuning since values output over standard ISO/SAE requests are typically dumbed-down (i.e. load and boost) and not all sensors are available through standard requests.

Finally, FlashWORKS is what we upload and download ECUs with. I'm happy to say we've flashed many mail-ins and drive-ins with FlashWORKS and have even helped Mitsubishi Canada win their class in this year's Targa Newfoundland.
Looking to the future, we've successfully transitioned from developing in-house tools, and I'm excited about what we're going to be offering 1Q 2009; I think many of you will be too.
I made a similar post in the EVO X section here.

First and perhaps most importantly - I'm sure most of you have heard of the DTCs being thrown in the past - I'd like to show MapWORKS. MapWORKS is an interactive map flowchart engine and ECU simulator, which we designed to answer questions like, "under what conditions does the ECU use map X," "precisely how is the coolant temperature sensor used," and "how is DTC P1235 thrown?" MapWORKS interfaces with our sensor database that associates names (like "MAF air temperature sensor" or "drive timer") with maps, axes, and software conditionals, and uses its built-in ECU simulator to parse ROM images into flowcharts and to add important interaction/investigative tools for intuition and understanding.

DataWORKS is our logging and tracing program. It interfaces with our custom ECU tracing interface to display real-time traces over any maps currently opened. I'll have to get a screenshot of tracing in action, but for now imagine a stream of dots overlaid tracing a realtime RPM-load curve. The dot overlay, instead of cell highlighting, allows us to position traces between cells with the same accuracy as the ECU's own interpolation. Thanks to the ECU tracing interface, all sensors can be logged and traced in their raw form. This is crucial for tuning since values output over standard ISO/SAE requests are typically dumbed-down (i.e. load and boost) and not all sensors are available through standard requests.

Finally, FlashWORKS is what we upload and download ECUs with. I'm happy to say we've flashed many mail-ins and drive-ins with FlashWORKS and have even helped Mitsubishi Canada win their class in this year's Targa Newfoundland.
Looking to the future, we've successfully transitioned from developing in-house tools, and I'm excited about what we're going to be offering 1Q 2009; I think many of you will be too.
I made a similar post in the EVO X section here.



can we only post updates on this wtf!!!!!!!!!!!!!!!!!!!!!!!!!!!!!