RomRaider

Oh and btw, did you find that you can run more timing in warm weather than cold ? Check this out when you have a minute ... still doing some research but I found this interesting

viewtopic.php?f=25&t=10462

This infamous stumble has a lot of people scratching their heads. My modification "seems" to have smoothed out that stumble a bit although I didn't really have a big stumble issue to begin with so this was a small improvement for me. I believe there is more going on here than it seems since the load CL load comp table shouldn't really make that much of a difference but it does. Few months ago I went back to the stock values in that table and got the occasional stumble while cruising on the highway in 6th. I did some logging and there was nothing unusual in the logs aside from that brief lean condition in CL which is what caused me to notice it in the first place. The odd part is, this happens in CL and since target AFR in CL comes from the O2 sensor, you would think that the ECU would just immediately compensate for it. That suggests that this condition should never happen but it does. So, either this is triggered by a mechanical condition somehow which was suggested on some threads or there are some other settings in the ROM that we don't know about that are interacting and causing the issue. Also, and this is unlikely but possible, the firmware in the ECU may have a bug that manifests itself this way. It is software afterall and it can have bugs My correction was mainly triggered by seat of my pants and the values I dialed in have eliminated this condition for me. Since I don't have real data to really back this up, I need to put a disclaimer on this meaning that your results may vary. These settings may have a different effect on your car. IMO, folks have been chasing this issue and experimenting with different settings but it isn't really clear what the exact cause is so if you don't know, how do you know you really fixed it? For this ROM, the settings I dialed in seem to be working well and I found some minimal gains in fuel economy.

Hey thanks for getting back and sorry for the late reply. It's interesting, I was under the impression that the load comp were also applied in OL not just CL. Are you positive that they are just active in CL ?

I seem to have improved my knock issue on spool but, the two main changes were :

1. Boost target are more progressive, I had a bit of a step function across torque request
2. I tweaked the load comp table to enrich in the 3200 rpm range.

It's also warmer out so maybe that help. Building my timing back up now slowly

You should be able to run more timing in cold weather, at the same load and RPM. Cold air is more resistive to knock hence it can tolerate more compression before it starts to spontaneously ignite. Consider how IAT comp table works. It adds timing as IATs drop and it pulls timing as temps increase. Obviously, each end has a finite limit and you can see that in the numbers. At each extreme, efficiency takes a back seat to safety. If you find yourself knocking as temps drop across several areas, take a look at your IAT comp table and possibly reduce the ramp up. Also, you could potentially adjust IAT activation table to fine tune how much of the compensation you'd like to see in certain areas. It is likely that your fuel composition in your area is different. I fill up typically with Shell which has a healthy dose of ethanol (up to 10%) and some ethanol is good for performance.



Pretty sure that table applies to CL only. Several reasons that make me say that, the table description states that the compensation is applied in CL, the tables themselves are defined in CL area and the most logical reason for it is, why would you need a comp table based on load for OL? The primary table already is based on load so any adjustments can just be made directly in that table. It would make no sense to have this comp applied in OL as it would offer no benefit and just complicate the code in the ROM.

UPDATE: I addressed couple issues based on feedback received. I revised the DBW profile and some WGDCs to improve low RPM response, adjusted based ignition timing maps in mid and high RPMs/high loads since several users reported that their cars do not tolerate the dialed in timing. So, the default ROM now runs with lower timing in those areas. Folks with better gas can adjust the timing to suit their cars (my car included).

Funny, every time I go on vacation, I end up posting an update. Apparently vacation time is when I have time to post

Good news, thanks to a generous donation from one of the users of this ROM and the fact that my birthday just came the other day (yay for me) , I am planning a trip next week to talk to folks at Kaizen Tuning to get a couple of pulls on their AWD dyno. The goal is to get a read out on the dyno to see what the car is putting down at the wheels. It should be interesting, if anything. Once I get a read out, I will post the results. Stay tuned.

Hi Ziggyrama

Happy Birthday Bro!! Thanks for the update!

I finally have time tomorrow to plug in my AEM UGEO with data log. I have the COBB Intake so before I can run your (5/22)tune I have to adjust maf voltage. Then I will post what I get.
Just to be clear I should data log RPM, Load, FBKC, FLKC, IAM, IAT, MAF, Target Boost relative, throttle?

