RomRaider

CarBerry ROM - 16bit Speed Density Project



Attention Tuners: If you are tuning for money and you use this ROM on a customers car (even if they "provide it"), I would request that you send $20 per customer via Paypal with the DONATE button above or below. I have put a lot of time and work into this ROM and I believe this is a fair amount, especially considering other rom patches with less functionality are generally $35+. Obviously this is all on the honor system, but please consider that I have put over 1000+ hours into the development of this ROM and my time is worth just as much as yours when you are tuning. I feel that I have made enough modifications to this ROM to distinguish it from anything else available and I believe that has value.

This ROM will continue to be free for personal use but feel free to make any donations if you appreciate the ROM. Thank you.



This is a ROM developed to enhance the capability of the stock ECU on 16bit Subarus. It uses a Speed Density control scheme which means fueling is calculated primarily from the MAP sensor instead of the MAF sensor. The ROM is based off the Group-N ROM and will only work on certain 16bit ECUs (see verified list below). You must have TGV deletes to run this ROM, this will be fixed in future versions (fixed in 4.2.0). The goal of this project is to provide stock ECU users with some of the benefits of aftermarket ECUs but retain the ease of use and low cost of Open Source.


Disclaimer: I assume no responsibility for any damages inflicted by running this ROM, use at your own risk.


Current Features Include(Includes Group-N Features)
-Speed Density
-Rally Style Anti-Lag
-2Step Launch Control
-Per Gear Wastegate and Boost Target control
-Anti-Lag enabled/disabled via user defined switch
-Aggressive Launch Control
-Flash CEL in the event of knock w/DTC functionality
-Fuel Pump Duty Control
-Map Switching
-Launch Control Static Fuel/Timing (Aggressive Launch Control)
-Positive/Negative MAP Sensor Offsets for aftermarket MAP sensors
-No Lift to Shift (Requires slight wiring modification)
-Cut X from Y for Launch Control and NLTS
-Spark cut Launch Control
-Increased Load Cap to a Max of 8.0g/rev
-IAM and FLKC Functionality w/New IAM calculation method
-Rotational Idle
-Target Boost Cap Increased to 64psig
-Knock Mode Indicator
-Force Pass Readiness
-Force Full Time Open Loop
-OverBoost Fuel Cut
-Mass Airflow mode w/blending capability!
-Knock sensor control definition updates
-Datalogging definition updates
-Per cylinder knock threshold logging
-Per cylinder knock noise level logging
-Per cylinder knock count
-Combined knock count
-Low Injector Pulsewidth compensation (enable/disable option)
-Intake Port temperature estimation for IAT compensations (enable/disable option)
-Omni Power Map Sensor Fix
-Injector Timing Definition
-A/F Learning Disable in open loop
-Tons of new idle control definitions
-Logger definition updates
-Evap compensation disable
-Updated Speed Density Tables to closer resemble a stand-alone ECU system
-Flex Fuel Capability!
-TGV Control!
-Alcohol Injection Control (Beta)
-Engine Load Smoothing
-Load Based Ignition Table option
-Individual table switching/blending control


Future Features Include
-Oil Pressure/Wideband Safety


Verified ECU Compatibility
-Although this ROM should work with any ECU that uses the wrx02 flash method, this is a list of tested and verified compatibility.

• USDM 02-03 WRX
• EDM 01-05 WRX
• EDM 03 STI
• ADM 01-02 WRX
• JDM 02-04 WRX
• JDM 02-04 STI

The current version is 4.2, this is the eleventh public release. If you have any issues/comments/requests please post up and I will see what I can do.


Version Log
4.2

• Flex Fuel Capability!
• TGV Control!
• Alcohol Injection Control (Beta)
• Engine Load Smoothing
• Load Based Ignition Table option
• Individual table switching/blending control
• Various definition additions

3.8.5

• Mass Airflow mode w/blending capability!
• Knock sensor control definition updates
• Datalogging definition updates
• Per cylinder knock threshold logging
• Per cylinder knock noise level logging
• Per cylinder knock count
• Combined knock count
• Low Injector Pulsewidth compensation (enable/disable option)
• Intake Port temperature estimation for IAT compensations (enable/disable option)
• Omni Power Map Sensor Fix
• Injector Timing Definition
• A/F Learning Disable in open loop
• Tons of new idle control definitions
• Logger definition updates
• Evap compensation disable

3.6.5

• Fixed bug with Map Switching

3.6.4

