New ECU+ feature: EVO ROM editing and map tracing
New ECU+ feature: EVO ROM editing and map tracing
Here's a new ECU+ feature of particular interest to EVO owners: EVO stock ECU ROM editing and map tracing. Let me know what you think.
Screenshots tell the story.
To setup the maps, you point the ECU+ software at a on-disk hex or bin file from your stock ECU. You'll still need to use something like EcuFlash to read the hex or bin file. (For now...
) Additionally, tell the software where your ROM definitions (metadata) are. The ECU+ can read unmodified EcuFlash XML ROM definitions.
Next, open up a capture and select "ECU Maps..." from the right-click menu. This brings up a tree view where you can pick the ECU maps you want to look at. You can pop as many up as you'd like, and can edit 1D maps in-line (see the rev limit entry). The viewer can filter by user level and a user-entered string. Folders spring open when they have stuff in 'em from a filtered view, so it's easy to find the map you're looking for.
To select a map, just click on it and it comes up on top of the other ECU+ graphs. You can have as many maps displayed as you'd like. The maps are "3D" colored to make it easy to build smooth maps, and of course the ECU+ software remembers what maps you have open as well as their window layout from one session to the next.
You can select a range of cells with the mouse, and then right-click to edit (or just type into the current cell). Lots of editing options are available, and will be familiar to EcuFlash users. You can also optionally edit the X and Y axis values. When you're done, the ECU+ will save the updated ROM file.
As you move the cursor around the graphs, the ECU+ software "traces" the maps by highlighting the current cell (in red) based on a variety of logged values. Tracing is real-time if you bring up a map while logging in your car.
A separate screen sets up the tracing parameters - you tell the ECU+ software the name of the X or Y axis on a given map, and how it should interpret that axis. The software can currently trace by RPM as well as computed load (using the same kind of load calculation as Mitsulogger, but using the higher resolution ECU+ logged values for injector pulse width), TPS voltage and temperature. I'd be willing to entertain adding other tracing types, which can be based on anything the ECU+ can log (which now, of course, includes all of the MUT-II values). Adding new tracing types is pretty easy at this point.
The whole ROM editing and map tracing thing still has a coupl'a minor bugs that I need to shake out, but in general it's "done" and works pretty darn well, IMHO.
Tom
Screenshots tell the story.
To setup the maps, you point the ECU+ software at a on-disk hex or bin file from your stock ECU. You'll still need to use something like EcuFlash to read the hex or bin file. (For now...
) Additionally, tell the software where your ROM definitions (metadata) are. The ECU+ can read unmodified EcuFlash XML ROM definitions.Next, open up a capture and select "ECU Maps..." from the right-click menu. This brings up a tree view where you can pick the ECU maps you want to look at. You can pop as many up as you'd like, and can edit 1D maps in-line (see the rev limit entry). The viewer can filter by user level and a user-entered string. Folders spring open when they have stuff in 'em from a filtered view, so it's easy to find the map you're looking for.
To select a map, just click on it and it comes up on top of the other ECU+ graphs. You can have as many maps displayed as you'd like. The maps are "3D" colored to make it easy to build smooth maps, and of course the ECU+ software remembers what maps you have open as well as their window layout from one session to the next.
You can select a range of cells with the mouse, and then right-click to edit (or just type into the current cell). Lots of editing options are available, and will be familiar to EcuFlash users. You can also optionally edit the X and Y axis values. When you're done, the ECU+ will save the updated ROM file.
As you move the cursor around the graphs, the ECU+ software "traces" the maps by highlighting the current cell (in red) based on a variety of logged values. Tracing is real-time if you bring up a map while logging in your car.
A separate screen sets up the tracing parameters - you tell the ECU+ software the name of the X or Y axis on a given map, and how it should interpret that axis. The software can currently trace by RPM as well as computed load (using the same kind of load calculation as Mitsulogger, but using the higher resolution ECU+ logged values for injector pulse width), TPS voltage and temperature. I'd be willing to entertain adding other tracing types, which can be based on anything the ECU+ can log (which now, of course, includes all of the MUT-II values). Adding new tracing types is pretty easy at this point.
The whole ROM editing and map tracing thing still has a coupl'a minor bugs that I need to shake out, but in general it's "done" and works pretty darn well, IMHO.
Tom
Trending Topics
ECU+ has a huge advantage over relying exclusively on the MUT values.. He is logging actual MAF frequency and RPM, so he can calculate load from the values and actually map trace very accurately, where my attempts with using the built-in MUT data haven't been quite as accurate.
Correct, I'm not saying that ECU+ is inferior in any way. I'm just having my friend make a quick and simple app that will allow users to just visually see where "about" in the map they are instead of having to cross reference every cell by hand.