Stalling and bouncing idle (after fixing idle switch)

[stealthee]

Not sure if it's your issue or not, but I had bad idle issues when my SAS got adjusted and was out of spec

[Toni]

open both roms and run the compare function. It won't tell you if the code is different, but should show any tables that are different.

Yeah, that is how I originally transferred my settings but then we made more after. I may do it again but this time only transfer the few things that really matter to get the car to run.

Not sure if it's your issue or not, but I had bad idle issues when my SAS got adjusted and was out of spec

I've checked it before and it was in spec and needed no adjustment. I'm thinking I may go through it all again.

[Greg E]

I haven't forgotten about you Toni. Got preoccupied last night.

Did I ever ask you if your MAF has a screen?

[Toni]

No problems, this would be nice to fix but easy to get around by disabling the idle switch lol so at least I can drive it

MAF does still have a screen.

Another data point. My trims saved from the old rom to the new but the new rom doesn't update them. I was a bit surprised to see the settings saved upon flash but I guess that makes sense, user vs program storage will be different.

[Greg E]

I hate to be a pain in the ass but these lines going everywhere are confusing.

Can you get me an excell log with the following:

TPS
RPM
Coolant temp
VE
2 byte load
2 byte airflow
Both narrowbands
ISC count
Idle Position switch
Target idle RPM
Speedo

[Greg E]

There is absolutely no reason why the production release of chrome wouldn't update your trims. It works perfectly in hundreds of cars. There are absolutely no code changes to that area of the ROM. It's all stock. If periphery 0 hasn't been changed, what about the fuel trim range table in the Open/Closed loop section? The one that deturmines what HZ corresponds to which trim.

[Toni]

I hate to be a pain in the ass but these lines going everywhere are confusing.

Can you get me an excell log with the following:

TPS
RPM
Coolant temp
VE
2 byte load
2 byte airflow
Both narrowbands
ISC count
Idle Position switch
Target idle RPM
Speedo

No problem, it was just meant for an overall view. I pasted a link to the evoscan log that generated it but doesn't have all the items you are requesting.

I assume you want a cruising log, an idle log, and a log of a stop?

There is absolutely no reason why the production release of chrome wouldn't update your trims. It works perfectly in hundreds of cars. There are absolutely no code changes to that area of the ROM. It's all stock. If periphery 0 hasn't been changed, what about the fuel trim range table in the Open/Closed loop section? The one that deturmines what HZ corresponds to which trim.

I realize it works, I guess I'm not debating that fact but now that I look back, it does sound like it. Just saying what I have seems to not work as compared to the betas I have but I'm saying my config of it.

No changes in the open/closed loop section.

[Toni]

Noticed something that doesn't seem to make sense to me.

Once I left off the throttle, airflow drops. This makes sense to me. What doesn't, is the fact that timing went up and so did RPM but airflow continued to drop? Typically in these idle situations I see airflow as a result of rpm and rpm as a result of timing. This normal operation that the ecu wants to add timing right after throttle close and idle switch triggered?

[Greg E]

If airflow goes down, load goes down and timing goes up. It's in the base timing map.

[Toni]

Did you switch something there, doesn't timing typically go up with less load?