Its never worked that way for me. Lean spool has always caused lean AFRs at unexpected or unwanted times resulting in unwanted knock. I thought about trying to tune the lean spool tables, but in the end, it made more sense to me to just turn off lean spool and tune reasonable AFRs in the fuel table.

 

I never got the idea that you want xx.x:1 AFR in every given situation under a certain load and RPM. If the car can handle a leaner AFR under a certain condition then that's likely what you want it to do as it will make more power and run more efficiently.

For example, lets say you have main fuel map tuned to run 11.0:1 AFR at 3.0 g/rev and 4000 RPM. You got to these values from 4th gear tuning and that's what it could handle while keeping the knock sensor happy. Now, you roll into the throttle at 2500 RPM in 2nd gear. 4000 RPM and 3.0 g/rev comes and the fuel map puts it at 11:1 AFR, as tuned. Yet, because the engine speed is accelerating much more quickly then it was in 4th, and there is not heat built up yet, you can get away with (and likely better off) leaning out the AFR under this condition because it will make more power and burn more efficiently.

I’m not arguing that LS works with the factory values on a heavily modified car. I highly doubt they are even close to ideal actually. I’m just wondering if tuning these maps may provide a car that’s more powerful and more efficient under more conditions then just WOT in 4th gear.

 

in theory LS sounds wonderful.

unfortunately the system as it stands now doesn't work like the theory.

therefore you are better off disabling it. IMHO

 

Come to think of it, maybe I'm better off disabling it again. It's just that transition area is a beast to tune.

 

Saying mitsu has the ECU tuned correctly from the factory is like saying a 9:1 AFR is optimum.

 

Actually, it probably is optimum for what they intended...a very safe tune that's still peppy.

Look at the AFRs stock, They actually sit in the mid/high 11s in the lower gears so it drives well and feels powerful. The car doesn't go really rich until it gets a lot of load and has the chance to build up heat.

I think lean spool could be a very good thing if it was well understood and tunable. Most standalones have this very same feature, they often refer to it as acceleration enrichment and the amount of enrichment is based on how quickly the engine speed is changing.

 

yeah I think you hit the nail on the head.

no-one really knows how it works (in our ECU) and thus no-one really knows how to tune it.

we have all gone the easy route - which is to disable it

 

how do i disable it?

 

It is easily done in the Periphery bits....

FBA bit 0 set to 0 will disable lean spool

 

be gentle
i don't see it in ecuflash ?

 

Sorry....didn't mean to come across as harsh. You will need to do a search for "Periphery Bit".

It is a mod done to the XML to allow you to control ECU test functions and all other ECU functions for that matter. Adjust at your own risk.

What rom ID are you running? If is it the same as mine I will post the Periphery bit mod for you. 94170015

 

i'm running 96260009 with tephra 5.1 mods

 

Sorry .....I had a stupid moment....

Periphery bits are the same for all EVO roms.

Paste the following into your XML

<table name="ECU Periphery00 Hex" category="Periphery" address="f9a" type="1D" level="2" scaling="Hex16"/>

<table name="ECU Periphery0 Hex" category="Periphery" address="faa" type="1D" level="2" scaling="Hex16"/>

<table name="ECU Periphery1 Hex" category="Periphery" address="fba" type="1D" level="2" scaling="Hex16"/>

<table name="ECU Periphery2 Hex" category="Periphery" address="fca" type="1D" level="2" scaling="Hex16"/>

<table name="ECU Periphery3 Hex" category="Periphery" address="fda" type="1D" level="2" scaling="Hex16"/>

<table name="ECU Periphery4 Hex" category="Periphery" address="fea" type="1D" level="2" scaling="Hex16"/>

<table name="ECU Periphery00 (F9A) Bits" category="Periphery" address="f9a" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>

<table name="ECU Periphery0 (FAA) Bits" category="Periphery" address="faa" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>

<table name="ECU Periphery1 (FBA) Bits" category="Periphery" address="fba" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>

<table name="ECU Periphery2 (FCA) Bits" category="Periphery" address="fca" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>

<table name="ECU Periphery3 (FDA) Bits" category="Periphery" address="fda" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>

<table name="ECU Periphery4 (FEA) Bits" category="Periphery" address="fea" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>

<table name="OBD-II Codes" category="OBD-II" type="3D" level="2" scaling="Hex16">
<table name="r4 (hex)" type="Static X Axis" elements="16" scaling="Hex16">
<data>8000</data>
<data>4000</data>
<data>2000</data>
<data>1000</data>
<data>800</data>
<data>400</data>
<data>200</data>
<data>100</data>
<data>80</data>
<data>40</data>
<data>20</data>
<data>10</data>
<data>8</data>
<data>4</data>
<data>2</data>
<data>1</data>
</table>
<table name="r5 (hex)" type="Static Y Axis" elements="13">
<data>00</data>
<data>01</data>
<data>02</data>
<data>03</data>
<data>04</data>
<data>05</data>
<data>06</data>
<data>07</data>
<data>08</data>
<data>09</data>
<data>0A</data>
<data>0B</data>
<data>0C</data>
<data>0D</data>
<data>0E</data>
<data>0F</data>
</table>
</table>

 

i see these now in ecuflash but its not quite right!
is there a " < " missing on the first line ?
and should there be a space between every table as there currently is in my xml?

 

Yeah...I made the correction. What you see above is correct.

Spaces between the tables mean nothing. It just makes the code take up more space