Stopping the fuel trims affecting WOT fueling
That's awesome!!!
Thank you for this...
I finally got my cruise trims -1.01 on average to 0. But this will make your life so much easier. I will let you know how it works.
EDIT:
THIS IS HOW IT LOOKS FROM 52680020.ROM from a 2008 GSR.
IS there a need to edit the top two values to what you have posted?
Thank you for this...
I finally got my cruise trims -1.01 on average to 0. But this will make your life so much easier. I will let you know how it works.
EDIT:
THIS IS HOW IT LOOKS FROM 52680020.ROM from a 2008 GSR.
IS there a need to edit the top two values to what you have posted?
i just got my DW 1000cc's in today and i'm planning on installing them on wednesday and running e85. so what you're saying is that i dont have to worry about the LTFT's because they will average to 0%? all i have to do now is get the right scaling? or how would this finding benefit me?
i just got my DW 1000cc's in today and i'm planning on installing them on wednesday and running e85. so what you're saying is that i dont have to worry about the LTFT's because they will average to 0%? all i have to do now is get the right scaling? or how would this finding benefit me?
I made a small how to on the other forum. FIX the link first.
Code:
http://www.evo x forums.com/forums/showthread.php?t=22338
I have input the codes in and the Close Loop LT Trim Control table appeared. However my top two values are different from what you had:
Low -> Mid: 62.50
Mid -> Low: 56.25
Mid -> High: 1587.50
High -> Mid: 1581.25
Do I need to change the top two to what suggested?
Low -> Mid: 62.50
Mid -> Low: 56.25
Mid -> High: 1587.50
High -> Mid: 1581.25
Do I need to change the top two to what suggested?
Replied on the other forum.
Man, this shows how ignorant I am! I thought that open loop tuning wasn't affected by the fuel trims!
I am not yet able to log fuel trims in my Ralliart, so I didn't pay much attention to them until now.
Will the code you have posted work in the 55590006 2010 Ralliart ROM?
I can't start doing real E-85 tuning until I can log fuel trims, so if anyone feels like finding the addresses for fuel trims in the 2010 Ralliart ROM, it is available for download here:
http://norcalmotorsports.org/users/b...M_55590006.zip
Thanks,
Keith
I am not yet able to log fuel trims in my Ralliart, so I didn't pay much attention to them until now.
Will the code you have posted work in the 55590006 2010 Ralliart ROM?
I can't start doing real E-85 tuning until I can log fuel trims, so if anyone feels like finding the addresses for fuel trims in the 2010 Ralliart ROM, it is available for download here:
http://norcalmotorsports.org/users/b...M_55590006.zip
Thanks,
Keith
Evolved Member
Joined: Oct 2002
Posts: 2,788
Likes: 1
Don't you mean the STFT drops to 0% when in _open_ loop? Sorry I am confused.. I thought closed loop mode meant trims are in effect including the stft (real time o2 feedback trim).
I tried a few items and got gibberish results. I don't remember what all I tried before begging for help, but the addresses don't seem to match up with what I was given by helpful members of the forums. For example, for RPM the above website lists mut address "21" In my mutt tale address 21 I have 80971D. The request ID I was given by helpful members that I am using in EVOscan for RPM is 23808763.... why are they different, and why don't the MUT derived numbers work for me?
So, is my mutt table jacked up in some way or do I have no clue how to actually use it?
Keith
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Last time I tried to use mutt table addresses I had no luck at all! Using this page http://evoecu.logic.net/wiki/MUT_Requests I tried to set up EvoScan to log the basics.
I tried a few items and got gibberish results. I don't remember what all I tried before begging for help, but the addresses don't seem to match up with what I was given by helpful members of the forums. For example, for RPM the above website lists mut address "21" In my mutt tale address 21 I have 80971D. The request ID I was given by helpful members that I am using in EVOscan for RPM is 23808763.... why are they different, and why don't the MUT derived numbers work for me?
I tried a few items and got gibberish results. I don't remember what all I tried before begging for help, but the addresses don't seem to match up with what I was given by helpful members of the forums. For example, for RPM the above website lists mut address "21" In my mutt tale address 21 I have 80971D. The request ID I was given by helpful members that I am using in EVOscan for RPM is 23808763.... why are they different, and why don't the MUT derived numbers work for me?
2) Evoscan requires a prefix of "23"
3) Depending on whether you are requesting an ODD or EVEN byte you will need to say returnbytes=1 or 2..
Actually pull to pull was possible, if I had just warmed up the car sometimes it would be stable, other times it would start shifting the LTFT from -2 over to +3 and run about 5% richer than expected. So my 11.5 AFR would drop to around 11.0 AFR and it would be smokescreen city. Then If I got on a different road with a 30 mph speed limit and the LTFT's started adjusting again it could swing back again. If I got on power entering the expressway then out of the blue the trims would be back to the way they were. I've logged it in the same drive several times and it was EVIL.
Another issue was that at higher airflows, if I was currently at +5 LTFT and it surpassed that higher hz reading at 6000-6500 rpm's with a larger turbo, out of the blue the 11.5 AFR that I tuned for might lean out to 12.0 AFR unexpectedly when it changed from mid to high trims.
Like Tehpra said, the high trims that we are kicking in earlier now are going to average 0% since the running average of the STFT during WOT should always be 0%. I love this!
Another issue was that at higher airflows, if I was currently at +5 LTFT and it surpassed that higher hz reading at 6000-6500 rpm's with a larger turbo, out of the blue the 11.5 AFR that I tuned for might lean out to 12.0 AFR unexpectedly when it changed from mid to high trims.
Like Tehpra said, the high trims that we are kicking in earlier now are going to average 0% since the running average of the STFT during WOT should always be 0%. I love this!
I guess if I could count on the LTFT to be more stable & accurate it would balance the tune based on intake temps and fuel used with more safety but the trouble is it almost has a mind of it's own. I'll update more when I figure out why my LTFT's are drifting so positive.
Last edited by Hiboost; Nov 18, 2009 at 07:52 AM.