Call me tonight after I get home from the gym (around 8:30). Lets go thru your EVOScan XML and see if the bits match mine just to be sure you aren't chasing your tail.
Printable View
Call me tonight after I get home from the gym (around 8:30). Lets go thru your EVOScan XML and see if the bits match mine just to be sure you aren't chasing your tail.
Sounds good; I certainly don't like chasing my tail. ABS switch is back to 1 after my doctor's appointment.
Well looks like the abs switch values were correct and the line to ecu is correct. I pulled the line to the ecu. 1 went away. Manually triggered and the switch toggled. Also. Apparently there is more to this than just stepping the isc when triggered. Nothing happened at idle. Guessing the car has to be rolling to a stop? Or my other issues are involved.
New isc/throttle will be coming Tuesday so I can do some more debug after that.
New throttle body is on! Damn it looks sexy lol. After setting the idle screw and it returns to normal mode, the rpms would be high but the ISC would not go lower than 22/24ish. If I tightened the screw it would raise the steps to match but if I loosened it would not go lower. I increased the subtractor table and then it was able to go low to enough steps to match what was set in the idle adjustment mode.
Does that seem odd?
What was your coolant temp during all this?
Increasing the subtract or means there's a huge variance between what the ECU sees for airflow and what the actual airflow is.
Car was fully warmed up, 180deg. Don't recall the exact value but way above the setting for the idle control temp. I only changed the 180deg point for the subtractor so the coolant was in that range.
Hmm I have so many questions but 5 minutes before a meeting lol.
So before the subtractor change:
I put it in SAS mode, isc drops to 7 and timing steadies.
I adjust the screw to target idle
I turn off SAS mode and in a few seconds the isc climbs to 20s and so does idle.
So the ecu has some idea of rpm vs airflow and it's trying to match it? What should my airflows be at 700 and 1000 rpm? I guess what are stock numbers?
So I tried to drive the car with the new throttle and the subtractor amount increased. Same problem but I was just crossing the fingers lol.
I reverted the subtractor back to stock and adjusted my Maft gen II's low settings at the idle rpm range. I was trying to see if I could get the car to actually adjust the isc lower without having to increase the subtractor. Also to see if the trims would move. Neither direction moved. All this seemed to do is increase/decrease the airflow.
Then I tried to play with the VE smoothing table. Increasing/decreasing didn't do anything except increase/decrease my o2 trim.
Same with the MAF scaling table.
I KNOW the trims worked when I first went flashecu so something has changed since. Also, apparently flashing different configs sometimes makes them trim. I tried an older config that I saw it trimming and today it didn't work. Something is screwy and it seems all connected.
Something else I noticed when watching this stuff live. My airflow hz seem to somehow jump. Engine doesn't feel any different but maybe this is a symptom of weirdness..
Example airflow:
50.03
75.38
50.32
25.45
49.83
49.34
49.73
49.73
50.32
51.5
50.61
50.52
74.99
49.83
49.53
50.22
50.12
50.12
50.81
75.38
74.89
49.63
49.93
25.75
50.52
From a separate log I also see it trying to adjust the isc steps lower.
Example ISC:
27
23
7
7
7
13
25
27
7steps is where it should be per the SAS mode adjustment...I believe the ecu is trying to move to 7 steps because the airflow reduces here so the steps are real. I only have one log of this situation.
What happens if you disabled closed loop entirely?
Was looking back at some logs. Here is an o2 log when my trims were working. This was back in 2012.
https://dl.dropboxusercontent.com/u/...s/o2s_2012.jpg
here they are now with trims stuck at 0
https://dl.dropboxusercontent.com/u/...s_20140604.jpg
Even still. Humor me. Try it.
For shits and giggles I tried flashing a stock vr4 rom with just my injector scaling,1st gen peripheries, I moved no other config from what I have been using. Trims almost instantly and the car drives and does not stall at all. I think I need to start with a virgin v2 config and see what happens. Trims max out quickly so my scaling must be off but I think a lot of that was tuned out in other tables. Odd that it being so far off and it ran better in turns of not stalling at stops lol.
Oh, disabling closed loop just made the car pulsate and run funny. It still wanted to stall just backing out.
Compare the two roms in ecu flash
Well, yeah...
I've already done this between configs to try and pinpoint what tables were causing the issue. Granted, I was never able to get the idle to work only the trims, got to the point where I removed all my changes and it still wouldn't work. Either I am doing something wrong (could never be!) or something is being weird.
Instead of working my way back to stock tables, going to move forward from stock tables and see how it goes. I found a log in 2013 where my trims were working. I had v2 at that point but what's odd, is I've only been making open loop type adjustments. Possible I inadvertently changed something and also saved it to my stock v2 config. Going to start from a rom from my mail to ensure I didn't screw with it.
I like to run the rom compare between the latest and the original v2 one.
Okay. THIS is dumb. Car is trimming and not stalling at idle.
Here's the sequence of events.
Flashed stock vr4 rom with injector stuff.
Reset battery
Trims work/no stalling
Flashed virgin v2 rom with injector stuff.
Reset battery
Trims work/no stalling
Copied most of the stuff from my "broken" rom to this new one. (skipped a couple things like knock settings and output lines that I had configured but never used)
Reset battery
Trims work/no stalling
Something is funny here. I am tempted to flash the "broken" one again to see if it will work but I don't want to make something not work again lol.
Are you sure this car is not, or has not ever been green? :suspect:
Hmm... I wonder if its not a RAM interface issue with your particular chip. ISC error learning and fuel trims are both things that are stored in RAM. This is where your modified reference points for a "tuned" idle and 14.7 AFR reside.
Holy shit I don't think it's run this well in a year lol.
Whatever your trims and ISC counts settle with, be sure to save them in case you have this issue again. Use that data to make a better "base" tune.
Hmm, what do you mean exactly? For the ISC, do you mean the initial ISC position ac on/off table? For the Trims, only thing i can do is change the injector scaling or the air/fuel tune right? I certainly don't want to do something that will affect my tune globally.
Adjust your MAF comp (VE) tables so that your trimS are close to zero and your base ISCV tables to match the values you are logging now.
Coo coo, thanks!