CarBerry ROM - EcuFlash Definitions

Carbibbles · **Joined:** Tue Aug 30, 2011 3:17 pm **Posts:** 900

Thanks to andya we finally have a completed EcuFlash def. These definitions allow adjustment of all tuning tables except certain feature option switches which will need to be edited in RomRaider.

Just place the CarBerryBASE.xml file into the subaru/bases sub-folder, and replace your current CarBerry.xml def with the CarBerry "version#".xml in the subaru/impreza sti sub-folder.

These defs are currently for use with v3.6.5, but they should work for future versions as well. If they become incompatible, I will update them as needed.

Update: Uploaded new definitions that andya created with metric definitions included in them. Any table with the (M) suffix will show metric values.

Thanks again andya

andya · **Joined:** Sun Nov 02, 2008 12:32 pm **Posts:** 274

I would say 'no problem' but I absolutely have a new found respect for what you have done with this ROM. When my head quits spinning, I will start on the Metric unit conversion.

rsmotors · **Joined:** Mon Oct 01, 2007 3:06 pm **Posts:** 12

Awesome! I will be on this tomorrow. Been busy on the dyno lately. I should have some time to play with the bugeye again. This will come in very handy.

maxouni · **Posted:** Sat May 05, 2012 3:11 am

Which version of EcuFlash this definition will works?
I have just tested with EcuFlash 1.29 and it shows all maps RPM ranges and MAP ranges incorrectly, SD Compensation map views completely incorrect

.

andya · **Joined:** Sun Nov 02, 2008 12:32 pm **Posts:** 274

maxouni wrote:

Which version of EcuFlash this definition will works?
I have just tested with EcuFlash 1.29 and it shows all maps RPM ranges and MAP ranges incorrectly, SD Compensation map views completely incorrect

Why have you not updated to the latest version of EcuFlash?
http://www.tactrix.com/index.php?option ... &Itemid=58

dschultz · **Posted:** Sat May 05, 2012 5:48 pm

Not that that EcuFlash version matters.
I suspect either a def problem or you are using it to open the wrong ROM version.

andya · **Joined:** Sun Nov 02, 2008 12:32 pm **Posts:** 274

dschultz wrote:

Not that that EcuFlash version matters.
I suspect either a def problem or you are using it to open the wrong ROM version.

Found it. The 1.2 version has 0 tolerance. Conflict with */ in RPM. Tried it on 4 different computers with no issues till I loaded the earlier version of EcuFlash.

karbarian · **Joined:** Sun Dec 25, 2011 8:04 pm **Posts:** 21

CarBerryBASE.xml in folder EcuFlash\rommetadata\subaru\Bases

replaced CarBerry.xml def with the CarBerry STI.xml in subaru/impreza sti folder

and only thing that opens is
-two primary open loop fueling
-throttle tip-in enrichment
-egt too high fault code enable/disable
-timing a/b
-and speed density base load comp. with tables all messed up....

:roll:

Merp · **Joined:** Thu Jul 23, 2009 1:46 pm **Posts:** 863

Carbibbles wrote:

Thanks to andya we finally have a completed EcuFlash def. These definitions allow adjustment of all tuning tables except certain feature option switches which will need to be edited in RomRaider.

Great work guys.

Is there some reason the bloblist feature in ECUFlash cannot accommodate 16bit switches?

andya · **Joined:** Sun Nov 02, 2008 12:32 pm **Posts:** 274

Merp wrote:

Carbibbles wrote:

Thanks to andya we finally have a completed EcuFlash def. These definitions allow adjustment of all tuning tables except certain feature option switches which will need to be edited in RomRaider.

Great work guys.

Is there some reason the bloblist feature in ECUFlash cannot accommodate 16bit switches?

I could look into it but there are so many changes constantly being made with addresses that it would be impractical until a final "Official" version is released.

rsmotors · **Joined:** Mon Oct 01, 2007 3:06 pm **Posts:** 12

So far so good here. I love how I can clean up my map now. Interpolation work wonders.

Merp · **Joined:** Thu Jul 23, 2009 1:46 pm **Posts:** 863

andya wrote:

Merp wrote:

Carbibbles wrote:

Thanks to andya we finally have a completed EcuFlash def. These definitions allow adjustment of all tuning tables except certain feature option switches which will need to be edited in RomRaider.

Great work guys.

Is there some reason the bloblist feature in ECUFlash cannot accommodate 16bit switches?

I could look into it but there are so many changes constantly being made with addresses that it would be impractical until a final "Official" version is released.

Understandable, if you decide to define switches and need a hand or some examples just ask

Also, if the addresses are moving around a lot, I HIGHLY recommend you guys start using unique CALID's for each revision. Otherwise it's asking for someone to mix up a def, corrupt a rom, and brick their ecu.

karbarian · **Joined:** Sun Dec 25, 2011 8:04 pm **Posts:** 21

karbarian wrote:

CarBerryBASE.xml in folder EcuFlash\rommetadata\subaru\Bases

replaced CarBerry.xml def with the CarBerry STI.xml in subaru/impreza sti folder

and only thing that opens is
-two primary open loop fueling
-throttle tip-in enrichment
-egt too high fault code enable/disable
-timing a/b
-and speed density base load comp. with tables all messed up....

:roll:

Thanks to Andya all works fine now, seems to be some sort of user error :lol:

dschultz · **Posted:** Mon May 07, 2012 11:22 am

Merp wrote:

Also, if the addresses are moving around a lot, I HIGHLY recommend you guys start using unique CALID's for each revision. Otherwise it's asking for someone to mix up a def, corrupt a rom, and brick their ecu.

I agree 100% with this approach. If you stick to three version digits then set the CAL ID to: CrBry365
Next revision would be: CrBry366

You can setup a dependency list if you wish for common unchanging items and refer back to an earlier version as needed. then just keep the base up-to-date.

Code:

<rom>
  <romid>
    <xmlid>CrBry366</xmlid>
    <internalidaddress>200</internalidaddress>
    <internalidstring>CrBry366</internalidstring>
    <ecuid>3D04EA4605</ecuid>
    <year>02-03</year>
    <market>JDM</market>
    <make>Subaru</make>
    <model>Impreza</model>
    <submodel>STi</submodel>
    <transmission>MT/AT</transmission>
    <memmodel>68HC16Y5</memmodel>
    <flashmethod>wrx02</flashmethod>
  </romid>
  <include>CrBry365</include>
</rom>
<rom>
  <romid>
    <xmlid>CrBry365</xmlid>
    <internalidaddress>200</internalidaddress>
    <internalidstring>CrBry365</internalidstring>
    <ecuid>3D04EA4605</ecuid>
    <year>02-03</year>
    <market>JDM</market>
    <make>Subaru</make>
    <model>Impreza</model>
    <submodel>STi</submodel>
    <transmission>MT/AT</transmission>
    <memmodel>68HC16Y5</memmodel>
    <flashmethod>wrx02</flashmethod>
  </romid>
  <include>CarBerryBASE</include>
</rom>

Carbibbles · **Joined:** Tue Aug 30, 2011 3:17 pm **Posts:** 900

Updated the first post with andya's def fixes.

maxouni - try removing any ecuflash defs that have anything to do the carberry rom. Then restart the computer and put these defs in place and open a rom. Ive had some weird issues with ecuflash defs before and this seemed to fix it.

Ill put in a CALID system for ecuflash, with romraider I have a byte that is checked for version information to make sure the user is alerted if the wrong def is used with the wrong rom. But I don't think EcuFlash can do that.

RomRaider

Forum rules

CarBerry ROM - EcuFlash Definitions

Who is online