• Fixed Per Gear comp enable/disable backwards
• Fixed Fuel pump duty switching

3.6

• Fixed small bug with per-gear boost control

3.5

• Changed Base Timing X-Axis from MAP relative to MAP absolute
• OverBoost Fuel Cut
• Target Boost Cap Increased to 64psig
• Knock Mode Indicator
• Force Pass Readiness
• Wastegate Duty Cap
• Force Full Time Open Loop
• Fixes to allow FLKC and IAM to become active
• New method of IAM implementation "total timing = Base Timing - (KCRM - (IAM/16 * KCRM))". With this method KCRM(Knock Correction Retard Max) is removed from Base Timing based on IAM (at an IAM of 16, no timing is removed : at an IAM of 0, the full value of KCRM is removed).
• Added full size Knock Correction Retard Max Table
• Various new knock control tables and definitions
• Increased Target Boost Cap to 64psi
• Added Headlight switch as ECU input
• Added Loggable Knock Correction Mode Indicator (use attached SDlogger def, 0=Knock Control Disabled 1=FBKC Mode 2=IAM Mode 3=FLKC Mode)

3.3

• Increased load cap to 8.0g/rev (must use the SDlogger def to correctly log engine load.)
• Fixed logging issue

3.1

• Added Knock Control Disable w/Active Launch Control

3.0

