MS3 pre-1.4 rc 16 released

[jsmcortina]

To announce the release of "MS3 Pre 1.4 rc 16" (release candidate)
ETA on this 1.4.x code becoming release is 1 month.

Who should use this code?
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 beta 15
Bug fixes:
CL boost was 10x too sensitive. Fix it.
CL boost min duty being used when off boost. Now shuts off the solenoid instead.
Fix generic sensors "linear" calc overflow at max range.

New / changed features:
Fiat 1.8 adjust by 4.5deg.

Minor / internal:
SSEM tweak to xgate code for ltch_lmms
Tweak to ini ref deadtime 100%.
Remove some dead code.
Remove unused 'next_txmode'

Known bugs
-

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

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.

[nathaninwa]

So far nothing to report with my setup

[ashford]

there seems to be no change from beta 14 on my end(coyote)
still trying to dial in pid loops, vvt2 and 4 react nicely vvt1 seems to drag ass compared to vvt3, will look closer tomorrow.

something else i noticed i recharged the ac today on beta 14 before i upgraded to 16 i noticed something goofy on both on the spare outputs
i have a 2 speed fan when relay 1 is on fan is on low when relay 1 and 2 are on fan is on high
relay 1 is on normal fan control
relay 2 is on a generic output
conditions are clt > 215 or status7 "AND" 32

it is acting like a NAND when status 7 is 32 the fan is on low when not 32 it is on high( i do this by either ramping the throttle or turning off ac)
if i set clt down lower, fan is always on high when above set threshold reguardless of status 7

if i set status7=32 it acts as it should if nothing else is affecting status7

[Suprazz]

there is an issue with the min duty and maximum duty field not available when configuring the boost control. By default, the value is 0 and 0 I think and this cause an error. To be able to change the min and max duty, I have to enable closed-loop, change the values and reconfigure to open-loop.

[Bmettie]

there is an issue with the min duty and maximum duty field not available when configuring the boost control. By default, the value is 0 and 0 I think and this cause an error. To be able to change the min and max duty, I have to enable closed-loop, change the values and reconfigure to open-loop.

I found this as well

[jsmcortina]

Ungreying those fields should be easy enough. I'll add it to the TODO list for the next RC. EDIT: Done.

James

[ashford]

how hard would it be to have individual pid settings for all 4 vvt's?

[puntogt4]

Hi James,
I load this new pre release but I find a bug,
I can't use single coil and ms3x cam imput, the only way is to use js10
also I find random cofiguration error, sometimes tunerstudio give a configuaration error when all is ok!!
I attach a picture of my setting who make the error and my msq
Francesco

[jsmcortina]

You do have a configuration error, but the message it shows is wrong. EDIT: Actually no...

You have set MS3X cam (PT2) as your datalog button, so you can't use it as the cam input as well.

I'll fix the config message.
EDIT: Second thoughts, the message is ok. It says "Conflict with JS10 / cam input" which is true, there is a conflict on your cam input.

James

[jsmcortina]

how hard would it be to have individual pid settings for all 4 vvt's?

Possible, but it seems like maybe that's masking some other issue. i.e. I wonder if the "noise filtering" that I added is confusing things ?
I had thought about exposing the filtering settings, but generally we try to avoid adding new settings unless really necessary. This could be added as an option on the "special settings" page if you want to tweak it?

Clearly I want to get this to 1.4.0 release real soon, so I'm not wanting to change much.

James

[Bmettie]

I'm still on beta 12 but yesterday I played with idle advance and I noticed that whatever i set the idle advance to, it would retard an additional 2 degrees, ie I set it at 18* and my TS gauge says 16*. I haven't been using idle advance I wanted to see if it would help the CL stepper idle control I just setup. I didn't log it to see if its a TS dash error or not, it was late, I'm going to put a timing light on it today and verify. Has this already been addressed in the latest rc?

[jsmcortina]

[Bmettie]

^ will do, gimme a bit, kids are still sleeping

[Bmettie]

Here they are, I started the log with IA disabled then enabled it, advanced the values in the table, retarded them back, disabled, and enabled IA again, all with Burns after a change. I've looked over settings and such and can't find any gotchas, maybe you'll find something in my settings that is causing this. I verified with my light that it is going to 16* advance.

Edit: I found it, for some reason the last cell in my cold advance was -2.0, obviously user error here. I wonder how long its been like that....

[Bmettie]

I realized what happened, I had changed the coolant values in my WUE table and it automatically changed the values in a few tables to match the WUE table without adjusting their respective setting value. Is there a way to remove the ties between the coolant values in different tables?

[jsmcortina]

A number of tables share the coolant values to make configuration simpler.

James

[allbottlenothrottle]

In the Launch/2Step/3Step/Transbrake settings the turbo staging Digital 4 Switched in 4 is missing as an option. That is what I have used in the past. Has it been renamed or is it missing? Thanks!

[puntogt4]

Hi all
Why I can't find on programmable output the out PK7, PK1 PK3?
i find on test output but no on listo of programmable and no on the generic PWM!
Francesco

[hardline]

Any eta on the stable release? If it is going to be longer than a few weeks, then I'll flash up to this code, but if it is going to be soon, I'll hold out and wait.

[Reverant]

I can't get the "AND" operator to work properly in this release (it worked fine in 1.3.4).

Here's the issue. The 94-05 Miata has 2 fans. I would like the 2nd fan to trigger on a coolant threshold and when the A/C kicks in (status7 AND 32).

I do this through the programmable outputs (injg is the 2nd fan in my setup).

In this release candidate, the 2nd fan in always on UNLESS the A/C kicks in. So it's working like "status7 == ~32" instead.

Watch how porta changes when status7 goes to 32 in the datalog.