TephraMod V7
Oct 11, 2009, 01:33 PM
#122
Dang, this thread blew up!
I think its a bad idea to do this all together. I believe doing this does not only disable the check, but disables the heater also. Someone else confirm if I am wrong... but if it does disable the heater it will destroy the rearO2 pretty quickly for those of us that still have it.
If you didn't know any better (and haven't set the emissions output correctly), it might also show a not-ready for that during an emissions test. It might be best to just leave this one alone, or include the definition but leave it stock.
Might I suggest adding the rear O2 sensor heater disable to this patch as well?
Open up the ROM, navigate to the "Mods" section, change "Rear O2 Heater Patch" from "4A0B" to "0009"
My rear O2 has been replaced with the wideband.
This might also work but I need to confirm the address!
Code:
<table name="Rear O2 Heater Patch" category="Mods" address="2c62a" type="1D" scaling="Hex16"/>
My rear O2 has been replaced with the wideband.
This might also work but I need to confirm the address!
Code:
<table name="Heater CEL" category="Rear O2" address="2c61e" type="2D" level="2" scaling="blobbits"> <table name="Bit values" type="Static Y Axis" flipy="true" elements="8"> <data>N/A</data> <data>N/A</data> <data>N/A</data> <data>N/A</data> <data>Rear O2 Heater CEL Enable</data> <data>N/A</data> <data>N/A</data> <data>N/A</data> </table> </table>
If you didn't know any better (and haven't set the emissions output correctly), it might also show a not-ready for that during an emissions test. It might be best to just leave this one alone, or include the definition but leave it stock.
Oct 11, 2009, 01:40 PM
#123
Dang, this thread blew up!
I think its a bad idea to do this all together. I believe doing this does not only disable the check, but disables the heater also. Someone else confirm if I am wrong... but if it does disable the heater it will destroy the rearO2 pretty quickly for those of us that still have it.
If you didn't know any better (and haven't set the emissions output correctly), it might also show a not-ready for that during an emissions test. It might be best to just leave this one alone, or include the definition but leave it stock.
I think its a bad idea to do this all together. I believe doing this does not only disable the check, but disables the heater also. Someone else confirm if I am wrong... but if it does disable the heater it will destroy the rearO2 pretty quickly for those of us that still have it.
If you didn't know any better (and haven't set the emissions output correctly), it might also show a not-ready for that during an emissions test. It might be best to just leave this one alone, or include the definition but leave it stock.
Oct 11, 2009, 01:42 PM
#124
Evolving Member
Join Date: Sep 2009
Location: Creston, Iowa
Posts: 123
Likes: 0
Received 0 Likes
on
0 Posts
What I think Chris meant is, from the factory, the boost control is load based. However, the load value the boost control system uses is SLIGHTLY different from the load value the timing/fuel maps use. This is what he is referring to as the "stock" boost control system.
This was later patched to reference the same load value that the timing/fuel maps use. This is what he is referring to as the "2 byte" boost control system. Although that's a bit misleading/incorrect. What he should have said is the "common load"or "standard load" boost control system. But yes, the values of this "common load" does match up with what we all came to know as "2 byte load" and that's the point.
As far as 2 byte vs. 1 byte... the difference is only for logging. They both reference the same value, as far as the ECU is concerned for the various maps and for the actual tune. 1 byte exists as a logging improvement only.
This was later patched to reference the same load value that the timing/fuel maps use. This is what he is referring to as the "2 byte" boost control system. Although that's a bit misleading/incorrect. What he should have said is the "common load"or "standard load" boost control system. But yes, the values of this "common load" does match up with what we all came to know as "2 byte load" and that's the point.
As far as 2 byte vs. 1 byte... the difference is only for logging. They both reference the same value, as far as the ECU is concerned for the various maps and for the actual tune. 1 byte exists as a logging improvement only.
Thanks
Oct 11, 2009, 03:29 PM
#128
Evolving Member
Join Date: Sep 2009
Location: Creston, Iowa
Posts: 123
Likes: 0
Received 0 Likes
on
0 Posts
Oct 11, 2009, 06:38 PM
#133
Will it be possible to include Mr Fred' temperature logging on version 7.1?
Having the V.7 + EGT logs will be the best rom ever for me!!!
Thanx Tephra for your great work! Will donate with 88590015' release ;-)
Cheers
C>
Having the V.7 + EGT logs will be the best rom ever for me!!!
Thanx Tephra for your great work! Will donate with 88590015' release ;-)
Cheers
C>
Oct 11, 2009, 06:52 PM
#134
Just a thought for an add-in, might want to include the MAP sensor tables that can be adjusted for different map sensor types for logging in Evoscan. With the Omni 4 bar being a very viable option I'm sure you'll see quite a few more people using them compared to a stock Evo X type.
Oct 11, 2009, 08:25 PM
#135
Account Disabled
iTrader: (8)
Join Date: Sep 2007
Location: Hayward
Posts: 3,366
Likes: 0
Received 0 Likes
on
0 Posts
Tephra you rock! 
You have paypal.
Does boost drop on knock go to 0% WGDC without BDEL correction applied? Is "High Knock Boost Drop and Knock CEL Flash time" the time that 0% WGDC is applied, then after that has elapsed it references WGDC map again?
- Bryan
You have paypal.
Does boost drop on knock go to 0% WGDC without BDEL correction applied? Is "High Knock Boost Drop and Knock CEL Flash time" the time that 0% WGDC is applied, then after that has elapsed it references WGDC map again?
- Bryan
Last edited by GST Motorsports; Oct 11, 2009 at 08:28 PM.