[FW MOD] ms2extra pre3.3alpha5 gslender v2.7

[gslender]

UPDATE : This mod has been updated to v2.8- see this thread >> http://www.msextra.com/forums/viewtopic ... 91&t=46616

G'day...

This modified firmware is based on the alpha release MS2/Extra 3.3alpha5 firmware and adds some further enhancements/fixes - notably most of the 2.6 mod features plus a few new features and fixes.

Changes made from alpha release MS2/Extra 3.3alpha5 are as follows:
* [since 2.6] MAP ‘Use Average’ fixes (MAP values now produced when engine not running)
* [since 2.6] RPM Smoothing – a moving sliding window added (help keep rpm values smooth)
* [since 2.6] tpsDOT Smoothing – a moving anchor option added (reduces false triggers in AE)
* [since 2.6] Adaptive PID – allows PID terms to be dampened in non-linear amounts based on a delta to target idle RPM.
* [since 2.6] Adaptive PWM Idle Voltage Compensation – adds a dynamic voltage baseline to ensure voltage droops or surges are relative to battery levels.
* [new in 2.7] Fuel calc now uses aircorrection and gammae in 10ths % resolution (eg. 100.1%)
* [new in 2.7] Changed mat based retard to linear MAT/Fuelload table (eg. allows retard when at full boost but none at idle)
* [new in 2.7] Added RPM/FuelLoad table scaling to aircorrection (eg. allows reduction to 0% air correction based on RPM & MAP/Load)

Plus these new features/changes since [mod] gslender v2.4.4 (or earlier):
* Adaptive VE – allows a non-linear adjustment to VE at idle based on a delta to target idle RPM.
* Previous TPS ‘Use Average’ option removed (as Alpha3 has TPS last-8-values-average from MS3 included)
* Ignore MAT air correction during ASE (to reduce heat soak) in Cranking Settings

Firmware >>

ms2extra_pre3.3alpha5_gslender_v2.7.zip

Dev Changes File >>

mod_changes_2.7.txt

Source>>

ms2extra_pre3.3alpha5_gslender_v2.7_source.zip

Enjoy
G

[msegt]

see if i would have waited 5 minuted id have had my answer, ill load it in the morning before we leave and let ya know if i find anything.

[duxthe1]

Dang! I just updated to 2.6 over the past weekend. Its been working (managing load at idle) SOOOOOO AWESOME that I wouldn't be tempted to update again but I see that the MAT retard at idle has been fixed. Considering that I specificly requested that, I guess I HAVE to update again.

[msegt]

Dang! I just updated to 2.6 over the past weekend. Its been working (managing load at idle) SOOOOOO AWESOME that I wouldn't be tempted to update again but I see that the MAT retard at idle has been fixed. Considering that I specificly requested that, I guess I HAVE to update again.

ya i checked new threads, pm'ed him, and it was up 2 seconds later..lol... good timing, i was bored, figured id ask, but its loaded ill try it tomarrow though...lol..

[sd1nl]

Hi,

Tried to make a new project on the 2.7 firmware, but it's giving me some difficulties:

The default RPM/MAP values in the "Load-RPM MAT correction scaling table" in this firmware are crazy, and when I try to change them I get a tunerstudio message that the values are out of range and I have to force TS to shutdown in Windows.

Because there is no appropriate "default tune" for the GSlender 2.7 firmware I cannot load a default correction table, and I'm pretty much stuck here.

What is the solution?

Rene

[gslender]

The default RPM/MAP values in the "Load-RPM MAT correction scaling table" in this firmware are crazy, and when I try to change them I get a tunerstudio message that the values are out of range and I have to force TS to shutdown in Windows.

Because there is no appropriate "default tune" for the GSlender 2.7 firmware I cannot load a default correction table, and I'm pretty much stuck here.

If you were to burn the firmware to an ecu, when TS connect with your old tune and updated project ini, the ecu would apply default values and TS would use them. The crazy is due to TS not having default behaviors and is normal.

Yes a default tune might help, but for most people, simply taking a backup copy of their current tune, burning the new firmware and connecting works fine. If things don't work, then you can always revert back to your old tune and reload the firmware and all is restored.

G

[sd1nl]

Yes, maybe I can use the 2.7 firmware, and get it into my ECU, but everytime I will try to change the RPM values in the RPM-LOAD-MAT correction table TS will freeze up. So how will I ever be able to enter the correct values in this table?

Or has my ECU default values for this table? Don't think so, because they were not there in v2.6

I actually loaded my old (v2.6) tune in TS, but this didn't change the values

[sd1nl]

Could you perhaps post a partial file for this table? Then I could import this

[gslender]

Yes, maybe I can use the 2.7 firmware, and get it into my ECU, but everytime I will try to change the RPM values in the RPM-LOAD-MAT correction table TS will freeze up. So how will I ever be able to enter the correct values in this table?

Or has my ECU default values for this table? Don't think so, because they were not there in v2.6

I actually loaded my old (v2.6) tune in TS, but this didn't change the values

What version of TS are you trying?

G

[sd1nl]

TS v 2.0.5

[gslender]

TS v 2.0.5

Post a screen shot as I'm not seeing it.....Mmmmmmm

G

[sd1nl]

This is the table:

v2.7a.png

This is the error when I try to change the rpm range:

v2.7b.png

[jsmcortina]

You need to be connected! (i.e. online) That's what's been said above.

James

[gslender]

LOL.... you need to correctly set the X / Y axis first before you attempt to correct the table bins.

Screen Shot 2012-07-14 at 8.33.13 AM.png

Here is how mine looks.

Sorry for laughing but sometimes until you see the issue, you are stumped trying to figure out what is wrong, when after you see it, its obvious.

G

[jsmcortina]

Working offline with new firmware is a very poor idea.

If you must do it then you need to use the default.msq for the new firmware first, then load your old MSQ.

James

[sd1nl]

LOL?

That's what I'm trying to tell you guys:

Setting the bins is not the problem!

When I'm attempting to change the XY axis TS gives the error and I have to shutdown

I did try to load the default 3.3.alpha5 tune, but this doesn't change the "load-rpm linear MAT correction scaling".

I will try to go online with this firmware today.

[jsmcortina]

LOL?

That's what I'm trying to tell you guys:

...and that's because you are working offline....

So, instead of arguing just go online.

James

[sd1nl]

Thanks for the help. Going online did indeed load a default file into TS. Problem solved. Rene

[duxthe1]

I got 2.7 installed today. There was an issue with the first attempt to download the firmware to the controller and the car wouldn't run. A second attempt went ok, without any weird warnings. This was the first update where I actually remembered to reconnect the coil and the injectors. Imagine my disappointment when it spun without firing. Once I got it to run, it does seem to settle into an idle better than it ever has.

3 cheers for GSLender Hip Hip Hooray!

[piledriver]

Loaded up and ran with no issues, although I may have spotted a bug (or just something weird) in WinXP or TS under WinXP...

When TS was shutdown (after running when it online) cycling power on the MS would not cause the FP relay to come on/prime==no start. I reloaded 2.6b and even 33a5 to make sure I wasn't crazy, same behavior.

Unplugging the serial cable, it worked as expected again.
Is there some serial shennanigans going on here?

Could not duplicate under Linux.
(i don't typically run TS under XP but I've been working a serial speed issue under linux which is resolved now)