MS3 pre-1.5.1 beta 4 firmware released

[jsmcortina]

To announce the release of "MS3 pre-1.5.1 beta 4" this fixes some bugs in "MS3 pre-1.5.1 beta 3". This is hopefully the final beta before 1.5.1 release.

Who should use this code?
Users wanting to test the new features or as directed by tech support to workaround known issues in 'release' version.

Who should not use this code?
Unless directed by tech support, new or casual users should use the current release code instead – see the Downloads page linked above.

Main changes since pre-1.5.1 beta3 firmware
Bug fixes:
Fix memset of vars2, was wiping Dome Bias and more.
Dome closed-loop was interfering with injector outputs.
Prevent MAP going negative.
3-step, transbrake, line-lock staging config code only runs when Launch system enabled

New / changed features:
Simplify Engine States by removing redundant "Fast Accel/Decel" settings.
Closed-loop Dome: change behaviour to use Bias value when beyond lowerlimit and baro when off-boost.
Don't operate dome control outputs when in I/O testmode.

Minor / internal:
Tweak on dp_adding ini entry.
ini PID typo correction.
Var renaming in MAP, MAF, TPS calcs. Should have no effect.
Change default ECU temperature calibration for Ult and Evo.

The firmware zip is available from:
http://www.msextra.com/downloads/dev/ms3/1-5-1/beta-4/

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.4.x
Users upgrading from 1.2.x or earlier codes need to pay more attention.
TunerStudio 3.0.16.6 beta or later is REQUIRED.
TunerStudio 3.0.18.09 beta or later is recommended for reliable SDcard readback.

Go ahead and use the built-in firmware loader on the Tools menu of TunerStudio 3.0.x - you'll like it.

[jsmcortina]

Has anyone tried this yet? Please report results.

James

[nathaninwa]

I loaded this into my tow rig James, MS3pro on a fairly stock 454. Worked great on a 4 hour haul today but don't use any of the changes, so for me nothing to report. I did not load this in the race car, but can for the next race I have coming up on Saturday, July 15

[Reverant]

Has anyone tried this yet? Please report results.

James

I want to try this on a customer's bike but I need to be able to revert back to 1.4.0 after testing, I assume there's no issue with that?

[jsmcortina]

Should be fine.

James

[krisr]

I got it loaded into mine just now, car fired up without issue. I'm waiting on 2 new wideband sensors before I do any driving though as i've just changed the torque converter and fuel pump so things are out of whack now. Will report back later today if the post man brings me the goods!

[krisr]

No issues here. Good solid 1/2 hour on the code, car runs just as good as it did before.

[fwman1]

I used the beta3 release for clbc pid logging to solve my clbc issue(Thanks!). Just curious if the INI PID typo correction in beta 4 will have any impact on clbc?
I like the idea of the simplified engine states, but don't want to have to redo my clbc settings.
Thanks again.

[prof315]

So far so good on an 04-05 Mazdaspeed Miata PnP Pro

[nathaninwa]

Another 4 hours in my tow rig and put 6 passes on the code in my race car. Nothing to report on my end

[jsmcortina]

I used the beta3 release for clbc pid logging to solve my clbc issue(Thanks!). Just curious if the INI PID typo correction in beta 4 will have any impact on clbc?

There is no code change, it is a spelling correction on the screen only.

James

[puntogt4]

I have problem for VSS1 setup,
on my car is connect to PT4 and i don't read any speed,
but if I set shaft speed to PT4 and high speed setup like on my MSQ I'm able to read the rpm's
now I cant go back to my old version because i lost the firmware -_-
Nobody have same problem to rat the speed from PT4 input?
on attach msq and relative log

[nathaninwa]

Question about the transbrake/launch features being disabled with vss, does this also apply to the bump box input? I'm assuming it's all tied together and would like to use the bump box button for boost table switching as well once I'm into high gear. I know I can use a relay and program an output of some kind but would rather just tie the grounds together and simplify the wiring

[puntogt4]

I have problem for VSS1 setup,
on my car is connect to PT4 and i don't read any speed,
but if I set shaft speed to PT4 and high speed setup like on my MSQ I'm able to read the rpm's
now I cant go back to my old version because i lost the firmware -_-
Nobody have same problem to rat the speed from PT4 input?
on attach msq and relative log

Today I load a old beta, 14.2, and vss come back again, I think the problem is on PT4 input, because by choose it for vss you can't set high option "speed input", like shaft speed, if there you don't set "high speed" I don't see any speed on tuner studio

Inviato dal mio HUAWEI NMO-L31 utilizzando Tapatalk

[whittlebeast]

I tossed 1.5.1 Beta 4 into the car and a couple of things jumped out. GEGO only worked when I was using the authority table. Fixed authority did not work. Flat line 100 GEGO, I tried PID and simple.

I run blended VE tables. VEAL would do adjustment on table 2 but the GEGO correction was not homing in on 0 correction.

I plan to race on this code this weekend.

Andy

[nathaninwa]

Interesting. I run the ego table on all my installs. Just switched to fixed authority on my tow rig and ego correction is working fine

[nvr2fst]

I raced on it this ver. over the weekend and it was much better with Dome control! Many thanks for fixing that! No more busting up when commanding high boost.

[whittlebeast]

I did not get a chance to test the VEAL thing. We are suspect it has something to do with my blended tables fueling that I do that is quite rare.

I did race this weekend with the Ultimate on 1.5.1 beta 4 and it ran my ITB motor with no issues.

Andy

[AbatelliCristian]

in testmode, full pump no work if I use PWM fuelpump controll. Is possible?

[Reverant]

I think the fuel pump test mode only tests the on/off relay output and not the PWM output...you need to test the specific output for that?