PATCH: TephraMod V5
#406
Evolving Member
yes - that was the "functionality test" so all the tables were the same (even the alt maps) to my unpatched version of the ROM. When I get back home I will post the graph. The spike was about 0.1 bar (1.7 bar) above what it used to be (1.6 bar). It was corrected within 0.2 sec. I was never spiking over 1.7 - so that is why I got focused on that.
#407
mmm, the only thing I can think of is load changes or temp changes.
ie going up a hill you will generate different boost vs flat ground
also
cooler temp will generate more boost than hotter temps...
I'm not saying your wrong, just I don't think there could be an issue, be glad to look at logs thou
ie going up a hill you will generate different boost vs flat ground
also
cooler temp will generate more boost than hotter temps...
I'm not saying your wrong, just I don't think there could be an issue, be glad to look at logs thou
#408
Evolving Member
Join Date: May 2007
Location: Edinburgh, UK
Posts: 121
Likes: 0
Received 0 Likes
on
0 Posts
Just finally had time to try the 5.1 - anyone observed this behaviour (96530006 with 5.1):
in both - normal and alt maps - with wot 3rd gear up to 6000rpm then change gear quickly to 4th (without NLTS) - the boost spikes when the load goes up when the 4th gear engages and wot again - of course then boost comes down (correction) - but could this be becasue the whole procedure (patch) is slowing down the timer/cycle - so it takes a little bit longer for all adjustment that the ECU is doing (on boos it is moost visible) but maybe timing/fueling gets slightly delayed as well. I can cure the boost spike by closely macthing the WGDC etc. - but this was not happening on a normal version of the ROM.
Not really an issue - but just lets me think about how much processor time is "lost" going through the whole routine and whether this doesnot affect some other time/cycle dependent performance.
in both - normal and alt maps - with wot 3rd gear up to 6000rpm then change gear quickly to 4th (without NLTS) - the boost spikes when the load goes up when the 4th gear engages and wot again - of course then boost comes down (correction) - but could this be becasue the whole procedure (patch) is slowing down the timer/cycle - so it takes a little bit longer for all adjustment that the ECU is doing (on boos it is moost visible) but maybe timing/fueling gets slightly delayed as well. I can cure the boost spike by closely macthing the WGDC etc. - but this was not happening on a normal version of the ROM.
Not really an issue - but just lets me think about how much processor time is "lost" going through the whole routine and whether this doesnot affect some other time/cycle dependent performance.
#410
Dave, any chance of John Banks ROMID soon, I am happy to bribe you with more donations!
edited because reading back it says be patient, ok, I'll be patient, but I'm not editing it now that I puit the effort into asking.
Sohail,
Both John and I use the ATS to very good effect, i suggest you try it. Most welcome to look at mine when we meet up to install Dave's new patch!
edited because reading back it says be patient, ok, I'll be patient, but I'm not editing it now that I puit the effort into asking.
Sohail,
Both John and I use the ATS to very good effect, i suggest you try it. Most welcome to look at mine when we meet up to install Dave's new patch!
Last edited by Adamantium; Apr 10, 2008 at 04:27 AM.
#414
Evolved Member
iTrader: (26)
Join Date: Oct 2007
Location: Colorado Springs, CO
Posts: 1,989
Likes: 0
Received 0 Likes
on
0 Posts
Another question..
1) I had the Rear o2 sim xml in my file before I did the V5. Do I need to delete this XML since V5 automatically has it in there via an enable/disable option?
See Below:
1) I had the Rear o2 sim xml in my file before I did the V5. Do I need to delete this XML since V5 automatically has it in there via an enable/disable option?
See Below:
Code:
<table name="Rear 02 Sim Hook" category="Rear_02" address="c250" type="3D" level="1" scaling="Hex16"> <table name="Code" type="Static X Axis" elements="1" scaling="Hex16"> <data>Hex16</data> </table> <table name="Address" type="Static Y Axis" elements="10"> <data>C250</data> <data>C252</data> <data>C254</data> <data>C256</data> <data>C258</data> <data>C25A</data> <data>C25C</data> <data>C25E</data> <data>C260</data> <data>C262</data> </table> </table> <table name="Rear 02 Sim Subroutine" category="Rear_02" address="4a000" type="3D" level="1" scaling="Hex16"> <table name="Code" type="Static X Axis" elements="1" scaling="Hex16"> <data>Hex16</data> </table> <table name="Address" type="Static Y Axis" elements="20"> <data>4A000</data> <data>4A002</data> <data>4A004</data> <data>4A006</data> <data>4A008</data> <data>4A00A</data> <data>4A00C</data> <data>4A00E</data> <data>4A010</data> <data>4A012</data> <data>4A014</data> <data>4A016</data> <data>4A018</data> <data>4A01A</data> <data>4A01C</data> <data>4A01E</data> <data>4A020</data> <data>4A022</data> <data>4A024</data> <data>4A026</data> </table> </table>