Is it normal to have the closed loop target RPM spike to uncalibrated values (on the during a drive? I have it activating and taking out/putting in spark aswell - which explains the surging/lugging that I felt this morning.

So the question is not about the closed loop control Advanced PID/simple, it is about the entry conditions for the activation of Closed Loop Idle, and its subsequent effect upon both timing (idle advance set to adaptive upon closed loop idle) and the idle valve duty cycle.

The car is a '92 Mk1 1.6 and so lacks a TPS - and so lacks also the Idle Activation TPS threshold.

Any ideas as the seemingly uncommanded altering of my spark and air ain't good! I want to ensure that closed loop idle activates < X RPM.

Super.

 

It would appear that based upon some sort of entry the Idle setpoint is made equal to the RPM at the point of trigger, it then returns via what looks like a constant ramp, to the Closed loop setpoint as set up in the closed loop target curve.

The result is that seemingly randomly, the idle setpoint becomes , for example 2345RPM or 3456RPM depend I suppose on whether it went into closed loop control at that point. Is there a boolean flag available on the recordings to tell if the engine is in closed loop? Though I suppose I can infer from the change in idle control advance that it is in closed loop at that point..

Pah - unplugged the valve and turned off idle advance in the mean time....... Ahh, Much better.....

 

if its activating while driving you have completely botched activation settings.

 

Indeed, and now I must away to find how and why. Any way of looking at the code behind the controller?

 

If this is not a case of "Be careful what you wish for," you can check out the code in the MS2 Development Forum at MSExtra.com.