RomRaider

Is it possible to remove the AT portion of my 16bit rom to gain better resolution in my wgdc maps? What is the limitation on creating more resolution? Is this available space?

I need better resolution to get rid of some boost fluctuation...

Sure it's possible if you are familiar with how these tables are referenced in the ROM, although if you need more resolution in a particular area you can achieve this by rescaling the RPM axis, which on the factory tune, usually has too much resolution at low RPM anyway.

Well, for instance: I'm getting knock at 2350 rpms under light load, if I decrease the row above or below, my knock travels in the direction that I change it (have tried decreasing both above and below and increasing, Knock goes away in that exact place, but occurs in the direction that I reduced or increased it.)

And I am getting boost fluctuation at 4200-4300 rpms, boost drops, same as timing, if I change it in the lower rpms, boost jumps way high and still falls off. If I increase it in the higher rpms, it spikes there. I know a mbc would correct this, but I would rather try tuning it out.

Thats why if I could remove all AT maps to increase available storage and increase the rows/column that are available in timing and wgdc/boost it would be sweet.

Last question, would a JDM STI ECU, with avcs disabled control my 205? I have read on here that some ecu's come with boost/wgdc by gear. Is it possible to use a jdm ecu to control these features? Am I asking for too much!? haha

I don't understand hex or how these roms are layed out, I'd love to but do not have the time and being an apprentice union electrician, I am already having crazyness pounded into my head on a bi-daily basis...

The point is, that it would not be a simple prospect especially if you don't know what you are doing. Target boost would be simplier for the 16-bit ECU as the MT/AT maps are consecutive but you still need to learn how the ECU references the maps (via the map type byte and then changing the offset to reflect the new table), how the row/col count is stored relative to the data (and changing the counts to reflect the new table size), and how the data is stored (so you could add additional values for row/col/data). All this within the space allocated by the target boost mt/at tables. Then you would need to modify the defs to work with your new table. Considering you are not willing to spend time to learn this, I would find an alternative solution as I doubt additional resolution is going to necessary solve your issue anyway. And doing this for base timing or advance tables would be even for complicated considering the limited unused ROM space for the 16-bit ECU.

well its not exactly my unwillingness to learn, I'd love more than anything to learn. I just don't understand how to read hex- How data is referenced. The boost issue would be easily solved, I do believe, by having higher resolution (IE more rows). Since for instance if I needed 64% wgdc at 4000 rpms, but need 65% at 4250 and back down to 63% at 4500, more resolution would fix this problem, overshooting is not the problem. I have played with the TD maps so much its not funny. I tried overshooting my target value and keeping target in check with TD, which is ok, but sporadically overshoots target by a significant amount.


I was just curious if it was possible to remove some of the unused stored rom, to increase resolution in highly used rom areas. Obviously its not all that easy or it would be common practice.

How about the JDM STI 16bit ecu, is it capable of being downgraded to run a 205? I mean obviously its very similar in design as far as sensors go - avcs. But I'm a huge huge huge fan of boost by gear (Hondata S300 uses it and its sweet)

Where does one start when he wants to start altering roms/definitions?

Well, it is possible for target boost since the at table falls immediately after the mt table. For the 16-bit ECU, 3d tables are arranged as follows:
[row data][row number of elements - 1][column data][column number of elements - 1][map type byte][table data]
You can check the base defs for the table in question for the row/col/data data type (uint8, uint16) as well as the size of the table (if not overriden in rom def). So, using the total ROM space used by target boost mt and at, you would add additional elements for row/col/data to reflect the new size as well as change the row and column counts according to the new size. The ECU references the single 16-bit map type byte offset, so you'll have to change it to reflect the new offset for your new larger table. Then you'll need to add your new table to the defs with the correct size and new col/row/data offsets.

If none of this makes sense, then it is probably not something you want to be messing with.

I don't know if a JDM ECU will work with a USDM setup. It depends on differences in sensors/wiring harness. I'm not sure where you would find that information, at least for the JDM ECU.

It never hurts to learn, what is a good program to edit the rom? I think I'll need a good hex editor correct?
And I'm never scared of a good challenge.
Thanks again.

Jerod

Ok I have a problem now. I went into ecu flash and was messing with some things. I went to edit map in the a/t target boost location and set row/column to 0. I increased the size of the m/t target boost to 8 columns and 14 rows (was 8 and 9).

I saved it (this is using a stock rom, trying to learn some things) anyway when I opened it back up, M/T target boost was listed under "turbo" not "boost control - Target." That can't be a good thing.

So I opened my current map up (did not make any changes to it, and it has the same changes applied.


Please help me get this sorted out. I'm scared to flash my car again in fear that I will mess some things up!!

Here is a screen shot. Please let me know what you think!

a better image. I really need help.... Not cool.. Hope I didn't ruin any maps...

Changing the defs would be the last step in the process, not the first. Changing what you did is not going to allow you increase the size of the table until you modify the ROM itself. I would not attempt to modify anything until you understand how the data is stored. To fix the defs, just delete the Subaru folder and download the Ecuflash defs.

Thank you. Yea, I realized that after I did it... Anyway where can I find material to learn how to do this from step one!? I feel so stupid, but everyone has to start somewhere...





Thanks again,

Jerod

No, not really. Again, I don't think increasing the table size is going to help you anyway. However, you could use an older ROM revision such as the one attached which happens to have a larger base timing, advance, and primary fueling tables (not target boost, however). But, there were fixes, IIRC, related to misfires in the newer ROM revisions - not sure if that would be a problem or not. They also changed the fine correction rows/column load/rpm values to fix "pinging at high RPM" in later ROM revisions but I assume you tuned these already and simply transfer your entire tune over to the older revision.