Green_Bandit's 16g build thread
I assume when you mean lean when starting you mean when its running.
The tables that keep the idle rich when its a cold engine are in 3 parts.
Maf compensation vs coolant temp is a general all around enrichment
Post cranking enrichment is just after starting to keep a nice rich idle while the o2 sensor warms up.
Post cranking enrichment decay is how long it enriches while the o2 sensor comes to life.
At least thats how i understand it there were a few threads by mr fred on evo's and fuel control which probably explain it in more detail.
RS - just an FYI on my xml this is what it said on the load and fuel limit cut:
<table name="Set to 9 to remove load limit" category="Miscellaneous" address="245da" type="1D" level="1" scaling="Hex16"/>
<table name="Set to 9 to remove fuel limit" category="Miscellaneous" address="246dc" type="1D" level="1" scaling="Hex16"/>
the address is different than the one you posted above.
<table name="Set to 9 to remove load limit" category="Miscellaneous" address="245da" type="1D" level="1" scaling="Hex16"/>
<table name="Set to 9 to remove fuel limit" category="Miscellaneous" address="246dc" type="1D" level="1" scaling="Hex16"/>
the address is different than the one you posted above.
RS - just an FYI on my xml this is what it said on the load and fuel limit cut:
<table name="Set to 9 to remove load limit" category="Miscellaneous" address="245da" type="1D" level="1" scaling="Hex16"/>
<table name="Set to 9 to remove fuel limit" category="Miscellaneous" address="246dc" type="1D" level="1" scaling="Hex16"/>
the address is different than the one you posted above.
<table name="Set to 9 to remove load limit" category="Miscellaneous" address="245da" type="1D" level="1" scaling="Hex16"/>
<table name="Set to 9 to remove fuel limit" category="Miscellaneous" address="246dc" type="1D" level="1" scaling="Hex16"/>
the address is different than the one you posted above.
Yes those are mean to be enabled when testing the ones i posted meaning with a value of 0x9
gotcha its just a number representing the value in ecuflash.
so I do this then right:
put this into the xml file
<table name="Set to 9 to remove fuel limit #2" category="Miscellaneous" address="246E4" type="1D" level="1" scaling="Hex16"/>
then go into ecuflash and under the word hex(value) put in 0xDA41 (replacing the 0009 that is there now on the "set to remove fuel limit" table) or is this going to make another table and I need to put 0xDA41 in that new table as the value??
so I do this then right:
put this into the xml file
<table name="Set to 9 to remove fuel limit #2" category="Miscellaneous" address="246E4" type="1D" level="1" scaling="Hex16"/>
then go into ecuflash and under the word hex(value) put in 0xDA41 (replacing the 0009 that is there now on the "set to remove fuel limit" table) or is this going to make another table and I need to put 0xDA41 in that new table as the value??
gotcha its just a number representing the value in ecuflash.
so I do this then right:
put this into the xml file
<table name="Set to 9 to remove fuel limit #2" category="Miscellaneous" address="246E4" type="1D" level="1" scaling="Hex16"/>
then go into ecuflash and under the word hex(value) put in 0xDA41 (replacing the 0009 that is there now on the "set to remove fuel limit" table) or is this going to make another table and I need to put 0xDA41 in that new table as the value??
so I do this then right:
put this into the xml file
<table name="Set to 9 to remove fuel limit #2" category="Miscellaneous" address="246E4" type="1D" level="1" scaling="Hex16"/>
then go into ecuflash and under the word hex(value) put in 0xDA41 (replacing the 0009 that is there now on the "set to remove fuel limit" table) or is this going to make another table and I need to put 0xDA41 in that new table as the value??
Add the lines he posted into your xml file, close it, save it, then open ecuflash and then your rom. Adjust the tables 1with at a time as long as the starting value roadspike posted matches.
Ok I have it in my rom and its ready to go, one last question:
The value in ecuflash for the path #3 (the one I put in the xml to try first) is the stock value that RS said. He said stock values should be 0x9, do I change the value in ecuflash to 0x9 or just leave it the way it comes up for that table.
The value in ecuflash for the path #3 (the one I put in the xml to try first) is the stock value that RS said. He said stock values should be 0x9, do I change the value in ecuflash to 0x9 or just leave it the way it comes up for that table.
What he means is, the stock value is listed as "Stock Value = *****", and he wants you to verify that the stock value he lists matches what you have. Once that is confirmed, then change the value to 0x9, then see if the fuel limit is removed by driving (carefully).
Path 1
Stock Value = 0x8B3B
<table name="Fuel Path Test 1" category="Miscellaneous" address="24668" type="1D" level="1" scaling="Hex16"/>
Path 2
Stock Value = 0x8935
<table name="Fuel Path Test 2" category="Miscellaneous" address="24674" type="1D" level="1" scaling="Hex16"/>
Path 3
Stock Value = 0x8903
<table name="Fuel Path Test 3" category="Miscellaneous" address="2467C" type="1D" level="1" scaling="Hex16"/>
You can add all three of the lines to your rom at once, and then just change the value for each one as you test....it'll llook like this in your xml
Path 1
Stock Value = 0x8B3B
<table name="Fuel Path Test 1" category="Miscellaneous" address="24668" type="1D" level="1" scaling="Hex16"/>
Path 2
Stock Value = 0x8935
<table name="Fuel Path Test 2" category="Miscellaneous" address="24674" type="1D" level="1" scaling="Hex16"/>
Path 3
Stock Value = 0x8903
<table name="Fuel Path Test 3" category="Miscellaneous" address="2467C" type="1D" level="1" scaling="Hex16"/>
You can add all three of the lines to your rom at once, and then just change the value for each one as you test....it'll llook like this in your xml
Code:
<table name="Fuel Path Test 1" category="Miscellaneous" address="24668" type="1D" level="1" scaling="Hex16"/> <table name="Fuel Path Test 2" category="Miscellaneous" address="24674" type="1D" level="1" scaling="Hex16"/> <table name="Fuel Path Test 3" category="Miscellaneous" address="2467C" type="1D" level="1" scaling="Hex16"/>
If you don't see a difference I think its probably best to leave it disabled and continuing to disable them until you have all 3 disabled. This will leave the 4th and default fuel path as the only option.
I'm leaving work now and will do the first path first and see if that works.






