MS3 pre-1.5 alpha 1 released

[jsmcortina]

To announce the release of "MS3 Pre 1.5 alpha 1"
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 the pre-1.4.1 beta 2 firmware
Bug fixes:
-

New / changed features:
Add boost dome control.
Add 128 byte SDcard logging format.
On/off VVT is now a curve.
Add ski-doo PTEC 24+1+1+1+1 wheel mode. 2-cyl 2-stroke.
Make PW extend mid-squirt if commanded PW increases.
Re-arrange outpc to workaround TS hardcoding for RTC.
Make sync count increment when reason 11 happens.
Add engine-state determination and logging.

Minor / internal:
-

Known bugs
Inconsequential, the firmware rev shows as "alpha 0".

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

Be sure to read the README.txt and RELEASE-NOTES.txt that are supplied in the zipfile.
Some more information on the dome feature is available is this temporary PDF: http://www.msextra.com/doc/pdf/Dome-sup ... -12-02.pdf

Upgrading users are advised to enable the "old baro calc" for backwards compatability.

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 2.6.x is REQUIRED.

[thedrew]

could you guys port the increased SD card logging back to 1.4? I'd love to get that feature sooner!

[muythaibxr]

For engine states, in this alpha, nothing is tied to it, just look at and set the settings, and send datalogs.

I did some bench testing of this tied to a bunch of other features last night, and it looks to me like it will work pretty well.

Ken

[ashford]

i have a few requests if it is not too late
for vvt target tables can the x/y bins for intake and exhaust be seperated. the non linear curves on a coyote are in completely different areas and what i have done is more or less a compromise

have a time after start of a second or 2 before vvt is turned on to let oil pressure be achieved

[dontz125]

The 1.4.1 had the option of 16 cylinders and 16 EGO channels; 1.5.0 still has 16 cylinders, but only 12 EGO channels. What happened?

[jsmcortina]

I took them out to make space for more realtime data in "outpc". This is a workaround due to hardcoding in TunerStudio.

Jamee

[dontz125]

Is this something Phil could address? I assume you mean there are only so many outputs that can be logged ...

[jsmcortina]

Is this something Phil could address? I assume you mean there are only so many outputs that can be logged ...

See http://www.msextra.com/forums/viewtopic ... 0&p=431140

James

[prof315]

Ok I finally loaded this up yesterday. Other than an initial bit of hard start the first time after the upgrade everything seems to be working ok. The Engines states stuff is a great idea. ( I watched the YouTube from this years megameet)

[muythaibxr]

Ok I finally loaded this up yesterday. Other than an initial bit of hard start the first time after the upgrade everything seems to be working ok. The Engines states stuff is a great idea. ( I watched the YouTube from this years megameet)

Can you set the engine state settings the way you think is right and send logs?

I have actually made some tweaks to it and tied it to a bunch of features now in our source repository, and it looks really good on the bench, so I'm looking forward to seeing results.

Ken

[prof315]

Ok I finally loaded this up yesterday. Other than an initial bit of hard start the first time after the upgrade everything seems to be working ok. The Engines states stuff is a great idea. ( I watched the YouTube from this years megameet)

Can you set the engine state settings the way you think is right and send logs?

I have actually made some tweaks to it and tied it to a bunch of features now in our source repository, and it looks really good on the bench, so I'm looking forward to seeing results.

Ken

Certainly Ken I would be happy to.

[prof315]

Here are some logs from my drive home last night. Please let me know if you need something specific.

Jeff

[muythaibxr]

Will take a look tonight.

[muythaibxr]

So the engine states are doing more or less what I expect. The only problem I'm seeing here is that your TPS calibration is off and it's causing "idle" state to briefly get entered when you lift the throttle because TPS is below the threshold you set (1%) but MAP is above the overrun threshold.

Ken

[prof315]

So the engine states are doing more or less what I expect. The only problem I'm seeing here is that your TPS calibration is off and it's causing "idle" state to briefly get entered when you lift the throttle because TPS is below the threshold you set (1%) but MAP is above the overrun threshold.

Ken

Ok that doesn't surprise me. It has to do with the throttle body I am using at present. It's the stock OBD2 throttle that came on the engine and basically it has a bi-directional DC motor that moves the throttle blade for an IAC along with 2 TPS circuits ( one for idle and one for driving) as well as an idle switch. Rest position gives an idle that is a a little too high (its a limp in feature) so I use it from rest to about 50% closed but it makes the TPS a little funky. At the "fully closed/minimum idle" position I have a negative TPS. At some point I am going to switch to a Ford Mustang throttle and ditch the stupid work around but I haven't had the time.

Let me know it you need anything else such as testing new code. My daily drive to work has a little bit of everything.

Jeff

[hardline]

Upgraded this evening. Only issues noted was it seems to run richer on startup. Aside of that, seems fine.

[muythaibxr]

Odd, nothing changed around that.