MS3 pre-1.4 alpha 8 released

[jsmcortina]

To announce the release of "MS3 Pre 1.4 alpha 8"
ETA on this 1.4.x code becoming release is 6 months.

Who should use this code?
Experienced users wanting to test the new features.

Who should not use this code?
New or casual users - please use the current release code instead - see the Downloads page linked above.

Main changes since pre-1.4 alpha 7
Bug fixes:
Respect Nitrous +12V polarity. **Beware changed behaviour**
Changed: Traction, 3step, TCLU-en, TCLU-brake, LTT, Dualfuel, tableswitching.
TC / OL-boost wasn't working.
Launch boost target was incorrectly scaled.
VVT temp vars volatile.
Fix bug where EGT warning triggered maxAFR in error.
Fix bug where EGT added fuel was still added when PW=0.
EGT shutdown also stops nitrous
Complementary VVT output channels 3,4 weren't being initialised for BMW S54
Correct ini addresses for progressive nitrous data (was misaligned in alpha7)

New / changed features:
Respond to EGT per cylinder.
Adjust Coyote ref angles for VVT1, VVT3.
Knock - respond per cylinder.
Change ALS behaviour for output, PWM output and idle-up. All three active when switch is active and all conditions are met regardless of TPS.
Over-run allows progressive cut and return with staging if it is inactive.
Set VVT angles to min/max as appropriate at init.
Tweak for VVT impossible angle handling.
Add three loopback 'outputs' to programmable on/off outputs
Add some triggers for GM7X 4cyl seq (untested)

Minor / internal:
Add slip*time gauge.
Add more dome code. Compiles but unfinished and untested.
Properly set dome output duties (convert from 1 PID output to an "empty" output and a "fill" output).
Move some of the new ram vars to v2 area of RAM. No more room in main RAM.
Get rid of some main RAM vars that were either unused, or didn't need to be main RAM vars
Add compile-time validation of flash page sizes. (Top of main.)
Move alternator curve settings.
Remove duplicated CANIN/CANOUT dash gauges.

Known bugs
-

The firmware zip is available from:
http://www.msextra.com/doc/ms3/files/al ... alpha8.zip

Be sure to read the README.txt and RELEASE-NOTES.txt that are supplied in the zipfile.
Some of the ini changes will result in harmless warnings when loading MSQs from 1.3.x
Users upgrading from 1.2.x or earlier codes need to pay more attention.
TunerStudio 2.6.x is REQUIRED.

James

[franksidebike]

Good morning James
In MS3 Pre 1.4 alpha 8 i have the same problem with the "Boost Control Bias Duty 2 Tabel" !
When i set in TS = Boost Control Setings>Boost Tabel Switching>Blend Curve6
i have no "Boost Control Bias Duty 2 Tabel"!
Frank

[nathaninwa]

I blend boost tables too. I'll load tomorrow and report back as well

[MBC-RACING]

Any hope for at max pressure for Nitrous, function in the future. A function that disables NOS above af given Pressure.

[jsmcortina]

Good morning James
In MS3 Pre 1.4 alpha 8 i have the same problem with the "Boost Control Bias Duty 2 Tabel" !
When i set in TS = Boost Control Setings>Boost Tabel Switching>Blend Curve6
i have no "Boost Control Bias Duty 2 Tabel"!
Frank

Same as in alpha 7. Boost control channel 1 always uses bias table 1. I recently changed the TunerStudio greying to match what the code was doing.

James

[jsmcortina]

Any hope for at max pressure for Nitrous, function in the future. A function that disables NOS above af given Pressure.

That is implemented in conjunction with launch - there's a "max MAP during Launch" setting - it will allow nitrous to spool the turbo. Is that what you were after?

James

[franksidebike]

Sorry James
I do not understand you?

Same as in alpha 7. Boost control channel 1 always uses bias table 1. I recently changed the TunerStudio greying to match what the code was doing.

James

In my Setting the "Boost Contrl Target Tabel2" read the "Boost Control Bias Duty Tabel1".
Is that right?
Frank

[jsmcortina]

Sorry James
I do not understand you?

Same as in alpha 7. Boost control channel 1 always uses bias table 1. I recently changed the TunerStudio greying to match what the code was doing.

James

In my Setting the "Boost Contrl Target Tabel2" read the "Boost Control Bias Duty Tabel1".
Is that right?
Frank

For boost blending - YES.

James

[nathaninwa]

Thanks James, that actually makes it easier tuning the boost bias table in blend mode

I'm also liking the egt per cylinder option. I might just have to run that on the current ls3 build project

[jsmcortina]

Do remember that the EGT safety feature is only intended as a band-aid. If it trips... fix the tune before the next run.

James

[franksidebike]

