RomRaider

Yes another ROM editor. Why? RomRaiders GUI wasn't what I wanted structurally or programmatically for my future goals. Altering RomRaider would have been equivalent to starting a new project anyways.

FWIW, no logger in my code, no competition yet

But if you want to try a fast, lower memory footprint ROM editor, give it a shot.

http://simpletune.org/home

Off to put UTEC support back in. Maybe sleep then UTEC

-Eric-

PS. I'm NOT going to start another forum/community. Great stuff exists here.

------------------------------------

Update! Added ROM Comparison Tool. For those of you that manage many versions of ROMs, this can help verify differences. Details here:
http://www.iwsti.com/forums/ecu-tuning- ... ost2194955

Looks good Eric. I'll have to compare its speed and memory usage to something I have in the works

Crap, nerd wars.

Hooray for tabbed UI!

[Edit: I later realized that there isn't one tab per ROM. Not so much glee, then.]

How do I make map scaling happen? I hit the button, entered a larger value for the rightmost column, nothing happened.
Tried entering a value and hitting the scaling button, still no luck.
Tried highlighting the whole axis, hitting the button, no luck.
Can you walk me through it?

Thanks!

-Open table
-Hit scale button, it should turn RED
-Double click axis cell, enter in new value, hit enter

Note that the fine and coarse buttons dont cause the table cells to change. Not a bug, just a limitation

Let me know if this helps!

When I do that, the only value that changes is the one cell that I typed the new value into.
My goal here was to scale this out to 3.2 g/rev instead of the original 2.5:



Doesn't really matter in this case due to the shape of this particular map, but the same thing happens (or rather, doesn't happen) with timing maps.

Well, all the cells below that axis value were changed. The logic is such that if you're extending the load beyond the current max, then use the last max value. Much like how the ECU deals with loads beyond table limits.

Open up a timing map and change a 1.6 to a 1.65 using the scaling and the values will change as there is data for the program to use below and above that value to interpolate a 1.65 load axis value.

Hope that helps, if not let me know.

I see. I thought it was going to rescale the table, not just the column. Please consider that for the next release.

I'll think about it, the backend code is all there. You can get the same effect playing with the smoothing and scaling functionality.

Looks nice. Is is possible to make the table x/y axis display configurable? For example I'm used to tuning a system with the load on the Y axis and RPM on X. It's not a big deal to get used to it but it does make it a little tough when jumping from system to system.

Thats a good idea. Though, since I'm the only hacking at this and free time is short, I'll have to file that with all the other nice to haves I wish I had time for

Thanks for the input!

Also, I'll be releasing a new version soon that compares ROMs, finds similar tables with different tables and offers to copy changes over. My development is driven by what I'm too lazy to do by hand.

Speaking of axes, I'd love to be able to view tables with 0/0 in the lower left.

Having the origin in the upper-left drives me nuts.

Oh, that'd be great.
Donations will be given

Done.

http://www.iwsti.com/forums/ecu-tuning- ... ost2194955