I'm 3 hours away from Kaizen Tuning, I'm in NYC. Have fun and take a video!

Thanks. Also add requested torque to your counters.

Hey, I just drove through NYC this past weekend on my way back from the vacation. $13 for a toll on Washington bridge WTH And the thing is filled with pot holes. Unbelievable. As usual, I got stuck in traffic. That part is amazingly consistent.

Quick update, I went down to Kaizen Tuning today to get some dyno numbers. Turns out that Kaizen uses Dyno Dynamics which is also known as the heart breaker dyno. In the end, what I wanted was to see the numbers and compare them to what a typical stock STi puts down on this dyno. I updated the first post on page 1 with the power graph from the session. The car put down 250Hp/275TQ which are good numbers for a stage 2 setup. For reference, a stock GR STI puts down 200HP on this dyno so the gains are real. I will tweak a couple of things in the next few days and a revised map. For reference, this is the plot:

I was going through your map, hats off for the effort. these dyno numbers compared to the stock sti is great.

I have 2 question:
why you disabled the Rear O2 sensor?
did you do any MAF scaling?

Thanks. The dyno is proof that the ROM is making real power, in line with what a stage2 setup should be making: 25% improvement in HP, 37% improvement in TQ over stock.

To answer your question, rear O2 sensor has no function other than to keep tabs on the efficiency of the rear catalytic converter. Once you go to stage2, the rear cat is either gone or replaced with something else (high flow cat). The readings from the sensor will not be useful and will trigger a useless CEL if you do not disable the code. AFAIK, all stage2 ROMs disable rear O2 sensor.

I did not do any MAF rescaling. This ROM is intended for stock intake and stock MAF calibration is good enough such that it does not warrant modifications. Bear in mind, once you start changing MAF scaling, your calculated load numbers will be different and that will affect lots of tables. So, if you're thinking about doing that, know what you're getting into.....lots of work with basically no payoff. If I were to go to an intake, I'd look at recalibrating MAF scaling. FYI, I have no plans to replace my stock intake. At this point, anything short of a turbo upgrade or alcohol injection will not yield major power gains on my car.

Thanks Ziggyrama for you answer, I guess I will try your map on my 2012 with similar modes. we will let you know the result.

Are you referring specifically to disabling the CAT efficiency DTC P0420, rather than disabling the rear O2 codes?

Both Actually I have a catted downpipe and all these sensors are enabled I did not see any CEL. I thought it has to be disabled in the catless.

Yes. There's a handful of code that I disabled in the ROM that are related to the rear O2 sensor. Without that, at least the USDM cars would end up throwing a CEL eventually. In the case of a non USDM car, perhaps the logic in the ROM is different and CEL is not triggered? I imagine different parts of the world have different regulations which may explain the difference in behavior. Note, it takes time for the car to throw the cat inefficiency CEL. If you're flashing ROMs on daily or semi-daily basis and not drive the car 100+ miles a day, you may not see the CEL since the car hasn't had time to trigger the code. I cannot speak for non USDM cars as I don't have experience there but in US, the car will post the light if you give it time.

Car: Subaru WRX STI EDM 2012 Hatch
Mods: Grimmspeed Electronic Boost Solenoid + Crawford Catted Downpipe + Drop-in Panel Filter + Crawford Air/Oil separator can + TurboSmart BPV replacing stock (No Tune required) + TurboSmart Wastegate Actuator 7psi replacing stock (No Tune required)
Fuel: 98 Octane (RON)

Today I flashed it to my Car using my base ECU AZ1G700K, the purpose is testing only. Will do some logs later and keep you posted.
I realized that you have more tables than mine:

Requested Torque Limit A (Per Gear/Engine Speed)
Requested Torque Limit B (Per Gear/Engine Speed)
Timing Compensation Per Gear (all Tables)
Fuel Temp Sensor Scaling

Also I found a bug when you compare image on RomRaider v.0.5.8 RC1, I got differences in Requested Torque (Accelerator Pedal) SI-Drive Sport, Sports Sharp and Intelligent.

The Tables are completely identical

I compared the images using ECU Flash and it showed no differences. I guess it is something to do with the RR definition file(May be)