TephraMOD V5.8 - testing help required
Jun 16, 2008, 08:53 PM
#31
I was just speaking in general, still running 5.0 so far 
I'm slightly concerned about the map averaging related to overshoot... but hopefully lowering to update intervals of 1 will help balance everything out. I like things smoothed, but I'm slightly concerned about overshoot with S1 cams and a stock turbo. In any case, I'm still much better off with ecu controlled boost than I was with the Tru-boost
edit: LOL I now notice your sig also
I'm slightly concerned about the map averaging related to overshoot... but hopefully lowering to update intervals of 1 will help balance everything out. I like things smoothed, but I'm slightly concerned about overshoot with S1 cams and a stock turbo. In any case, I'm still much better off with ecu controlled boost than I was with the Tru-boost
edit: LOL I now notice your sig also
Last edited by fostytou; Jun 16, 2008 at 09:21 PM.
Jun 17, 2008, 08:57 AM
#33
Evolved Member
iTrader: (19)
Join Date: Aug 2007
Location: NJ
Posts: 801
Likes: 0
Received 0 Likes
on
0 Posts
how do you reverse these patches on ECU Flash once it's on there? I did one of your patches but don't have the confidence to mess with the no lift shift...vale..etc.
Jun 17, 2008, 05:16 PM
#37
notes:
* avg map replaces the original variable - if you want to log the original please log 0xFFFF8417
* ditto for the rear 02, so log 0xFFFF8409 for the real variable
* 0xFFFF840B has the 2byte->1byte variable so log that and then in evoscan multiple the "x" by whatever factor, ie by default use Eval="1.2*x"
* avg map replaces the original variable - if you want to log the original please log 0xFFFF8417
* ditto for the rear 02, so log 0xFFFF8409 for the real variable
* 0xFFFF840B has the 2byte->1byte variable so log that and then in evoscan multiple the "x" by whatever factor, ie by default use Eval="1.2*x"
Sorry man, I'm blind I guess.
Jun 17, 2008, 08:23 PM
#39
log 0xFFFF840B (or just 0x840B if you are editing only the last part of the MUT entry.)
so pick an unused MUTID, I like 0x40, and stick 0x840B in there, then log MUT40 in evoscan and use the formula that I said above).
What loads are you seeing normally?
so pick an unused MUTID, I like 0x40, and stick 0x840B in there, then log MUT40 in evoscan and use the formula that I said above).
What loads are you seeing normally?
Jun 17, 2008, 08:42 PM
#40
OK I have put 94170015 on the first post.
I will wait for these two ROMS to be tested.
Please test all the current features - especially those in the changelog in post #1.
again usual precautions must be followed these are all untested
I will wait for these two ROMS to be tested.
Please test all the current features - especially those in the changelog in post #1.
again usual precautions must be followed these are all untested
Jun 24, 2008, 11:29 AM
#43
Sorry Dave I havent had much time to give feedback on 5.8. But I will upload it tonight and see what I can get done to give good feedback. Because of how I have my xml setup so I can use the same version of ECUflash to tune my car and customers it takes me awhile to switch things around
anyway enough excuses and I will try to get results
aaron
anyway enough excuses and I will try to get results
aaron
Jun 24, 2008, 05:15 PM
#45
Evolving Member
Join Date: Apr 2008
Location: New Zealand
Posts: 462
Likes: 0
Received 0 Likes
on
0 Posts
