MS3 pre-1.4 alpha 6 released

Post by **jsmcortina** » Sat Sep 27, 2014 7:43 am

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

Who should use this code?
Experienced users wanting to test the new features.
This particular code is being released as a fix for a specific Nissan CAS misfire issue.

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 5

Bug fixes:
Properly limit integral sum for boost PID.
Re-ordered injector event array update code to resolve SR20 (and other) injector issue. *

New / changed features:
Add the beginnings of engine state tracking.
Add setup mode for closed loop boost control. It zeros out PID gains so bias table can be tuned
like an open-loop table.

Minor / internal:
-

* The specific issue fixed here is likely to impact other wheels where you are running sequential fuel and the number of teeth per 720 degrees is equal to the number of cylinders. e.g. Nissan SR20, Nissan RB25, Optispark.
I do not believe there is any impact on other wheel modes that use a decent number of teeth (36-1 etc) or on wheels where both edges of the teeth are used (e.g. 4G63)
EDIT: The symptoms of this problem was that at certain injection angles/loads/RPMs (when the start of an injection pulse aligned with a tooth edge) there was a miscalculation that could cause an injection pulse to be missed. This would be observed as a misfire.

This firmware has been released ahead of schedule due to the misfire bugfix. There are other changes that were planned for alpha6, but will now be in future releases. Feel free to post up with any existing issues you have, that appear to have slipped off the radar.

The firmware zip is available from:
http://www.msextra.com/doc/ms3/files/al ... alpha6.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

sheek · Post by **sheek** » Sun Sep 28, 2014 8:37 pm

cant wait to test this out

especially with the rb25 miss at 2800 rpm

hardline · Post by **hardline** » Tue Sep 30, 2014 8:44 am

I'll be testing this out this weekend on the Zetec decoder.

tpsretard2 · Post by **tpsretard2** » Wed Oct 01, 2014 7:49 am

I have installed this version before going to a client this morning.
I am using the subaru 6/7 decoder, for the 15 min drive i believe that there is a noticeable difference in the running of the engine. Something i was fighting thinking it was a tunung problem has almost gone.

Will continue to test...

shaodome · Post by **shaodome** » Wed Oct 01, 2014 4:43 pm

Ah great! This was the issue we were talking about @ DIY HQ then?

I'm in the middle of an install on an SR20 right now. I'll give it a go on the stock trigger wheel first (I was buying the DIY disc with each SR install by default).

Post by **jsmcortina** » Thu Oct 02, 2014 5:51 am

shaodome wrote:Ah great! This was the issue we were talking about @ DIY HQ then?

Yes.

Talking face to face gave me a much better understanding of the problems you had been seeing and I was then able to replicate it on the bench.

James

Matt Cramer · Post by **Matt Cramer** » Thu Oct 02, 2014 6:11 am

We are testing the new firmware on an SR20DET car here. I think Ben has the latest results.

hardline · Post by **hardline** » Sun Oct 05, 2014 3:54 pm

Only issue I have seen so far is that Overboost protection is always activated. I turned it off and my no start issue went away.

Post by **jsmcortina** » Sun Oct 05, 2014 4:06 pm

hardline wrote:Only issue I have seen so far is that Overboost protection is always activated. I turned it off and my no start issue went away.

hardline · Post by **hardline** » Sun Oct 05, 2014 8:09 pm

Here is my tune, I'll have to go get a datalog of the issue

shaodome · Post by **shaodome** » Mon Oct 06, 2014 7:49 am

the lower RPM miss (3000ish) on the SR20 wheel decoder is gone. The car I tuned Saturday, didn't have very big injectors, so we stopped at 270whp, thus we didn't check for the higher RPM load, but it seems like it is fixed.

As for the overboost, works fine for me. Are you sure you aren't talking about boost tolerance?

jabbatron · Post by **jabbatron** » Sun Nov 09, 2014 2:37 am

..........

Post by **muythaibxr** » Mon Nov 10, 2014 5:43 am

It is a method of tracking the engine's state to see if it is in cruise, idle, accel, decel, overrun, etc. Then all the features that currently ask for a bunch of similar settings will have those settings removed and use the engine state to trigger instead. The idea is that those settings will be set once and tuned to give the right behavior before enabling any advanced features that depend on them, and we should end up woth more consistent behavior.

prof315 · Post by **prof315** » Mon Nov 10, 2014 8:26 am

NICE!

Post by **muythaibxr** » Tue Nov 11, 2014 5:27 am

Right now it is enabled and you can set the settings but no other features are tied to it. I wanted to see some datalogs before doing the rest.

ashford · Post by **ashford** » Tue Nov 11, 2014 7:06 am

i have a 2 speed fan, using normal fan settings for low clt>195 and a spare out for clt>205 or/OR bit 128(ac on). will this affect its operation?

juansh2385 · Post by **juansh2385** » Wed Nov 12, 2014 7:48 am

Same as ms2 the code have support for 5 bar sensors but the fuel load maximum is 400 kpa

Post by **jsmcortina** » Wed Nov 12, 2014 7:55 am

juansh2385 wrote:Same as ms2 the code have support for 5 bar sensors but the fuel load maximum is 400 kpa

Same user settings change needed as MS2.

James

julian944 · Post by **julian944** » Sun Nov 23, 2014 1:21 am

Hi James,

I might found a small bug. In boost Control settings, I've activated specific launch duty/target, and said boost target is 400kpa. (I'm using closed loop boost control). But I guess boost target gets divided by 10 because boost target goes to 40% when activated.

Regards Julian

Post by **jsmcortina** » Sun Nov 23, 2014 5:13 am

I've confirmed this launch boost target bug and it will be fixed for the next alpha.

EDIT: It looks to be a mistake in the ini file:
boost_launch_target = scalar, U16, 702, "kPa", 1,0,0,{loadhigh},0
should be
boost_launch_target = scalar, U16, 702, "kPa", 0.1,0,0,{loadhigh},1

James

Megasquirt Support Forum (MSEXTRA)