When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I wanted to post this just to make sure we are on the same page. I am using the XML code from page 1 of this thread, which I have included below and the Rear 02 Simulator is disabled (0) within the Tephra MOD options. mrfred provided an EXCEL file showing what updated HEX values to use with the new tables, which I have attached. The other values not provided by mrfred that I am using are shown below. I am using the PLX wideband that is scaled from 10-20 AFR.
The new HEX values used in the tables were provided by mrfred in the attached EXCEL file.
Some time ago I attempted to apply this patch to my rom (evo 9), followed the instructions above changing the values/addresses for the new tables in the rom and I was unable to get it to work. I ended up giving up on it so I scrapped the modified xml and rom with the patch and went back to a stock evo 9 88590015 xml and rom. Later I realized I couldn't get it to work because my mut table was messed up (mut table is now fixed) so the addresses used by the patch didn't match up with the mut table.
My question is this: If I flashed my ecu with the xml and rom containing this patch (new values/addresses in new tables for the patch), then flashed it back to a stock 88590015 xml and rom, do the previous changes made to those patch tables in the rom still exist in the ecu even though I no longer see the patch tables defined since I removed the patch from the xml file? Do I need to change the values/addresses in the new patch tables back to stock values/addresses before removing the patch and flashing back to a stock xml and rom?
Some time ago I attempted to apply this patch to my rom (evo 9), followed the instructions above changing the values/addresses for the new tables in the rom and I was unable to get it to work. I ended up giving up on it so I scrapped the modified xml and rom with the patch and went back to a stock evo 9 88590015 xml and rom. Later I realized I couldn't get it to work because my mut table was messed up (mut table is now fixed) so the addresses used by the patch didn't match up with the mut table.
My question is this: If I flashed my ecu with the xml and rom containing this patch (new values/addresses in new tables for the patch), then flashed it back to a stock 88590015 xml and rom, do the previous changes made to those patch tables in the rom still exist in the ecu even though I no longer see the patch tables defined since I removed the patch from the xml file? Do I need to change the values/addresses in the new patch tables back to stock values/addresses before removing the patch and flashing back to a stock xml and rom?
what flew where ??? how did you spoil the mut and at the same time log something ???
take a clean bin and apply a patch, then tweak.
short instruction change - "Front O2 (ADC 04) RAM variable" to 6A6E change - "Rear O2 (ADC 0A) RAM variable" to 6A6C
change - "MUT12 Value (To Read Wideband)"to 6A6D ( if you want log wb by MUT12) set: Closed Loop Wideband On/Off to 1 Cold Engine Closed Loop AFR to 14.7 Min Coolant Temp To Use AFR Table to 70
calc and set: "Wideband AFR Correlation 1/mL Value", for LC-1 1/mL = 31.9 "Wideband AFR Correlation bL/mL Value", for LC-1 bL/mL = 289 "AFR Table Multiplier High Word" (try set 3) and "AFR Table Multiplier Low Word" (try set 0xACCD) or set "modern AFR Table Multiplier" to 1
Originally Posted by Dow Jhob
AFR map multiplier wrong
because of this, the simulated signal is always to rail..
part3 wrong (incomplete)
how you like the complexity, my patch is made on the basis of the same Excel, I have attached instructions, everything is done in a dozen clicks
I greatly appreciate your help and it appears your updated patch is now working. I performed the setup per your instructions, but because my Wideband is 10-20AFR I used different values. "Wideband AFR Correlation 1/mL Value", (10-20 AFR) 1/mL = 25.5 "Wideband AFR Correlation bL/mL Value", (10-20 AFR) bL/mL = 255
I also disabled (0) the "Rear O2 Simulator" in the "Tephra Mod Options" table.
To test the patch I logged the simulated narrowband O2 Sensor volts (mut13) as a function of the wideband AFR (mut12=0x6A6D), which was set to 14.7:1 in the High Octane Fuel Map. As you can see from the graph below the ECU is targeting 14.7:1.
I next changed the High Octane Fuel map to target 15.6:1 AFR and subsequently logged the simulated narrowband O2 Sensor volts (0-1v) as a function of the wideband AFR. As you can see from the graph below the ECU is targeting 15.6:1.
Your patch appears to work as intended so I would like to say thank you for all of your help. For those with the TephraMOD-88590715-v7 ROM this simplified patch should resolve your problems. I like that your patch automatically populates the new HEX values when turned on, which makes this much easier to implement. I will update if I run into any issues, but I plan to run this full time as of today.
Curious, have you implemented any tuning strategies to simplify tuning the ISCV tables for idle? There are many different idle tables accessed by the ECU so it can be difficult determine what table to tune. My car will idle rock solid, but will sometimes randomly rev up to 2500rpm for some unknown reason. Is there a way to have the ECU tell you which map is being used at that time or a way to eliminate some of the maps from being used? Curious to hear your thoughts about this. Again, thank you for all of your help.
idle speed is destabilized either due to malfunction or humped camshafts,
if your cmshfts stocks check yor idle valve a typical problem is the wear
of the guide grooves, in fact, replacement, or air leaks, in all other cases
the idle is rooted to the spot, it is also a typical mistake to try to deplete
the idle below 1 to 14
if version 2.0 then we will extend the patch for the very lazy
Last edited by Dow Jhob; Dec 22, 2021 at 01:06 PM.
idle speed is destabilized either due to malfunction or humped camshafts,
if your cmshfts stocks check yor idle valve a typical problem is the wear
of the guide grooves, in fact, replacement, or air leaks, in all other cases
the idle is rooted to the spot, it is also a typical mistake to try to deplete
the idle below 1 to 14
if version 2.0 then we will extend the patch for the very lazy
Thank you again for all of your help and you clearly have programming skills. I saved the file as v2 because you added 2 lines of code vs the original version I downloaded.
Regarding the idle, I do run larger GSC R2 cams with significant lift and duration. Additionally, have the original IACV from 2006 so perhaps I simply need to replace with a new one. BTW, what do you mean by this comment, "the idle is rooted to the spot, it is also a typical mistake to try to deplete the idle below 1 to 14." Are you referring to the % Demand?
for large cam set idle afr to 13 maybe 12-11.5
when I had a Honda with buddyclub5 camshafts so there idle I had to put 10
Thanks for the explanation and I'll try 13:1 at idle along with a new IACV. Idle stability at 14.7:1 is good at 980rpm with no load (AC, alternator, or Power Steering). However, when load is applied (AC, alternator, power steering) the idle stability becomes randomly inconsistent.
I was able to apply the latest v2 MrFred patch (that DowJHob put together) and all seems to work. Thank you very much MrFred and DowJHob for all your awesome work!
I did have a different value in the MUT12 table and the "var patch" in my Recompile Tephra v7 original but modified it to make the patch "match". At address C2BA was 0x6A64FFFF8408 instead of 0x6A64FFFF6A68. And MUT12 was set to 0x8408... I am guess this was to read the rear O2 input voltage for the wideband. My notes are horrible from 9 years ago when I setup tephra... So best I can tell.
Thanks again!
Last edited by dingus; Mar 11, 2022 at 04:05 PM.
Reason: credit where credit is due...
