intenseapple

After fighting to get my idle perfect using firmware v1.4.x I got close to success. Idle was mostly stable other than the initial entrance into CL idle during which the RPM would drop uncomfortably low before idle kicked in. Reducing rpmDOT threshold helped with this but caused issues where the ECU would kick itself out of CL idle under load changes (fans, AC especially). I was fairly comfortable with it how it worked though. I just switched to firmware v1.5.1 trying to fix an unrelated issues and realized that CL Idle PID entry settings had been switched over to "engine state". I fiddled with this for a while but it worked even worse than the 1.4.x code did. After a few hours I decided to dig into the code and really think about how all of this was working. The main question I came to was this:

Why do we even care about RPMdot for the idle state?

In my mind, the idle state consists of a closed throttle and low RPM (say <1% TPS and <70 RPM above cl_idle_target_rpm). Why would rpmDOT play a role in entering idle at all? I am not an expert in engine state tuning or the MS3 firmware by any means, but I do have solid programming skills and I'd really like to take a stab at making this work better for me. Am I crazy to think that the current setup that MS3 uses for idle is junk?