Sorry James
I do not understand you?

Same as in alpha 7. Boost control channel 1 always uses bias table 1. I recently changed the TunerStudio greying to match what the code was doing.

James

In my Setting the "Boost Contrl Target Tabel2" read the "Boost Control Bias Duty Tabel1".
Is that right?
Frank

For boost blending - YES.

James

Ahhh thats great
Frank

[MBC-RACING]

Any hope for at max pressure for Nitrous, function in the future. A function that disables NOS above af given Pressure.

That is implemented in conjunction with launch - there's a "max MAP during Launch" setting - it will allow nitrous to spool the turbo. Is that what you were after?

James

Well sort of. I still want to run Nitrous out of launch until a certain map level. I will lose boost at gearchange, and would love for nitrous to help recover.

[piledriver]

I changed the min time for overrun fuel cut back to zero in the .ini (and then in TunerStudio) and it works just fine, no longer sounds like a firefight when I shift or decel.
The previous min time was .5 seconds.

The progressive return makes the transition smooth, and the actually functional fuel cut seems to the let RPM drop faster on shifts.

I can't see the upside of the .5 second delay default/minimum from here.

[jsmcortina]

I can't see the upside of the .5 second delay default/minimum from here.

Many users try to use over-run with conditions that can trip in driving accidentally. The delay prevents this. I'm not aware of anyone else wanting zero delay before.

James

[piledriver]

I can't see the upside of the .5 second delay default/minimum from here.

Many users try to use over-run with conditions that can trip in driving accidentally. The delay prevents this. I'm not aware of anyone else wanting zero delay before.

James

I recall you fighting hard to get that working properly on MS2.

Immediate fuel and spark cut for shifts and decel is critical.
The soft return solves all ills, and unless you set the MAP value to high so it fights with the idle settings it's NBD.
(inhibiting fuel cut when CL idle is engaged would solve that)
At least it was just an .ini limitation.

I don't recall ever intentionally NOT running a zero delay.

I have a very short exhaust setup with ~no tailpipe, so If i'm spewing unburned fuel for that half a second, it sounds like I'm taking shots at folks with an automatic
For everyone else, they are just wasting fuel.

I cannot visualize any scenario where blowing raw fuel into the exhaust would be a feature for any length of time.
Any non-zero delay does exactly that even if you don't hear it.

[jsmcortina]

I can't see the upside of the .5 second delay default/minimum from here.

Many users try to use over-run with conditions that can trip in driving accidentally. The delay prevents this. I'm not aware of anyone else wanting zero delay before.

I recall you fighting hard to get that working properly on MS2.

When was this?

The delay for overrun has been there since 2003 or so in MS1/Extra.

Why is there "unburned fuel" in the exhaust? Did you ignition stop working?

James

[piledriver]

Back during the early days of sequential fuel on MS2E.

Ignition at any timing while spraying fuel at ~30kpa when the throttle slams shut apparently does little good.

What purpose does it serve?
I have no issues with smooth transitions, esp with the soft return setup you created.

When I lift, I want it to shut off, now, not half a second later.

I have had it set to zero delay--- had to zet it to zero to get rid of popping, and shifts seem to have improved, but possibly just feel better due to lack of embarrassment due to the rifle shot sounds from my exhaust going away.

I have no exhaust leaks, just ~no tailpipe and the muffler hanging on the collector.
Similar to a motorcycle.

[muythaibxr]

piledriver:

The main use of the delay is so that if you can't get the parameters that enable overrun to enable it when it shouldn't.

Locking it out when CL idle is engaged is fine if CL idle is enabled. But not everyone uses that, and I've seen a number of people who have had issues with overrun engaging when they don't want it to.

You have to be very careful in your tuning to set a 0 delay there and actually have it work without any odd side-effects.

That said, on my own engine I tune close to a 0 delay (.1 sec I think, 0 would probably work though) for similar reasons to you.. if I don't do that (And get EAE tuned right) I end up with popping and carrying on when in overrun conditions but without fuel cut engaged. Not everyone experiences that when in overrun though.

[jsmcortina]

I changed the min time for overrun fuel cut back to zero in the .ini (and then in TunerStudio) and it works just fine, no longer sounds like a firefight when I shift or decel.
The previous min time was .5 seconds.

I checked and it appears that MS3 does and always has had a 0.5 minimum.

James

[piledriver]

I probably just noticed it because I went back and forth MS3>MS2>MS3

MS2 allows zero, and I had it set as such as far back as I can recall.
MS3 has the lower limit in the .ini at .5, but it is only a .ini setting, and easily corrected.

It works ~infinitely better for me at zero. YMMV. No issues, esp with the soft return.

I suggest allowing zero, even in the default is .5.