MS3 pre-1.4 rc 17 released

[jsmcortina]

To announce the release of “MS3 Pre 1.4 rc 17″ (release candidate)
ETA on this 1.4.x code becoming release is a week or so.

Who should use this code?
All users are welcome to try this code, but do upgrade to the full “release” version when it comes out.

Main changes since pre-1.4 rc 16
Bug fixes:
Allow min/max duty setting when O/L boost.
CANEGO rounding.

New / changed features:
-

Minor / internal:
Add loop to datalog set.
ini tweaks for tooltips.

Known bugs
-

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

Be sure to read the README.txt and RELEASE-NOTES.txt that are supplied in the zipfile.

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.3.x
Users upgrading from 1.2.x or earlier codes need to pay more attention.
TunerStudio 2.6.x is REQUIRED.

[jsmcortina]

This version also links to an updated version of the TunerStudio Reference Manual for 1.4.x. Please use the embedded Help menu within dialogues to automatically download the new version and confirm it is working ok.

James

[nathaninwa]

Firmware loaded and tomorrow is about a 7 hour round trip poker run

[Reverant]

CANEGO rounding.

Can you please elaborate on this one?

[jsmcortina]

When fetching EGO values over CAN from an IO-x the value is rounded instead of truncated.
e.g. 14.46 -> 14.5 instead of 14.4.

James

[Reverant]

Ah ok great.

[ashford]

ill give this a shot on the coyote today

[nathaninwa]

About a 10 hour run today without a hickup. Didn't try any launch stuff but drivability, boost and all the odd stuff I'm running worked. Didn't even hook the laptop up

[richyvrlimited]

I don't think the Crank to run taper is working properly. It worked fine a few RC's ago.

I'll test the 1.3 release tonight just to confirm.

http://www.msextra.com/forums/viewtopic ... 97#p444497

[jsmcortina]

I don't think the Crank to run taper is working properly. It worked fine a few RC's ago.

Nothing has changed there for a very long time.

James

[shaodome]

The max EGO correction KPA value is still fixed at 300kpa. Can this be connected to the max KPA setting for the map sensor in use?

[phoenix3d]

Hi James.. Sorry but not sure if this would be the correct place to post this...

Regarding the New 1.4 Manual.. I see that the Updated Tacho output with variable output is not in the 1.4 manual... yet...

Kindest Regards
Gordon.

[jsmcortina]

Hi James.. Sorry but not sure if this would be the correct place to post this...

Regarding the New 1.4 Manual.. I see that the Updated Tacho output with variable output is not in the 1.4 manual... yet...

Just fine to post here. Yes, sounds like I need to review every single page of the manual.

James

[AbeFM]

Er, I'm not sure if it's something I'm doing, but I get no VVT control. Running a miata 36-2 set up. VVT worked before.

I SUSPECT the change happened when I went to the 36-2 set up. Either way, the timing sits at 271.1 or whatever the minimum is, and doesn't move (vvt1 angle). If I go into test mode, I can get the cam to advance (motor runs off) but the numbers aren't changing.

I'm not sure what might help, but am attaching an msq.

[AbeFM]

Ah, well, no need to stop the presses. I was testing out an alternate Cam Pos Sensor and for some reason it was only producing singlets. The "double tooth" on the cam was being missed.

The troubling part: Why didn't this show up as a lost sync? I drove around a tank or two of gas and aside from "the car really doesn't like this weather" or "It's kinda down on power today", there was no indication. This doesn't speak volumes of praise for how in-tune I am with my motor, but it does highlight something that probably could use fixing?

Anyway, let me know if there's anything I can do. I've yet to bench test the sensor, though I could.
-Abe.

[jsmcortina]

No datalogs.

James

[AbeFM]

A button in tuner studio to export the right sized file for export would make this a lot easier. For that matter, something that said how long file will be before you save it would help. It's always three or four tries to make a log, hence less of them uploaded.

The tooth log has some with OEM sensor, then later some with alternate sensor - showing the different behaviors.

[ashford]

sorry for being late, i tried it on the coyote initial testing shows no different behaviour.

on a side note i tried out the spare out AND feature it works now if both threashold and hyst is set the same. did notice a strange behaviour though, in certain circumstances it appears the wait time for the ac clutch control is also added to the fan after the clutch engages

[jsmcortina]

The troubling part: Why didn't this show up as a lost sync? I drove around a tank or two of gas and aside from "the car really doesn't like this weather" or "It's kinda down on power today", there was no indication. This doesn't speak volumes of praise for how in-tune I am with my motor, but it does highlight something that probably could use fixing?

I checked the datalog and it shows half-sync only. i.e. no cam-sync.

James

[AbeFM]

Thanks! I'll have to add an indicator for MSDroid.