RomRaider

Hi Freon,

Is there any chance you'd want to put your code into an otherwise stock A2ZJ710J ROM? That would make it a safe flash for the rest of us 2004ers I imagine, and then we could just update the tables to our current tunes and flash it in.

Awaiting (and drooling) in eager anticipation...

I don't consider any flash automatically "safe".

Yeah I will try to copy it over to an otherwise stock rom.

Freon, is ur rom safe to try on my fp green setup? U stated u had hacked some tables that where not in rom raider defs. I don't feel comfortable with a rom that I can't see the tables that have been changed.

Well. Yeah. I guess when I said safe, I didn't mean safe as in safe, but more as in safer.

Very, very cool.

It's mainly stuff to try to keep the DBW throttle open more at idle to help with idle stability. Default throttle open angles at idle and such. I don't think any of those DBW changes are fundamentally unsafe.

Some CELs are defeated there too, like the TGV codes, some rear O2 codes, etc., that may not apply to your car.

I'll copy the code into an otherwise stock ROM. I have never loaded it on a stock or stage 2 car, and like the FAQ states I do not think you need SD with a stock or stage 2 car. But it needs to happen eventually anyway to give people another starting point... This isn't actually very hard so I'll try to do it soon before I get back on the XML and try to finish up the SD hack for 05 STI.

[quote="Freon"]It's mainly stuff to try to keep the DBW throttle open more at idle to help with idle stability. Default throttle open angles at idle and such. I don't think any of those DBW changes are fundamentally unsafe.

Some CELs are defeated there too, like the TGV codes, some rear O2 codes, etc., that may not apply to your car.

I'll copy the code into an otherwise stock ROM. I have never loaded it on a stock or stage 2 car, and like the FAQ states I do not think you need SD with a stock or stage 2 car. But it needs to happen eventually anyway to give people another starting point... This isn't actually very hard so I'll try to do it soon before I get back on the XML and try to finish up the SD hack for 05 STI.[/ nb. Thanks, that would be great and thanks for your time spent on this project.

Cool. Sounds good.

FWIW, i'm running a twin-scroll GT30R setup.

[quote="fastblueufo"][quote="Freon"]It's mainly stuff to try to keep the DBW throttle open more at idle to help with idle stability. Default throttle open angles at idle and such. I don't think any of those DBW changes are fundamentally unsafe.

Some CELs are defeated there too, like the TGV codes, some rear O2 codes, etc., that may not apply to your car.

I'll copy the code into an otherwise stock ROM. I have never loaded it on a stock or stage 2 car, and like the FAQ states I do not think you need SD with a stock or stage 2 car. But it needs to happen eventually anyway to give people another starting point... This isn't actually very hard so I'll try to do it soon before I get back on the XML and try to finish up the SD hack for 05 STI.[/ nb.

Freon, email me the rom or post it up when if you get the sd on a stock rom. I looked at it in ecu edit and it looks tipical of a ve map. very nice job. Looks to be pretty straight forward as far as tuning the table goes.
Why do you still have some of the maf table non zeroed. I would think you could just zero out the table if its not being used.
I am very interested in trying sd out with my fp green. I think it will help me out alot with some issues that I have had to work around.

Well I left the MAF table there just so you could compare your MAF if you want. You could zero it. I suggest setting the voltages to zero, not the data output. I'll explain.

2D and 3D maps are read from right to left, bottom to top. Incidentally (or maybe not so?), this would give fastest execution at high load, high RPM, warm engine and the slowest execution time slowest at idle, warming up.

It is zero'd to save CPU cycles. By shifting the MAF table to the right and leaving the left half under voltage range it saves the subroutine loops where it looks down each axis for a match. In fact I think that change makes the whole subroutine run faster than stock even with SD in there. Maybe not in all circumstances, but in most. 3D maps read quickly. MAF is actually slow because at idle it has to count down 40-50 columns. VE map at 15x15 would never take more than 32.

If you need an extra hand porting the code to other ROM versions, you can count me in

I have no plans to port to HC16. If you want to port it to 16bit, go for it. Hopefully the Excel model, FAQ, and source code are sufficient to explain what needs to happen.

Keep in mind I'm providing this under the guise that it will not magically show up in commercially sold maps or products. I'll be more than slightly upset if someone sells the work I am giving away for free.

I think you misunderstood what i said

just offered to port the 32bit code to any other 32bit ROM people might ask for, and absolutely for free...

Well, I plan on doing that myself as time allows, but knock yourself out. I released source code and modeling so it could be understood but also to be reproduced.

I will probably not be able to get to them all. I'm mainly shooting for 04-07 STI and 06-07 WRX, and eventually 08 as well. It may be a while before I get around to all the LGT and FXT models.

I know things are slightly rearranged in some ROMs. Like the D/A conversion will happen in one subroutine, then another will check the upper and lower CEL limits (for P0102 and P0103). You may be able to place the code in either subroutine. I haven't quite gotten there yet.

I didn't mean to come off as overly defensive.

Then be sure to license it as such...if this works as well as advertised, someone is gonna try to package it and sell it.

I agree with trying to license the code. Something like this, maybe?

http://www.gnu.org/licenses/gpl-howto.html