MS3 pre-1.4 alpha 7 released

[jsmcortina]

To announce the release of "MS3 Pre 1.4 alpha 7"
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 6
Bug fixes:
Hitting rev limiters disables EGO correction.
Alter CAN passthrough behaviour. Only send second packet after remote has replied.

New / changed features:
Subaru 36-2-2-2 VVT has its own ignition mode.
On/Off outputs - use "hyst" setting as match with bitwise AND. *CHANGED BEHAVIOUR*
Sequential shift cut can cut fuel also.
Pit lane limiter.
Changes to Flex input code, so it works harder to reject rogue data.
Flex blending: AFR, WUE, ASE, CrankPW, Overboost, boost CL, boost OL, fuel, spark, Accel-pump AE, Time-based AE
Traction control LED.
Allow VVT with Daihatsu 3cyl. (actual VVT untested.)
Add preliminary support for 2zz-ge VVT (in 2JZ VVTi)
Add slipxtime to outpc.
Extend nitrous curves to 10 points.
Extend launch retard to 10 points.
Add VSS based progressive nitrous.
Variable tacho output.
Add CANIN indicators.
Allow PORTA, PORTB, CANOUT1-8 outputs to be I/O tested.

Minor / internal:
Add a couple more checks for pending interrupts.
Change greying of boost bias2 - only for two channel boost, not switching.
ini fix for ign3 greying
Re-arrange memory usage page28
Add bitmasks to ram4.no_cyl or use num_cyl
16bit freq option for swpwm.

Known bugs
EDIT: There is an ini error for the progressive nitrous curves and they won't work.

The firmware zip is available from:
http://www.msextra.com/doc/ms3/files/al ... alpha7.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
(EDIT: removed spurious comment about Nissan CAS that related to alpha6)

[gurov]

Add CANIN indicators.
Allow PORTA, PORTB, CANOUT1-8 outputs to be I/O tested.

yay, i had to do some weird things when developing with CANBUS to get the status of these. awesome !

[nathaninwa]

Thanks James. I will get this tested out for sure Thankyou. I need to verify I have the inputs, can I share my clutch input, I do not use flatshift, just launch control.

Edit, and thankyou for tacho flexabilty, mines been off 100 rpm since install.

[jsmcortina]

Share it with what? Generally sharing is not permitted.

James

[nathaninwa]

I was thinking sharing the clutch switch input for launch control with the pit limiter. I'll be able to get to the car tomorrow and probe out inputs, and looking over my list I should have my old flex input abailalble

[franksidebike]

Hi James
Is this OK?
Whenn I open my .msq from ms3-pre1.4alpha2 the "Boost Control Bias Duty 2" Tabel is greyed out!

2014-10-14_10.58.34.msq

Sequential shift cut can cut fuel also.

Thank you for Fuel Cut
Frank

[jsmcortina]

Hi James
Is this OK?
Whenn I open my .msq from ms3-pre1.4alpha2 the "Boost Control Bias Duty 2" Tabel is greyed out!

What were you hoping to use it for?

James

[franksidebike]

What were you hoping to use it for?

You mean the "Boost Control Bias Duty 2" Tabel?

I have "Blend Curve (6) Boost 1-2"!
Read the "Boost Control Targets 2" the "Boost Control Bias Duty 1" Tabel?
Frank

[jsmcortina]

I have "Blend Curve (6) Boost 1-2"!
Read the "Boost Control Targets 2" the "Boost Control Bias Duty 1" Tabel?
Frank

Boost channel 1 always uses bias table 1. I changed the greying to match what the code was doing.

James

[elaw]

I have "Blend Curve (6) Boost 1-2"!
Read the "Boost Control Targets 2" the "Boost Control Bias Duty 1" Tabel?
Frank

Boost channel 1 always uses bias table 1. I changed the greying to match what the code was doing.

James

Ah... I was confused about that as well. Thanks for the clarification!

[93supercoupe]

super excited about trying the Pit Lane Limiter as a rolling anti lag. Possible testing tomorrow afternoon

[piledriver]

I'm delighted to see the flex blending working on ~everything it needs! Awesome!
(I think that was only breifly mentioned as a desire in a small thread, quite recently, too)

Trying to get woked up enough to go out in the dark and pull my ECU to reinstall my now repaired MS3, this provides more incentive.

[93supercoupe]

The traction indicator- that is only LED out put? theres no on/off indicator in TS? I see that you can display traction timing retard, but no other traction control related field?

[jsmcortina]

There's an "indicator" for traction active. For alpha 8 I added TC slip*time as a gauge also. It is loggable but not displayable in alpha7.

James

[93supercoupe]

Pit Lane Test.msl

So just got back from testing the new alpha7

I tested the pit lane limiter and traction control.

Traction Control:
Im not sure this is specific to the alpha7 release, but it would not respond to the boost duty table in the reactions. It would respond to the spark retard table, but all that would do is raise the boost the more it spun because of the lower timing values.

Pit Lane Limiter as Rolling Anti Lag:
Works great. Didnt get too much time to play with the settings but this is what ive learned.
I only tried RPM and Hold
1.using spark cut makes it pretty difficult to keep it smooth. I tried messing with the RPM window and also the sensitivity slider, but could never get it smooth enough.
2.using spark retard works amazing, but it increased speed. Im pretty sure its because my RPM window was too big and in my log, i didnt even have it engaged long enough to hit its rpm window limit.
3.Overall it works great. What a difference for a turbo car. Makes for a wild ride when you release the button!!!

[93supercoupe]

Heres another log of the Pit lane, this time using spark cut

RPM based
Holding
Spark Cut
0 retard
no fuel cut

My concern here is the lean condition created before the release of the button. This could just be my VE table going into areas normally never achieved, although i have not looked yet. As you would expect with a 0degree retard, it made less boost. It still made boost, but less. I could probably get it to make more by adding some ignition retard, but i dont feel comfortable doing that unitl i can get rid of the lean condition im experiencing with the spark cut.

[jsmcortina]

Spark-cut will always create a "lean" condition in the exhaust because raw fuel and fresh air are going past the O2 sensor.

James

[93supercoupe]

thinking back to my previous dealings with a spark cut type limiter, i realized thats probably what was happening.

Im going to keep playing with the settings. Ideally, id like to have the smoothness of just the spark retard, but the holding accuracy of the spark cut, but im not sure thats even possible.

Any thoughts on the traction boost table not responding?

[jsmcortina]

Traction Control:
Im not sure this is specific to the alpha7 release, but it would not respond to the boost duty table in the reactions.

I think I've found what's going on here and will work on it for alpha 8.

James

[jsmcortina]

Any thoughts on the traction boost table not responding?

I sent a test code to your forum registered email.

James