PATCH: TephraMod V5
Apr 9, 2008, 03:18 PM
#392
Evolved Member
iTrader: (26)
Join Date: Oct 2007
Location: Colorado Springs, CO
Posts: 1,989
Likes: 0
Received 0 Likes
on
0 Posts
I am currently working on transferring my tuned maps over to the new V5. I just want to ensure that I am doing this right.
According the readme file from Tephra, it said to delete the Hi/Lo Octane fuel map. Now I lost my ability to input my hi/lo fuel maps into the new version. Where does this fuel map go now in V5?
I currently have the Alternate map function disabled. I just want to be able to run V5 without having to mess with the alternate map settings yet.
Can anyone tell me where to place my base fuel maps?
Thanks!
Cheers-
E
According the readme file from Tephra, it said to delete the Hi/Lo Octane fuel map. Now I lost my ability to input my hi/lo fuel maps into the new version. Where does this fuel map go now in V5?
I currently have the Alternate map function disabled. I just want to be able to run V5 without having to mess with the alternate map settings yet.
Can anyone tell me where to place my base fuel maps?
Thanks!
Cheers-
E
Apr 9, 2008, 04:50 PM
#395
Newbie
Join Date: Nov 2005
Location: Sydney, Australia
Posts: 40
Likes: 0
Received 0 Likes
on
0 Posts
Question and suggestion perhaps Dave ...
Suggestion: Was thinking if you can make NTLS enabled when ALT Maps gets enabled? dont know about others but when driving round town day to day i dont like using NTLS and on the ocasion like to have a bit of a hit and forget about NTLS and the car goes jerk jerk
so was thinking NTLS is more so for going quick and I supose you would want to use it with your QUICK (alt) map so perhaps enable them together? or maybe have a switch to say Enable NTLS with alt map?
Question: Since removing the 2nd 3rd etc Boost / Wastegate / Octane maps what effect does this have? as in what were these maps previously used for? and is there any impact that they arent there anymore? I'm guessing its when the ecu detected defferent octane levels it would use the appropriate map but just want to check and be sure that not having them isnt a drama? sorry if they are n00b questions but I guess thats how we learn... THHHANNNKS!
Suggestion: Was thinking if you can make NTLS enabled when ALT Maps gets enabled? dont know about others but when driving round town day to day i dont like using NTLS and on the ocasion like to have a bit of a hit and forget about NTLS and the car goes jerk jerk
so was thinking NTLS is more so for going quick and I supose you would want to use it with your QUICK (alt) map so perhaps enable them together? or maybe have a switch to say Enable NTLS with alt map?Question: Since removing the 2nd 3rd etc Boost / Wastegate / Octane maps what effect does this have? as in what were these maps previously used for? and is there any impact that they arent there anymore? I'm guessing its when the ecu detected defferent octane levels it would use the appropriate map but just want to check and be sure that not having them isnt a drama? sorry if they are n00b questions but I guess thats how we learn...
THHHANNNKS!
Apr 9, 2008, 06:57 PM
#397
kayman - the #2 #3 and #4 maps have been placed by a single #1, the code has been modified to use #1 in all scenarios - most people would set #1, #2, #3 to the same thing anyways... just makes tuning quicker
wickedE - alt MIVEC was considered, but apparently 1 MIVEC map suits all situations, so it was decided not to bother
wickedE - alt MIVEC was considered, but apparently 1 MIVEC map suits all situations, so it was decided not to bother
Apr 9, 2008, 08:21 PM
#401
I thought #1 was warm up, #2 was normal and #3 was limp home mode.
It is still useful to have a #1 and #3 and make them conservative for when the engine is cold, and when knocks limping home (if that ever happens)
It is still useful to have a #1 and #3 and make them conservative for when the engine is cold, and when knocks limping home (if that ever happens)
kayman - the #2 #3 and #4 maps have been placed by a single #1, the code has been modified to use #1 in all scenarios - most people would set #1, #2, #3 to the same thing anyways... just makes tuning quicker
wickedE - alt MIVEC was considered, but apparently 1 MIVEC map suits all situations, so it was decided not to bother
wickedE - alt MIVEC was considered, but apparently 1 MIVEC map suits all situations, so it was decided not to bother
Apr 9, 2008, 11:38 PM
#403
ok for timing 1,2 and 3 are all used - currently the belief is 2 is used most of the time, 1 and 3 are used when MIVEC isn't on target...
for boost 2 and 3 (and 4 if you have it defined) are used for conditions that are never met.
hence the decision was made to reduce confusion and remove these maps!
for boost 2 and 3 (and 4 if you have it defined) are used for conditions that are never met.
hence the decision was made to reduce confusion and remove these maps!
Apr 10, 2008, 12:25 AM
#404
Evolving Member
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.
Last edited by evo828; Apr 10, 2008 at 12:33 AM.