TephraMod V7
just a quick q on scaling the maf on the big maps. do you scale the "airflow/hz raw scaling" table in fuel tab, under immobilizer options or the "maf scaling (maf adder already added)" in the global fuel settings tab? as one is units and the other is g/s.
Mike
Mike
i really feel that these threads and mods should be for tuners only. for people like me (new to EVOs), there is just too much to learn and too much knowledge to be known BEFORE attempting any of this.
only the time i've spent tuning other cars has helped me even come CLOSE to understanding all this stuff. as mentioned before, i'm sticking with ver 5.x because i FINALLY have a grasp of how it works. ver 7.x has WAY more stuff than i know what to deal with. if i ever go to a formal tuner and they want to use ver 7, then fine. i'll let them make the adjustments and i won't TOUCH them. too many "well, if you change this, then you have to change these too", etc. i get lost.
but for now, ver 5 does all i need.
Same here whats with this ?? address is 3e252 for scaling in def it says (none)
although that doesnt effect my perception of power, the log shows a big zig zag from high to low in wddc.
I just lowered that input from 150 because I believe it is overriding the percent throttle map.
I made use of the Big Map Translator spreadsheet to convert my timing values over to the big maps, and they look spot on compared to my small maps.
But I am seeing the same problem as Boosted GP when logging timing during a WOT 3rd gear pull.
Up to load 110 or so, the timing values are pretty much spot on, thereafter the logged values are reading 3-5 degree's higher that what is in the ignition map. This continues right up till red line.
Timing fuelling and boost are spot on to what I use to log with the small maps, it is only the timing which seems to be off.
When I get my laptop back, I can post up the map tracer/logs and ROM file if needed.
Does anyone else have the same issue and is there a fix for it?
Thx.
Does anyone have a fix for this?
Last edited by SeanV; Nov 16, 2009 at 05:53 AM.
does this happen only during accelerations? if so perhaps the math used by the processor is rigged to the original map. Since we are seeing view points the ecu doesn't recognize there may be inconsistencies. Then once the dramatic acceleration is done the ecu can use the new timing from the new larger map.
It is very possible that you are just bouncing around between min load for boost control, 100% wgdc under this load, and the 0% or whatever is in your maps. When I had the 100% wgdc under this load option set too high I could get a bit of oscillation.
Log wgdc and see if it is going 0-100-0% or something similar as you oscillate
I am going to try 9653 Opt 4 on my 04 Evo 8. I notice that the gear dependant boost is set up for 6 gear Evos. My car is 5 speed. What do I do with the 6th gear. Ignore it? Will it work oin 5 sp Evos. I believe I also saw a 0 gear on the tables.
zero them out or fill them in, as long as you have the correct numbers in 1 through 5.
the correct numbers are in here someplace,,, I had to search for them last week. try a search in the ecuflash forum or even in this thread.
the correct numbers are in here someplace,,, I had to search for them last week. try a search in the ecuflash forum or even in this thread.
1) Made the "0" columns in both the BDEL, WGDC equal the "1" column
2) Made 0 and 1 rows in the "RPM/Speed to Gear" tables equal the same values
I'm not sure which table did it, but it works nicely now.
Last edited by D-VO; Nov 16, 2009 at 06:34 PM.
The big zig zag wont deliver smooth torque curve. More than that it makes the car feel jerky under constant part-throttle, isn't it? Actually that is what I have and I consider it to be a problem.
What nothere said.^^
It is very possible that you are just bouncing around between min load for boost control, 100% wgdc under this load, and the 0% or whatever is in your maps. When I had the 100% wgdc under this load option set too high I could get a bit of oscillation.
Log wgdc and see if it is going 0-100-0% or something similar as you oscillate
It is very possible that you are just bouncing around between min load for boost control, 100% wgdc under this load, and the 0% or whatever is in your maps. When I had the 100% wgdc under this load option set too high I could get a bit of oscillation.
Log wgdc and see if it is going 0-100-0% or something similar as you oscillate
By the way, what does min load for boost control table define? And what is WGDC=100% under this Load scaling, what does 200% mean is it equal to 200 load?
Last edited by Biggy VIII; Nov 16, 2009 at 10:33 PM.
Hey just to let you know, I was having a problem when using gear dependent boost control and launch control maps at the same time. When launching, there was no boost control in 1st gear at all. I was able to rectify the issues by making the following changes:
1) Made the "0" columns in both the BDEL, WGDC equal the "1" column
2) Made 0 and 1 rows in the "RPM/Speed to Gear" tables equal the same values
I'm not sure which table did it, but it works nicely now.
1) Made the "0" columns in both the BDEL, WGDC equal the "1" column
2) Made 0 and 1 rows in the "RPM/Speed to Gear" tables equal the same values
I'm not sure which table did it, but it works nicely now.
WGDC=100% under this Load is 200... that is ~1bar of boost, right? I am not trying to make my boost any lower than 1bar under part-throttle.
The big zig zag wont deliver smooth torque curve. More than that it makes the car feel jerky under constant part-throttle, isn't it? Actually that is what I have and I consider it to be a problem.
Ok I will log wgdc with my current WGDC=100% under this Load setting, and than lower it to say 100.
By the way, what does min load for boost control table define? And what is WGDC=100% under this Load scaling, what does 200% mean is it equal to 200 load?
The big zig zag wont deliver smooth torque curve. More than that it makes the car feel jerky under constant part-throttle, isn't it? Actually that is what I have and I consider it to be a problem.
Ok I will log wgdc with my current WGDC=100% under this Load setting, and than lower it to say 100.
By the way, what does min load for boost control table define? And what is WGDC=100% under this Load scaling, what does 200% mean is it equal to 200 load?
Your BCS will not do anything up to that load point, then it will activate (and if set over this load go to 100% else go to defined boost control). Load is deliniated with a % symbol everywhere in the program, so yes... 200% means 200 load.








