[FW MOD] ms2extra 3.2.1 beta gslender v2
 

Whoa! Just released v2 of my mods, and this update is a major release to the mods I've previously completed and includes significant changes from previous release.

http://www.msextra.com/forums/viewto...p?f=91&t=43370

The changes and new features include:

• Based on latest MS2/Extra 3.2.1 beta
• New Memory Page - now ms2 has lots more space for more future mods.
• New MS3 Initial Value Tables (ivt) - in addition to last-known-good (lkg) for idle duty (for MAT correction).
• New MS3 PWM voltage correction tables (volt idle correction).
• Adaptive Idle Advanced (rpm error to target) plus extra bins
• Latest MS3 Bug fixes in AC idle handing
• RPM pid input smoothing (smoother IAC further still)
• AC/Fan load idle up, including idle duty adder; AC and cooling fan engagement time delay; AC and cooling fan disengagement delay
• Clutch/Neutral closed loop PID lockout
• tpsDOT smoothing

It's just so chocka-full of goodness ya have ta scream!! :yippee:

G

Epic!

Particularly point 2, So the MSII is not full any-more.

1) How did you do this and,
2) Doesn't that nullify some of the devs reasons for no longer working on MSII i.e. that it's full so back porting of MSIII code can't be done?

AFAIK most of the changes are backported from MS3 - only its gslenders work now (in coorperation with Ken, James and Jean).

I am really impressed by the dynamics the MS2 development has taken in the last weeks... Unfortunatly I have to wait until 1st of april until I can drive my car again. (The car is in winter sleep mode now...)

Richie,

Yes the extra memory page is awesome, which allowed a lot of stuff to be added.

We have backported from MS3 (with permission from devs):
voltage correction tables
initial duty value table- optional replacement for last known good value
PID RPMdot smoothing (sliding window)

But the feature with the most significant impact for me is the Adaptive Idle Advance- just smoothens all your issues away. It's a modification to the idle advance curve, making it rpm-error based, not map based (but tha option is still there if needed). I believe that will be forward ported to MS3 ;)

Would appreciate more people uploading data on how this FW is running. I believe there are still some issues to hunt down, particularly in the throttle lift area using Initial Value Table, particularly with AC.

Greg

It never was full? It is a real bitch to develop on and ms3 is so much better that you'd sell ya mother to get one if you only had ms2 to develop on going fwd.

Whoa! Not sure if I'd say it is my work - I didn't do that much without a crazy amount of help from Ken. It is really a joint effort.

Yup, I'm pretty pleased too, but if you can, upgrade to ms3 - I've learn't a lot about the ms2 and she ain't pretty. :giggle:

Using 3.2.1 gslender v2.

This FW has a bug where with AC load, the dashpot is not added on throttle lift, only the AC adder. Without AC, the dashpot is added normally.

I solved this (while waiting for the fix) by setting dashpot to zero and incorporating the dashpot value into the IVT table.

This is what I got initially- too much duty in the IVT causing the revs to hang high and PID having to pulll it down.
http://img.photobucket.com/albums/v6...IVTtoohigh.png

Over the next 10 mins, as the engine was warming up, I tuned the IVT table, reducing values in the relevant rows. The final table on the left, with red numbers.
Attachment 186231

The final result: a CONSISTENT catching of the revs on throttle lift, and QUIET entry into CL idle! :yeah!:
Attachment 186232

These are free revs in neutral (worst case for droops). I did do a short test run in the parking lot (was raining cats and dogs outside), with similar consistent results!
Attachment 186233

...then update ya sig !! :giggle:

Holy crap Greg, that RPM trace looks OEM.

Great work grant and Greg!

Yup, the predictablility is really nice. Knowing that there won't be any surprises. That is the great difference between the Initial Value Table and Last Known Good. It takes some extra effort to populate the table, but once it's dialled in, it becomes dead reliable. Now hopefully the plugin API for TS is released so we can figure out how to automate the population of that table (among other things).

This is probably as good as it gets, until the dashpot itself is revamped, to tie it to RPMdot (which is what it is meant to control). Something like an exponential decay as it approaches target.