LEAN SPOOL question
Jan 30, 2009, 02:20 PM
#16
Thats why the Evo 10 is such a slow car.
Lean spool not only brings the AFRs into optimal values (momentarily), it brings them into better values than it's possible without lean spool.
Because you cannot drive so high AFR only set by the fuel-table over the whole RPM-band. Means if you would hard drive your car on the german Highway (no speed limit), you can wait until your engine gets a little warm 'cause of running consantly high AFR values.
With the Lean spool tables you can drive your engine for example from 2000 - 6500RPM with a AFR value of around 12.5. And before the the engine becomes to hot the Lean spool is switching off to prevent a damage.
Lean spool not only brings the AFRs into optimal values (momentarily), it brings them into better values than it's possible without lean spool.
Because you cannot drive so high AFR only set by the fuel-table over the whole RPM-band. Means if you would hard drive your car on the german Highway (no speed limit), you can wait until your engine gets a little warm 'cause of running consantly high AFR values.
With the Lean spool tables you can drive your engine for example from 2000 - 6500RPM with a AFR value of around 12.5. And before the the engine becomes to hot the Lean spool is switching off to prevent a damage.
Jan 30, 2009, 02:58 PM
#17
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.
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.
Mar 2, 2009, 09:48 PM
#21
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.
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.
Mar 3, 2009, 08:32 AM
#26
Evolved Member
iTrader: (22)
Join Date: Nov 2003
Location: Northern KY near Cincy
Posts: 2,408
Likes: 0
Received 6 Likes
on
6 Posts
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
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
Mar 3, 2009, 08:37 AM
#28
Evolved Member
iTrader: (22)
Join Date: Nov 2003
Location: Northern KY near Cincy
Posts: 2,408
Likes: 0
Received 6 Likes
on
6 Posts
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>
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>
Last edited by Appauldd; Mar 3, 2009 at 08:37 AM. Reason: error correction
Mar 3, 2009, 08:45 AM
#29
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?
is there a " < " missing on the first line ?
and should there be a space between every table as there currently is in my xml?
Mar 3, 2009, 08:48 AM
#30