idle issues
#16
EvoM Community Team Leader
If you take a look at page 128 Section 10.15 of Merlin's tuning guide I think you will see where I am coming from. The value in the table is a static value, what you normally see in your logs is the learned value. All i think i am advocating here is making the learned value much closer to the static one.
#17
Ok so tried everything and its still acting up so i got pissed off and tried 9653 rom. Copied everything over and was finally able to get car started after it not wanting to start. The car idled great and isc steps stayed dead locked at 10 which i never seen before. Now, theres a fueling problem. I had to make map ve 1:1 and rpm factory setting for it to idle stoich. I cant drive it because itll go lean. If i rev it itll go lean as opposed to 9417 where itll richen up. I checked all the settings and it seems fine. Really wanted to try out 9653. ****ing car lol.
#18
Evolved Member
Ok so tried everything and its still acting up so i got pissed off and tried 9653 rom. Copied everything over and was finally able to get car started after it not wanting to start. The car idled great and isc steps stayed dead locked at 10 which i never seen before. Now, theres a fueling problem. I had to make map ve 1:1 and rpm factory setting for it to idle stoich. I cant drive it because itll go lean. If i rev it itll go lean as opposed to 9417 where itll richen up. I checked all the settings and it seems fine. Really wanted to try out 9653. ****ing car lol.
Now i feel it is a matter of tuning it step by step. Tune it from scratch you will be happier.
#19
I was looking over the map last night and I think I found the problem. In my haste copying everything over I copied the maf compensation settings from 9417. 9417 uses % and 9653 uses g/s. The numbers ended up being cut by half lol. I will try it again today.
Now this is going to sound dumb because by now I should know this but maybe I’m just overloaded with work and trying to figure this **** out. The way I would always tune the map ve and rom ve tables was I would look at load and make changes on the right side of table. For example, let’s say at idle it’s at 36 load on evoscan and I wanted to go richer. Let’s say map ve is as follows on left side : 20, 39.9, 50, 80, etc. Since idle is showing 36 load I would raise value on right hand side at the 20kpa. The other day I realized this didn’t make any changes. I looked at barometer(kpa) on evoscan and it was reading 58. So I made changes to the right hand side of where the 50 is in map ve and afr changes for idle. Have I been doing this wrong the whole time? Was I supposed to be logging kpa on evoscan to make changes to the ve tables? Maybe it’s because I changed the left hand side of the table from original values? Sorry for the long post just didn’t want to make a whole new thread for this. I’ll report back on 9653.
Now this is going to sound dumb because by now I should know this but maybe I’m just overloaded with work and trying to figure this **** out. The way I would always tune the map ve and rom ve tables was I would look at load and make changes on the right side of table. For example, let’s say at idle it’s at 36 load on evoscan and I wanted to go richer. Let’s say map ve is as follows on left side : 20, 39.9, 50, 80, etc. Since idle is showing 36 load I would raise value on right hand side at the 20kpa. The other day I realized this didn’t make any changes. I looked at barometer(kpa) on evoscan and it was reading 58. So I made changes to the right hand side of where the 50 is in map ve and afr changes for idle. Have I been doing this wrong the whole time? Was I supposed to be logging kpa on evoscan to make changes to the ve tables? Maybe it’s because I changed the left hand side of the table from original values? Sorry for the long post just didn’t want to make a whole new thread for this. I’ll report back on 9653.
#20
Evolved Member
I was looking over the map last night and I think I found the problem. In my haste copying everything over I copied the maf compensation settings from 9417. 9417 uses % and 9653 uses g/s. The numbers ended up being cut by half lol. I will try it again today.
Now this is going to sound dumb because by now I should know this but maybe I’m just overloaded with work and trying to figure this **** out. The way I would always tune the map ve and rom ve tables was I would look at load and make changes on the right side of table. For example, let’s say at idle it’s at 36 load on evoscan and I wanted to go richer. Let’s say map ve is as follows on left side : 20, 39.9, 50, 80, etc. Since idle is showing 36 load I would raise value on right hand side at the 20kpa. The other day I realized this didn’t make any changes. I looked at barometer(kpa) on evoscan and it was reading 58. So I made changes to the right hand side of where the 50 is in map ve and afr changes for idle. Have I been doing this wrong the whole time? Was I supposed to be logging kpa on evoscan to make changes to the ve tables? Maybe it’s because I changed the left hand side of the table from original values? Sorry for the long post just didn’t want to make a whole new thread for this. I’ll report back on 9653.
Now this is going to sound dumb because by now I should know this but maybe I’m just overloaded with work and trying to figure this **** out. The way I would always tune the map ve and rom ve tables was I would look at load and make changes on the right side of table. For example, let’s say at idle it’s at 36 load on evoscan and I wanted to go richer. Let’s say map ve is as follows on left side : 20, 39.9, 50, 80, etc. Since idle is showing 36 load I would raise value on right hand side at the 20kpa. The other day I realized this didn’t make any changes. I looked at barometer(kpa) on evoscan and it was reading 58. So I made changes to the right hand side of where the 50 is in map ve and afr changes for idle. Have I been doing this wrong the whole time? Was I supposed to be logging kpa on evoscan to make changes to the ve tables? Maybe it’s because I changed the left hand side of the table from original values? Sorry for the long post just didn’t want to make a whole new thread for this. I’ll report back on 9653.
#21
I never payed attention to it. I always thought what I had log and go by was load and make changes to ve according to load. I realized one day that the map ve table said kpa on the left hand side of the column and it hit me that maybe I should be going by kpa to make changes to ve instead of load. Am I right? Sorry I’ve just been learning all this on my own with the help of a friend on here but I think on that I misunderstood him. So am I right in thinking that I should be logging kpa and making changes to the right hand side of the column according to the numbers that the readings fall in on the left hand side? If that makes any sense?
#22
Evolved Member
I never payed attention to it. I always thought what I had log and go by was load and make changes to ve according to load. I realized one day that the map ve table said kpa on the left hand side of the column and it hit me that maybe I should be going by kpa to make changes to ve instead of load. Am I right? Sorry I’ve just been learning all this on my own with the help of a friend on here but I think on that I misunderstood him. So am I right in thinking that I should be logging kpa and making changes to the right hand side of the column according to the numbers that the readings fall in on the left hand side? If that makes any sense?
Its nice to see how a little brain storming can do lol
#23
Lol yeah. I’ve been playing around with 9653. I think I like it better but I tried closed loop and I have the same lean tip in. Take off is horrible goes full lean. I’ve read so many threads on here I think I know this forum by heart. Tried every async table, fuel map, hz, everything. Idk just can’t figure it out. Open loop it is I guess.
#24
Evolved Member
iTrader: (4)
I have it set at 950 and sometimes it’ll drop to about 900 and go as high as 1100.
So should I adjust biss with sas to get it down to 7 steps?
#25
Evolved Member
iTrader: (4)
Ditch the 9653 and move to the better 94170715 ROM. It is hands down the best American EVO 8 rom out there. Know it by heart. The 9653 Rom is Euro Spec, and they don't have what we have because of the USDM Market and Emissions BS the US has. Car will run better on the 0715 ROM, I know, I have completely tested both back in the days when they were released.
#26
You’re talking about the 9417 rom? I’ve always been on that rom. I figured I’d try the 9653 because it has a lot more async stuff and options the 9417 doesn’t have. This was in hopes of getting the car running with closed loop. I can’t get rid of the lean tip in no matter what I do. Also, I’ve found the 9417 to be inconsistent. It feels like one day it does one thing and then another day it changes idk.