WORKS ECU flash development - behind the scenes
Thread Starter
Account Disabled
Joined: Apr 2008
Posts: 10
Likes: 0
From: CA Bay Area
WORKS ECU flash development - behind the scenes
I posted a similar thread not long ago in the Evo ECU section, but when I went to find it, it had been moved to vendor announcements. I'm posting a copy here.
-------------
It's been a while since I updated you guys from the trenches of the WORKS Lancer/EVO X flashing program. I'm usually busy behind the scenes and not rearing my ugly head in public, but 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. We use the tools I've introduced here, among others, in conjunction with dyno, street, and track time to create our brain flashes.
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.
-------------
It's been a while since I updated you guys from the trenches of the WORKS Lancer/EVO X flashing program. I'm usually busy behind the scenes and not rearing my ugly head in public, but 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. We use the tools I've introduced here, among others, in conjunction with dyno, street, and track time to create our brain flashes.
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.
