What happens at peak load?
Currently I have leanspool disabled...Is there any other table that needed to be altered when disabling leanspool? At first I did it the old way of defining the leanspool tables and setting both start/stop to 1500. Then I changed it via the periphery bits way which totally disables it (I also made sure to set the start/stop back to their original settings) I just feel like I'm missing something here...
Raas -- A few quick questions: (1) Did you smooth the AFR and Timing maps (timing changes will change AFR readings), (2) What do your Low and Fuel maps look like as (the ecu will interpolate if there is knock -- I can't recall if you were knocking in this area), and (3) what is your load cutoff set to -- i am 99.999% positive this is not the issue, I just want to be sure....
OK I went back to post#5 and it looks like your AFR drops from 11.6 to 11 around 4K and then back....I could not find the 10 afr in the 3500 area like the first post stated -- maybe I am blind. That said, I see why the change is happening around 4K
...
OK I went back to post#5 and it looks like your AFR drops from 11.6 to 11 around 4K and then back....I could not find the 10 afr in the 3500 area like the first post stated -- maybe I am blind. That said, I see why the change is happening around 4K
...
Last edited by cij911; Jun 12, 2009 at 06:34 AM.
Raas -- A few quick questions: (1) Did you smooth the AFR and Timing maps (timing changes will change AFR readings), (2) What do your Low and Fuel maps look like as (the ecu will interpolate if there is knock -- I can't recall if you were knocking in this area), and (3) what is your load cutoff set to -- i am 99.999% positive this is not the issue, I just want to be sure....
OK I went back to post#5 and it looks like your AFR drops from 11.6 to 11 around 4K and then back....I could not find the 10 afr in the 3500 area like the first post stated -- maybe I am blind. That said, I see why the change is happening around 4K...
OK I went back to post#5 and it looks like your AFR drops from 11.6 to 11 around 4K and then back....I could not find the 10 afr in the 3500 area like the first post stated -- maybe I am blind. That said, I see why the change is happening around 4K
...Raas -- A few quick questions: (1) Did you smooth the AFR and Timing maps (timing changes will change AFR readings), (2) What do your Low and Fuel maps look like as (the ecu will interpolate if there is knock -- I can't recall if you were knocking in this area), and (3) what is your load cutoff set to -- i am 99.999% positive this is not the issue, I just want to be sure....
OK I went back to post#5 and it looks like your AFR drops from 11.6 to 11 around 4K and then back....I could not find the 10 afr in the 3500 area like the first post stated -- maybe I am blind. That said, I see why the change is happening around 4K...
OK I went back to post#5 and it looks like your AFR drops from 11.6 to 11 around 4K and then back....I could not find the 10 afr in the 3500 area like the first post stated -- maybe I am blind. That said, I see why the change is happening around 4K
...1) Yes I did smooth both maps as best I could...on the timing map I try not to go more than 2 degrees between cells and the fuel map is pretty smooth with the exception of the area in question.
2) For the low octane maps (both fuel and ignition) I just took their high octane counterparts and adjusted from them...for the ignition I just copied the high octane and took out about 3 degrees across the board, and for the fuel I did the same and added about .5 point across the board. And no, I wasn't knocking in these areas.
3) My boost cut, even though its not recommended, is set at the maximum of 319% so I too don't think this is the problem
Oh sorry about that, the log I posted was just one of the many showing the problem...I had dozens of logs and I just picked one, but there are instances where it has gone as rich as 10.x around that area...
If you don't mind sharing, what's causing this??
Raas -- You know I am more than willing to help ...First a few observations -- the two logs you posted are very different (were any tune changes made in between?) -- look at load, timing , and AFR. Also, I believe you are looking at the wrong cells (based on what you highlighted). The two logs showed a difference of ~10 load and 2 * of timing at ~3800.
If you send me your current logs and tune, I'll take a look -- it is very hard to keep going back to different posts....
...First a few observations -- the two logs you posted are very different (were any tune changes made in between?) -- look at load, timing , and AFR. Also, I believe you are looking at the wrong cells (based on what you highlighted). The two logs showed a difference of ~10 load and 2 * of timing at ~3800.If you send me your current logs and tune, I'll take a look -- it is very hard to keep going back to different posts
....
Last edited by cij911; Jun 13, 2009 at 08:14 AM.
cij, thanks for helping out. Yes many changes were made between runs trying to straighten out the rich dip that's why the 2 logs I posted look a little different, but they both show the same problem (even though they are not at the same exact rpm)
Oh no, if you are referring to post #5 where I have that 3000rpm 260-330 load highlighted that was not directly related to the problem area...that was just me smoothing out the table from some changes I made (I just happened to hit the printscreen at that moment)
My logs and maps are constantly changing because I'm currently in the process of tuning...If you don't mind we could continue the conversation via email, and I'll send you my current maps with a fresh log for you to take a look...thanks man
Oh no, if you are referring to post #5 where I have that 3000rpm 260-330 load highlighted that was not directly related to the problem area...that was just me smoothing out the table from some changes I made (I just happened to hit the printscreen at that moment)
My logs and maps are constantly changing because I'm currently in the process of tuning...If you don't mind we could continue the conversation via email, and I'll send you my current maps with a fresh log for you to take a look...thanks man
Wreckleford, on the AFRMAP issue, since you mentioned it I just went back through my evo9base's XML and realized that the endian for "AFR" (among a few other items) in the scaling list is set to big and I'm on v1.29a which means it should be little...do you think this could be the cause of my AFRMAP not correlating with my actual fuel map?
Raas -- I sent you an email after looking at your log and your tune....A few things to note that did not sync with your earlier statement -- (1) low/high maps are NOT the same and (2) your car seems to be interpolating between the low / hi maps even when your log shows no sign of knock. I don't know why the ECU would be doing this, but IMHO that is the issue. Try making the hi and lo maps the same (as hi), reflash, and do a few more logs....
Raas -- I sent you an email after looking at your log and your tune....A few things to note that did not sync with your earlier statement -- (1) low/high maps are NOT the same and (2) your car seems to be interpolating between the low / hi maps even when your log shows no sign of knock. I don't know why the ECU would be doing this, but IMHO that is the issue. Try making the hi and lo maps the same (as hi), reflash, and do a few more logs....
^^ Exactly...So the REAL question is why would the ECU start interpolating between the Hi / Low maps without any logged knock or just 1 count of knock ? I am wondering if there is logic that senses the octane (since he is running 90 ) and automatically starts migrating to the Low maps ? (Tephra / JC Banks / MrFred / others may be able to provide insight...)
Last edited by cij911; Jun 14, 2009 at 09:43 AM.
Ok I just finished talking to cij and he recommended a few changes that I should make to the maps...gonna give it a try and report back in a bit. There was a little misunderstanding about the maps being the same, I thought he was referring to the 123 hi being the same but he mean 123 hi/lo all being the same just to trick the ecu when interpolating between the both maps. I also find it strange that the car would look up the low maps when there is no knock present...
it would be from your meth i' presume, especially if it's an on/off kit and not progressively tracking your IDCS, even with the HFS-6 I find I have to lean out progressively as the meth comes on, it pretty much lowers AFRs a full point. No way will the afrmap match your afrs with meth as the ecu doesn't track the meth idcs.