RomRaider

Donations are welcome!

Edit: Version 2, fixed Open Loop Primary Fuel tables as X & Y axis sizes were interchanged.
This RomRaider Editor def is partially based on various previous defs.

This EcuFlash def is based on the RR def above. Let me know of any issues.
Store the file in directory: \Program Files\OpenECU\EcuFlash\rommetadata\subaru\Forester 2.0
of your ECUFlash installation. Updated EcuFlash 32BITBASE def is needed for the above def.
Store the file in directory: \Program Files\OpenECU\EcuFlash\rommetadata\subaru\Bases

The logic around quite a few tables seems to have changed in this ROM. Let me know if I didn't get it right.

The RomRaider Logger def for this ROM can be found in this post.
Use minimum logger.xml version 46.

Thanks for this definition. A lot of enthusiasts from my country has been waiting for something like this since the sh5 came out.

Hey Dale,

Thanks for the effort on this one! Just a few questions about the defs though...

Ecuflash

Fueling - Warm-Up Enrichment group contains no tables.


Romraider

Fueling - Warm-Up Enrichment group available (though empty) in Ecuflash def is absent altogether

Fueling - Primary Open Loop Fueling Cruise is scaled oddly... rpm axis goes to 4000rpm in 7 rows then the last 4 are zeros. Could be it's supposed to be this way with extra rows but these extra rows are not all one value as is usually the case when Subaru wastes space in tables. Ecuflash definition looks much more normal with only 7 rows.

Fueling - Primary Open Loop Fueling Non-Cruise is scaled oddly. I would guess the table should only have 12 columns like the Ecuflash def.

Timing Compensation (IAT) Activation table has two identical values in the engine load scale but the values in these two rows are different. Seems a little odd.

Intake Cam Advance Angle Non-Cruise I can enter a minimum value of -40* which is possible I guess, but maximum value can be set up to 215*, which cannot be mechanically possible.

Exhaust Cam Retard Angle Non-Cruise I can enter a minimum value of 0* which is possible I guess, but maximum value can be set up to 255*, which cannot be mechanically possible.

Everything else looks entirely reasonable from a quick skim. Thanks!

WOW something got messed up. I'll have to check what happen between my review and posting the def as it was all A-okay before my post.

There are no Warm-up enrichment tables as the logic is so weird it would be another month before posting anything. Do you really need it?

Hell no, I don't need that. Just wanted to give you all the errors I found.

Should I have updated anything else in RR before testing the definition?

None have been defined yet.


None have been defined yet.

The X & Y axis sizes in the RR def had been interchanged, fixed in v2 def

Yes that's odd and it is how the values are set in the ROM. It is still used in the logic, but now acts more like an on/off switch for "Timing Compensation IAT" more than anything.

This is the same behaviour as any other ROM and any other table. The min/max is enforced only by the acceptable values for the particular data type of the field. i.e. unit8 range is 0 to 255, uint16 range is 0 to 65535. This range is then used in the table data formula to determine the limits. So for the intake AVCS with the data type uint8 and expression="x-40" the min is "0-40" and the max is "255-40". I guess as a tuner you already know the 215 degrees of advance is not possible. Hence tuning is not for the uneducated

Original post has been update with a new RR def. The EcuFlash def was correct all along.

TBH, this t00ner had never tried to put such silly values into other ROMs. I was curious about the ranges on this one as it's clear Subaru have defined the cam centerlines differently than on EJ series engines.

Thanks for the effort Dale. I don't know what we'd do without you! The revision works great for me now.

You're welcome.
The enforcement of the range is a little odd. I say this because the EcuFlash defs actually have scaling limits defined, but they do not appear to be enforced. I tried -40 to +40 in the def but EcuFlash still allowed me to enter the max the data type could handle.

BTW I think they call this the FB engine...
http://en.wikipedia.org/wiki/List_of_Su ... _FB_engine

Yes, this is the FB20. I was looking at the fact the intake AVCS values in the stock ROM are in some tables negative values and wondering if that meant the cam could retard from the centerline, and remembered that in EJ series engines the zero position according to the ECU may not be at the cam centerline but some degrees away from that. As soon as I get a car in my hands I will be trying to see what values the hardware will actually reach.

Thanks again Dale! Donation coming as soon as I can confirm with a car that we can flash it.

Hey Dale, I just sent you a donation for this one. Can you check the DBW tables are labeled correctly? It seems the Sport and Intelligent tables are identical and the Sport # is less aggressive, which seems odd. Interestingly, the X model doesn't even have Si-Drive, it has the sportshift trans...

Thanks again for the support!

If the Si Drive parameter is not in the Logger list then most likely it is locked to a specific value forcing only one of the three tables to ever be used. I could provide you with a special logger.def to allow you to query the Si Drive mode. With that info I could determine if it is locked and then re-name the DBW tables more appropriately.

Yes, it could be one of those Subaru 'let's put the code here now but not use it until next year' things. Or, two of the map sets could be toggled with Sport mode and D...
TBH I am running the same timing tables now in all three modes anyway. Next time I have one of these cars on hand I will check to see if the Si-Drive mode parameter shows up to be logged.

Or, let's base this ECU code off of a 2.0 JDM STi with daul avcs and disable all the stuff we don't need.
If there's no Si switch then most likely there's no Standard parameter to log. I looked at the ECU init string and I'm pretty sure the Si Drive parameter is not going to show up in the list.

Hi, I have a machine with the Forester, 2011 s-edition, sh9
I want to install the si-drive, on the dashboard is a display mode s, s#,i, but they are not active ...
is it possible to buy a block of Si-drive from Japanese and install configuration?