MS3 pre-1.5 rc 11 released

[jsmcortina]

To announce the release of "MS3 pre-1.5 rc 11" this supercedes "MS3 pre-1.5 beta 10".
It is planned that this "release-candidate" code will be promoted to "release" on Monday. Please test this weekend if possible.

Who should use this code?
Users wanting to test the new features.

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 beta 10 firmware

Bug fixes:
Prevent MAF lookup from reading illegal address (AW reset issue.)
Use MAFOPTION defines is isr_rtc.s
sync-loss not checked when set to off in CEL.

New / changed features:
-

Minor / internal:
Comment some redundant settings in ini.
Expand Engine State tooltips.
Tweak 'Calculations 1' list.

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

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

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

Boost dome control supplement manual
http://www.msextra.com/doc/pdf/Boost-supplement-1.5.pdf

[jsmcortina]

The required beta version of TunerStudio can be downloaded from:
http://www.efianalytics.com/TunerStudio/beta/

James

[arran]

Edit - updating to the required beta version of tuner studio, this resolves the problem.

Using the normal TS version results in the below error and the tune can't be loaded back into the MS

Updated to 1.5 rc11, went fine until attempting to load my project. Tuner Studio is reporting the following. I only just updated it to 3.0.16 . I used TS inbuilt firmware loader

1 Errors:
Error: ECU Definition File mainController.ini requires a newer version of this application.
Required Specification: 3.51
Supported Specification: 3.5

Please upgrade to a newer version., Problem at:
[mainController.ini]:[Line:36]: iniSpecVersion = 3.51


0 Warnings:

[arran]

EDIT: turned off the car for 20 minutes while I checked sensor calibrations, didn't change anything, went back to the car started TS and turned on ignition, items below are working! Now to work out the Engine state settings, car is idling well below target, barely running

Now I have the tune loaded, but not yet driven the car, I can see a couple of things in the dashboard that do not look right.
I have front and rear rotor EGT probes, both are reading 0 degrees C. They use JS4 and 5. Ambient is 35 degree C here today, #%#$ too hot
My oil pressure is currently at -18 psi (engine is off), uses EGO2
Fuel pressure is at -12 psi (engine off), uses EXTMap

[jsmcortina]

Please attach before and after MSQ/MSL.

James

[ashford]

im not sure if this is the right place for this but i ran across a behavior issue that has not affected me till my most recent combo.

dashpot is not acting like a dashpot. there is no taper down after a throttle lift. it needs closed loop to pull it back out. typically if i need to i adjust it so the engine dosent bog down on a throttle tap in gear not moving. this resulted in a high idle condition till the car was stopped(vss )

the way it acts now if you have the initial idle table set it just adds to the table. so basically adding to the table as a whole has the same effect. i checked some logs from other cars and the behavior is the same but with no adverse effect like this application. as far as i can tell all versions since the addition of the pid slider does this. can we get the older behavior like it was pre 1.3

[acedeuce802]

EGO is listed twice in any of the drop downs to select an analog input.

Does this just refer to using the O2 In pin as a generic analog input if not using it for wideband?

[jsmcortina]

EGO is listed twice in any of the drop downs to select an analog input.

That should only be on the EGO page. Both do the same thing.

Does this just refer to using the O2 In pin as a generic analog input if not using it for wideband?

Yes.

James

[arran]

I think the cause was low battery voltage.
I had the ignition on for an extended duration and bat voltage sagged into 9 volt region. All the sensors that were misbehaving rely on a powered circuit/sensor to operate. When the car was off for the 20 minutes mentioned below I had it on a battery charger.

EDIT: turned off the car for 20 minutes while I checked sensor calibrations, didn't change anything, went back to the car started TS and turned on ignition, items below are working! Now to work out the Engine state settings, car is idling well below target, barely running

Now I have the tune loaded, but not yet driven the car, I can see a couple of things in the dashboard that do not look right.
I have front and rear rotor EGT probes, both are reading 0 degrees C. They use JS4 and 5. Ambient is 35 degree C here today, #%#$ too hot
My oil pressure is currently at -18 psi (engine is off), uses EGO2
Fuel pressure is at -12 psi (engine off), uses EXTMap

[dontz125]

EGO is listed twice in any of the drop downs to select an analog input.

Does this just refer to using the O2 In pin as a generic analog input if not using it for wideband?

Looking through the lists for generic sensor, I see EGO (ADC5; the V3.0 or V3.57 main board input) and EGO2 (ADC12, on the MS3 DC exansion header). Yes, EGO is available for analogue input when not using the local WBO2 input; EGO2 is always available.

[arran]

Took the car for a drive. The Tunerstudio RPM gauge is reading double the RPM shown on the vehicle's dashboard. The vehicle tacho is showing the correct rpm. The megasquirt however is driving that tacho, so the MS is both correct and incorrect at the same time.

The engine is running but running quite badly, it seems like the fuel calcs are using the incorrect rpm.

Attached msl and msq, this is the first 1MB from cold start heading out for a drive today.
CAS is a nippondenso 24/2. Everything was running fine on 1.4

2017-01-16_18_modified.msl

Arran current tune.msq

[jsmcortina]

Took the car for a drive. The Tunerstudio RPM gauge is reading double the RPM shown on the vehicle's dashboard. The vehicle tacho is showing the correct rpm. The megasquirt however is driving that tacho, so the MS is both correct and incorrect at the same time.

Investigating.

James

[jsmcortina]

Took the car for a drive. The Tunerstudio RPM gauge is reading double the RPM shown on the vehicle's dashboard.

I found the issue and reverted a recent change. If you are able to test today, please send me a PM and I can email a code over right away.

James

[acedeuce802]

Looking through the lists for generic sensor, I see EGO (ADC5; the V3.0 or V3.57 main board input) and EGO2 (ADC12, on the MS3 DC exansion header). Yes, EGO is available for analogue input when not using the local WBO2 input; EGO2 is always available.

I should've clarified this is using the MS3pro ini. Both are listed as EGO. I don't believe there should be a second EGO option, since MS3pro just has O2 In, Analog In 1, 2, and 3. I feel like this input should be called "O2 In" since that's what the pin is labeled as in the documentation.

[jsmcortina]

I feel like this input should be called "O2 In" since that's what the pin is labeled as in the documentation.

Good call.

James

[jsmcortina]

I fixed the 2-rotor issue and changed that input pin naming. Those changes are in "1.5.0 release" due shortly.

James

[arran]

Hi, any update? Car's broken

[jsmcortina]

Did you see this?

I fixed the 2-rotor issue and changed that input pin naming. Those changes are in "1.5.0 release" due shortly.

James

[arran]

Yep, right around the same time I saw this.
PM was sent per your request. If the plan changed please let me know and I'll spend the time and roll back.

I'm just trying to help

Took the car for a drive. The Tunerstudio RPM gauge is reading double the RPM shown on the vehicle's dashboard.

I found the issue and reverted a recent change. If you are able to test today, please send me a PM and I can email a code over right away.

James

[chips60bug]

Yep, right around the same time I saw this.
PM was sent per your request. If the plan changed please let me know and I'll spend the time and roll back.

I'm just trying to help

Took the car for a drive. The Tunerstudio RPM gauge is reading double the RPM shown on the vehicle's dashboard.

I found the issue and reverted a recent change. If you are able to test today, please send me a PM and I can email a code over right away.

James

I don't spend a lot of time on the general ms3 page, but it would be worth your time to go over there. 1.5 has been officially released now. Link is over there.