MS3 pre-1.5.2 beta 5 firmware released

[jsmcortina]

To announce the release of "MS3 pre-1.5.2 beta 5" this adds some bug-fixes and improvements over "MS3 pre-1.5.2 beta 4".

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.2 beta 4 firmware
Bug fixes:
Fix SDcard reported size for larger cards.
Ensure overdwell still operable during sync-loss or stall.
Ensure nitrous code runs during sync-loss or stall.
Do apply cel_overboost.
Prevent nitrous timer rollover issue for timed-nitrous lookups.
Prevent launch timer rollover issue for launch retard lookups.
Fix nitrous 'restart' behaviour.

New / changed features:
In closed-loop boost or open-loop dome, do not allow a target less than baro.
Add resync delay feature.
Change EGO to Ideal PID type B. (NB - retuning likely required.)
Debounce launch/transbrake button input.
Check launch pin more frequently.
Change Hemi VVT tooth check points. (untested.)

Minor / internal:
Tweak tooltips on boost tables ref absolute kPas to add note about 100kPa.
Bump up Dome limits to 700kPa.
Tweak transbrake time minimums.
PID log field precision.

The firmware zip is available from: http://www.msextra.com/downloads/dev/ms ... -2/beta-5/

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.28 or later is REQUIRED.

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

[jsiedlicki]

This was mentioned back in beta 4 but must have been missed for beta 5.

The listing for the Internal Baro Sensor in the I/O pins List Showing Usage dialog references the wrong variable. It should reference

Code: Select all

portusage_ad0h[2]

But instead references the variable which represents Analog Input 1

Code: Select all

portusage_ad0h[4]

The same error is in both files.

Code: Select all

displayOnlyField = "Internal Baro Sensor", { bitStringValue( portLabels , portusage_ad0h[4]  ) }

ms3pro-evo.ini on line #7656
ms3pro-ult.ini on line #7699

[jsmcortina]

The listing for the Internal Baro Sensor in the I/O pins List Showing Usage dialog references the wrong variable. It should reference

Code: Select all

portusage_ad0h[2]

But instead references the variable which represents Analog Input 1

Code: Select all

portusage_ad0h[4]

No.
I checked the firmware and the internal baro port IS configured as ad0h[2]. So there must be a different reason that you are seeing a mixup.

James

[jsiedlicki]

No.
I checked the firmware and the internal baro port IS configured as ad0h[2]. So there must be a different reason that you are seeing a mixup.

James

I'm a bit confused. We are in agreement that the internal baro IS on ad0h[2] BUT the ini lists it as being connected to ad0h[4]. Note that ad0h[4] is being refernced by two different inputs in the ini file. Below is the ms3pro-evo.ini as an example. The ultimate has the same issue.

Code: Select all

line #7656:  displayOnlyField = "Internal Baro Sensor", { bitStringValue( portLabels , portusage_ad0h[4]  ) }

line #7678:  displayOnlyField = "Analog In 1", { bitStringValue( portLabels , portusage_ad0h[4]  ) }

Also the Internal Baro Sensor input is listed in both the I/O pins List Showing Usage AND the I/O pins List2 Showing Usage dialogs. Not sure if that is intentional or not.

[jsmcortina]

I'm a bit confused. We are in agreement that the internal baro IS on ad0h[2]

Oops, I misread your post.

James

[techmarcblsx]

trans brake multi bump
when my trans brake is engaged on creep mode, without my "bump" button being pushed at all it is pulsing the trans brake.
if i push the "bump" input button it stops it, this seems backwards from what it was on last 1.4 firmware.
shouldn't have to push and hold two trans brake inputs to hold the car still. nor is this the way its explained in tuner-studio.
tuner-studio says creep mode says holding of the button will cause a series of bumps or steps until the button is released.
absolutely zero changes in the car other than the firmware update.

[jsmcortina]

trans brake multi bump

[techmarcblsx]

my apologies

[jsmcortina]

How is your bump button wired? I see that you are using the "Nitrous" input pin. That (should) expect a 12V signal. I have a feeling that older firmware didn't always respect that polarity and may have worked backwards.

James

[techmarcblsx]

its a ground input just as it was before so bump button from chassis ground to nitrous in and nitrous out to the ground side on the SSR.

[techmarcblsx]

bump input setup

[jsmcortina]

its a ground input just as it was before so bump button from chassis ground to nitrous in

That's backwards. The "Nitrous In" pin expects 12V.

James

[techmarcblsx]

it worked just fine prior to the firmware update, so if i supply the nitrous input pin 12V my problem should be resolved?

[jsmcortina]

it worked just fine prior to the firmware update

The behaviour was broken in older firmwares.

so if i supply the nitrous input pin 12V my problem should be resolved?

Yes.

James

[techmarcblsx]

just spoke with EFI source, im being advised to change my bump input to tableswitch and leave it on a ground

[jsmcortina]

just spoke with EFI source, im being advised to change my bump input to tableswitch and leave it on a ground

That works too.

James

[techmarcblsx]

tried both ways with no luck
nitrous in from a 12V source changes the rate in which the transbrake pulsed, but when you took the 12V away it still pulsed
tableswitch ground switch did absolutely nothing

[krisr]

Just upgraded to b5 from stable to see if the tweaks to the SD card will help my issues. Initial log is fine but will see how it goes when I take the car out. Well done on the changes to EGO feedback, MUCH faster!

[Paul_VR6]

Anyone have good starting values for new ego PID?

[taank]

Tested last night, ego is extremely responsive.
Transbrake creep feature stopped working for me in beta 5