MS3 pre-1.6 RC 1 firmware

[jsmcortina]

To announce the release of "MS3 pre-1.6 RC 1" (release candidate) this adds a number of changes over "MS3 pre-1.6 alpha 3". Assuming no new issues are found, this code is expected to be promoted to "release" in the near future.

Who should use this code?
Existing users are encouraged to load this code and confirm expected operation.

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

Main changes since pre-1.6 alpha 2 firmware
Bug fixes
Fix 29bit CAN receiving bug where certain IDs were mishandled.
Fix CAN Receiving variable list (CAN PWMin 1 was missing) and offsetting later options.

New/changed features
Add built-in support for Spartan3 CAN wideband.
Add Generic Sensor raw/10 option.

Minor/ internal
Various.

The firmware zip is available from: https://www.msextra.com/downloads/dev/ms3/ms3-1-6/rc1/

** Injector deadtime method has changed since 1.5 and earlier codes. You MUST check and reset your deadtime. **
** Honda K24A2 / TSX/D17 changes **

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.1.xx or later is recommended for correct serial validation and SDcard format operation.

[ShirtUser]

Thanks for doing this. I appreciate the time that it takes.

I'm curious why the maximum mafflow multiplier changed from 585 to 573 in 1.6:

viewtopic.php?p=598220#p598220

[Suprazz]

It's really nice to see new firmware.

New injector deadtime is great and canbus spark adjust over can receiving.

Is there a way to display CAN ADC values without linking it to generic sensors inputs? I would be great to have them available in the right click menu of tunerstudio when you're customizing the dasboard.

I have few other suggestions:
- When using spark mode 2jz vvti, it would be great to have the option start wasted cop to be available.
- I would be great to be able to have different safety shutdown between afr and oil pressure.

[atias]

boost control lower limit delta don't work like it should, it holding the bias value duty cycle up to the threshold before the target boost instead of 100 duty cycle.
single solenoid, closed loop, basic mode.

and the internal data logger records some crazy numbers on some of the channels

ms3pro gen 1

[jsmcortina]

Tune and logs please.

James

[atias]

internal log with messed up fields (was all good at 1.5.2 before update to latest)
pc log that show the lower delta issue
boost controller setup pic

thanks..

[jsmcortina]

boost control lower limit delta don't work like it should, it holding the bias value duty cycle up to the threshold before the target boost instead of 100 duty cycle.
single solenoid, closed loop, basic mode.

That's by design, the "boost builder" full duty only happens once per arming (I forget the exact conditions) and after that the bias is used. This is to prevent over-boosting if you pedal during a race.

James

[LanciaDan]

internal log with messed up fields (was all good at 1.5.2 before update to latest)

I also had problems with the SD log on some fields (on 1.6 alpha 3). viewtopic.php?p=597262#p597262
Maybe the same problem?

[atias]

internal log with messed up fields (was all good at 1.5.2 before update to latest)

I also had problems with the SD log on some fields (on 1.6 alpha 3). viewtopic.php?p=597262#p597262
Maybe the same problem?

may be the same error, i installed a flex sensor and added the ethanol fields to the logger just before the firmware update.
tomorrow ill try to remove them and record a log.

[atias]

internal log with messed up fields (was all good at 1.5.2 before update to latest)

I also had problems with the SD log on some fields (on 1.6 alpha 3). viewtopic.php?p=597262#p597262
Maybe the same problem?

tomorrow ill try to remove them and record a log.

nope )-:

[PhoB]

Also notieced problems with SD log values with previous test versions(after update to newer version). Just remove all variables/fields. Make test log with some basic ones to confirm correct operation. Then add again all you want.

[atias]

played with the SD logger a few hours today.
removed all fields, added some basic fields and its back and running good.
then i added the rest of my fields and the logger got screwed up again .
after that i started to add a few at a time to try find the problem ones, and it seems like its a random combination of a few fields. i think some of the problem is with the fields that start with the letter C (i did groups eliminations by the first letter of the fields, one group at a time ).
after the logger gets screwed, the only way to make it work good again is to remove all fields and start adding again.
in the end i managed to get back most of the fields that i really really need, but the problem is still there.