MS3 pre-1.5.1 beta 1 firmware released

[muythaibxr]

I will have a look later tonight.

[aidandj]

Just a description of the log. The first attempt at idle it works perfectly. Starts at the initial value, then slowly works its way down to minimum.



Next time around it drops straight to the minimum, and then kind of works it way back up.

[VcrMiata]

Exiting and re-entering closed loop idle does not always reset initial conditions resulting in oscillations.

I noticed when I'm dropping out of CLI because of exceeding slow deceleration, when CLI is re-entered
the initial target RPM, initial PWM duty cycle and the ramp time are not reset - the values continue from the point that we dropped out of CLI.
It also looks like ramp down continues to affect PWM duty cycle while outside of CLI (maybe because we are in engine idling state?).

The impact of this is when re-entering CLI, the conditions increasingly become worse as there is a greater difference between
CLI pre-condition PWM (when engine idling state occurs) and actual CLI PWM entry. This causes CLI oscillation.

The fix for this in my case was to increase slow deceleration from -300 (which seemed reasonable) to -600 which I think is a bit high (although I have no objective data to present evidence of this assumption ) -

In the example below (tune has slow deceleration set to 300), notice how the PWM Idle duty difference increases causing an even greater RPMdot.
CLI On reflects [status 2] & 128

idleoscillation.png

[aidandj]

Its almost like sometimes its using the Last Value, instead of the initial table.

[CMac89]

How's this coming along for stable release?

[jsmcortina]

How's this coming along for stable release?

There will likely be another couple of betas first.

James