• NLTS
• Removed the MAX load table
• Included Decel Fuel Cut Table
• Included the ability to use positive or negative values in the MAP sensor offset
• Removed the user levels
• Coded in a "cut x from y" method for launch control and NLTS (to get a quicker more accurate RPM hold)
• DTCs can effect CEL status alongside KnockCEL
• Sparkcut Launch Control
• Ability to disable Defrost logic (if anybody ever had issues with using it as an input)
• Fuel pump duty hysteresis (so fuel pump duty doesn't go crazy when you are right on the edge of the switch point)

v2.6

• Re-Organized Defs
• Added Map Switching
• Added Aggressive Launch Control(Static Fuel/Timing)
• Multiple Choice Input Controls
• Added Auto Transmission Logic Disable (To accommodate using the TID pin as an input)

v1.5

• Initial Release

-I would like to give a huge thanks to the following people for their input, testing, and general tuning discussion that has helped this project move forward.

• fastblueufo
• elevenpoint7five
• JSarv
• Merchgod
• bcheck555
• ride5000
• mrf582
• andya
• ckibue
• Wrick
• 02rexwi
• lukesky_wrx
• seanathan
• gaby
• Dr Waffles
• Artizle

And of course thanks to dschultz and all the guys that have developed the romraider software.

If you have been part of the project and I missed your name I apologize, shoot me a pm


-ROMRAIDER v0.5.3b RC10 OR NEWER IS REQUIRED FOR EDITING OF THIS ROM - You can download this here --> ROMRAIDER Download

--Please read "How to transfer tables" under "Setting up a Base Map" in post#3 of this thread to avoid ROM corruption when upgrading to a newer version of the CarBerry ROM.

--Versions newer than v3.6.5 use a patching utility to apply a patch to the original group-n rom. This separates my modifications from the original Subaru ROM file. Just run the patching utility and it will patch the provided "Speed Density Base.hex" file to the latest revision of CarBerry. Use the provided definitions only for the patched rom.




MD5 Hashes
---------------------------------------------------------
Speed Density Base.hex - 4829E0CB0DDDDDCDAA47C88391C4B3C7
CarBerryROM-rev4.2 - 8572ABC6D7037A0ED099EE7D9E0A050B

Speed Density
Re-writing this

Knock-CEL

Knock-CEL Enable
This enables the Knock-CEL function, DTCs will not effect the status of the CEL when this function is enabled.

Knock-CEL Sensitivity
This value controls the amount of FBKC required to illuminate the CEL. FBKC must fall numerically lower than this value to trigger the CEL. If the sensitivity is at "0" and you get any negative FBKC (ex. logged -2.11 FBKC) then the CEL will light. If you have the sensitivity set at "-5" and you log "-2.11" FBKC the CEL will not light, but if you log "-5.1" with the sensitivity set at "-5" then the CEL will light. So the FBKC has to drop further negative than the "sensitivity" setting in order to light the CEL.


Anti-Lag

Attention Anti-Lag users:
-First of all, I would like to mention, as many others have, that the ALS can be hazardous to your engine/turbo. Please keep this in mind if you decide to use this feature of the ROM. The use of the ALS requires more advanced tuning and should only be used/tuned by more experienced tuners that fully understand the risks involved. For all users of the ALS please make sure your vehicle is set up accordingly, this includes the removal of all catalytic converters(rendering the vehicle as off-road use only) and re-locating the front O2 sensor to the downpipe as it can break apart and destroy your turbo.


Throttle Kick
I finally got a chance to dig through the TPS code and figure some stuff out. The anti-lag that we have been using thus far has been very mild, and I believe the ROM is actually meant to be used in conjunction with a "throttle kick". Please note that I am using the term "throttle kick" in reference to locking the throttle slightly open so that more air can enter the engine when no throttle input is being applied (I am not referring to the act of actually kicking"with your foot" the throttle pedal). A throttle kick can be implemented in various ways, most often with a longer set screw. The amount of "kick" can generally vary from 5% to 15% depending on how aggressive you would like to go.

If you look at the idle timing tables and idle speed target tables you will notice they have two rows, one being .58v and one being .74v. These are slightly mislabeled as "Throttle Position Sensor (Volts)" (I have corrected the labels in the upcoming version). The parameter that these tables are actually referencing is basically the amount of "throttle kick" that has been applied, the .58v row is stock throttle position(completely closed) and the .74v row is about a 6% throttle kick(this row will be used at higher kick percentages as well). This referenced value remains constant no matter what your current TPS voltage is. So now these tables start to make a little more sense, you can see that the ECU removes timing and adjusts the idle speed target based on the amount of throttle kick that has been set in order to keep the engine from revving up due to the cracked open throttle. I have done some testing and I can tell you that with the throttle kicked open a bit the engine definitely has a more "lumpy" idle that is usually associated with rally cars. Having the throttle kicked should produce a much more aggressive ALS, I haven't done any testing yet but I will soon.

So the question is, "How do I set up a throttle kick?". Well first of all you need to decide what method you will use to keep the throttle plate cracked open. Usually you can use a longer set screw but other methods can be used as well. I will leave this up to you. Turn your key on and log TPS volts, you should "kick" the throttle open to a value between .74v(~6%) and .9v(~12%). Then you need to "calibrate" the kicked throttle. To do this is very easy, the ECU "zeros" out the throttle after reset. So to calibrate the throttle all you need to do is set up your throttle kick, then reset the ECU using learning view or the romraider logger (I used learning view). And that's it, your ECU will see your "kicked" throttle position as 0% throttle. And now (depending on if you set your kick to .74v or higher) the bottom row(.74v) of your idle timing and idle speed target tables will be used. If you decide to set your throttle back to normal you do not need to reset the ECU, just remove the kick and the ECU will "re-zero" the throttle.


In the next coming version I will also add support for a solenoid actuated kick that will automatically zero the TPS without an ECU reset. This will allow users to switch between a kicked throttle and standard throttle with the flip of a switch (with the addition of a throttle kick solenoid to the throttle body)



Map Switching

Map Switching - Enable
This enables the Map Switching feature.

Map Switching - Input Control
This selects the switch that will be used to determine the active map. When the selected switch is activated, all tables with the prefix "Map2 -" will be used.


Launch Control

Launch Control - Enable
This table Enables or Disabled Launch Control.

Launch Control - Input Control
Select an input to control the active status of launch control.

Launch Control Mode Disable (Veh. Speed)
This is the Launch Control Vehicle Speed Threshold.

Launch Control Fuel Cut (RPM)
This is basically your Launch Control Target RPM, generally you can set its values 1 RPM apart for tight RPM control.

Launch Control Mode Enable (RPM)
This is used for the Static Fuel/Timing if it is Enabled. Fuel/Timing will lock at the specified static values over this RPM.

Launch Control - Static Fuel/Timing Enable
This enables the Aggressive Launch Control feature. By forcing the Fuel Target and Ignition timing to be static you are able to lock them at very low values which will increase boost and power upon using Launch Control.

Launch Control - Static Fuel Target
This is the Fuel Target that will be used when Launch Control is Active and RPM is over "Launch Control Mode Enable (RPM)". Set this low to something like "9" or "10".

Launch Control - Static Ignition Timing
This is the Ignition Timing that will be used when Launch Control is Active and RPM is over "Launch Control Mode Enable (RPM)". Set this low to something like "-10" or "-12" (Note the negative).


No-Lift-To-Shift (NLTS)
The NLTS system calculates the RPM of the next gear based on vehicle speed and attempts to rev-match to that RPM while also cutting fuel to unload the drivetrain and allow extremely quick shifting. You must wire your clutch switch to an ECU input and also make sure your "gear determination thresholds" are set up correctly for your transmission.

Clutch Switch Wiring
The cruise control clutch switch must be used for NLTS, this switch has a 2 wire connector with a yellow/red wire and a yellow/green wire. You can wire the switch in two methods.

A. If you don't care to retain your cruise control functionality (cruise control will be disabled with this method) you can simply snip the wires and run one from the connector to a ground and the other to the ECU input pin/wire. If you choose to wire it this way you must set the clutch switch input to "inverted" in the NLTS settings. See the diagram below.


B. If you wish to retain your cruise control you can wire it up with a 12v source and 2 diodes. This will retain cruise control functionality. Follow the diagram below for this method.


Clutch Switch Adjustment
For better results, you way want to adjust the clutch switch closer to the clutch pedal. Without this adjustment you may experience some jerkiness when releasing the clutch in a slower manner.

NLTS - Enable
This table Enables or Disabled NLTS.

NLTS - Activation Input
Select an input to control the active status of NLTS.

NLTS - TPS Threshold
This is the TPS threshold, above which, NLTS will be active.

NLTS - Clutch Switch Input
This determines the ECU input that you wire your clutch switch to.

NLTS - Vehicle Speed Ratio Units
These are the units that are used to calculate the rev-matched RPM between shifts. Use the "Vehicle Speed Ratio Calculation" logger parameter in the SDlogger.xml and obtain average values for each gear. The ROM is setup by default for a standard USDM wrx 5speed.

NLTS - Minimum Calculated RPM
This is the lowest RPM that will be calculated to rev-match to when shifting gears.

NLTS - RPM Offset
This is a static offset to the calculated rev-match RPM.


Fuel Pump Duty

Fuel Pump Duty - Switch Point (MAP)
This is the point based on Manifold Absolute Pressure that the Fuel Pump duty will switch from low to high.

Fuel Pump Duty - Low Duty Cycle
This will be the Fuel Pump duty when MAP is below the "Fuel Pump Duty - Switch Point (MAP)".

Fuel Pump Duty - High Duty Cycle
This will be the Fuel Pump duty when MAP is above the "Fuel Pump Duty - Switch Point (MAP)".

Awesome work. I can't wait to try it out!! I'll have to re connect my heater control now so I can use the defrost button...

Thanks a whole bunch Jason, awesome work here, will be testing in JDM cars shortly

Carbibbles, are you planning to support any EDM 16bit ecus like A4SE900D(2001/2002)? I can be the test mule. I can even test it on 16bit EDM STi 2003+ and 16bit EDM WRX 2003+ if needed.

Thank you for sharing your hard work with the rest of us! You are doing amazing work!

Correct me if I'm wrong, but wont this work for EDM WRX's since they use the same flash method?
As for the 16 bit STI's, I believe it would work for them, except AVCS wouldn't be active...

This should work on any ECU that uses the 02wrx flash method (including some non usdm STIs), so it should work on the EDM ECUs that you mentioned subeboost. And this ROM does support avcs so that shouldn't be an issue.

I can confirm that this rom works on EDM 16bit ECU. I just finished my testing session. No ghost CEL and defrost button works just fine. One thing I noticed is that the engine moves/shakes more when you turn it off compared to MAF rom. Is this normal?

The idle targets are set to 1000rpm by default in the CarBerry ROM, it is possible that the increased engine shake is from coming down from a higher rpm. You could try setting the idle targets down to stock settings and see if that helps


Thank you for verifying that it works on your ECU. I think I will put up a list of verified ECUs in the main post, what year/make/model did you test it on?

wonderful, just more reason for me to swap to a EJ207 and get rid of my 06WRX's 32 bit ECU lol

Well you moved along quickly since we last talked I haven't looked at it yet, but nice work Jason!

Yeah, I had experience with hacking roms for turbododges so it helped me figure out the subaru stuff pretty quick. I love doing stuff like this so ive been pretty motivated

Thanks

What's your background on this besides previous ROM hacking? Software engineer?

Definitely not a software engineer, but I am going to school for mechanical engineering. I've always been a bit of a computer nerd, this stuff really isn't that complicated once you get the basics down and its mostly just a bunch of math. I've been working with the Subaru logic for about 9 months now.