MS3 pre-1.5 alpha 5 released

[jsmcortina]

To announce the release of “MS3 pre-1.5 alpha 5” this supercedes “MS3 pre-1.5 alpha 4”.

Who should use this code?
Experienced 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.5 alpha 4 firmware
Note that many of the bugfixes noted here were deployed in parallel to the 1.4.x code stream.

Bug fixes:
Output test mode over-rides spark cut.
Fix typo that broke Innovate EGO CAN polling.
TC boost duty calc fix.
Allow CAN I/O testing to work.
Split conf_iobox into two pieces to get on/off outputs working again.
Launch+nitrous works from launch input not soft zone.
Change psig scaling for fuel_pressure and fp_drop.
Remove invalid Inj I/J from Hardware PWM list.
Clarify PP/PT usage on “inj1/2” for MS3-Pro.
Protect against INVALID ports in on/off outputs.
Boost target is kPa not %.
Correct pull-up/down setting on JS10 input
Fix ‘=’ condition in on/off outputs (ancient bug)
MAP logger was sending two zeros at end of data.

New / changed features:
Make throttle closed state depend only on the throttle being closed and not on idle state, but make entering PID depend on idle state. Also fix valve closing when close delay is set to 0 but the system isn’t rebooted.
3-wire PWM idle turns off both coils KOEO if set.
Get rid of VSS settings for idle features.
Add WOT engine state
SDcard field selector needs new TS to support all fields in 128 byte mode.
Change smoothing calc for battery voltage to allow better convergence.
Add lookup table for MS3-Pro ECU temperature sensor.
Add more loops
Split CANOUTx and LOOPx into second prog on/off.
Add more pins to I/O test mode.
Tiny tweak to rpmdot calc.
Expose raw VE1,2,3,4 table lookups in outpc.
Add ADC11,12,13 as options to digital inputs.
Change Knock digital input to use standard pin list.
Remove old-style MAF calibration table and correction curve.
Add custom thermistor table.
Integrate dome control with regular boost control. (Needs testing.) Updated docs to follow soon.
Barometer smoothing.
Fan control: add settings for TPS, VSS shutoff and re-arrange settings internally.
A/C idleup: add settings for TPS, VSS, RPM shutoff.
Oil pressure can trigger limp mode (note delay.)
Add check for baro, airden, WUE zeros and give config error.

Minor / internal:
Apply ini tweaks from EFIanalytics.
Overboost tooltip tweak.
Loader tweak.
Tweak ini for engine states to have tool tips.
Create maxspeed in ini and raise it.
Change defaults for MS3-Pro battery calibration.
Increase decimal places for logged target EGO.V and lambda.
Tweak IObox4 defaults.
Add more in/out pin option space.
egocor 13-16 removed and space in outpc re-used.
oddfireang decimal
Implement TS “ini pin option lists” to reduce ini size.
Add nopullup option to digin_setup.

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

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.x 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.

EDIT: Known bugs 5th Nov
Boost/launch setting not working
SDcard SPI comms speed setting not working
VSSout rate setting not working
Alternator output normal/invert not working

EDIT: Known bugs 16th Nov
There's a critical bug that breaks the "Programmable on/off outputs 2" if using MAF.

[jsmcortina]

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

James

[franksidebike]

Hallo James
In "Boost Control Setings" i can no Switch the "Specific launch Duty/Target" to On, is always Off!
Frank

[jsmcortina]

Hallo James
In "Boost Control Setings" i can no Switch the "Specific launch Duty/Target" to On, is always Off!
Frank

Yes, that's weird! Investigating. EDIT: This will require a tiny firmware tweak to fix. I can email.

With the fairly major changes for i/o port standardisation, it is quite possible that a few settings will have problems like this.

James

[whittlebeast]

VE1 thru VE4 raw behaved as expected. I like the firmware loader. The motor is down for about a week but I will test that when a few parts show up.

Andy

[dontz125]

Why does the DBW function only have a CAN output, vs PWM or Stepper?

Nice to see the 'spare' (PK1-PK3-PK7-PM2) pins made available for output.

[jsmcortina]

Why does the DBW function only have a CAN output, vs PWM or Stepper?

MS3 is not a safety engineered product. The DBW functionality requires an external safety engineered control box.

James

[dontz125]

Gotcha. I had wondered what had happened to change the previous mantra of "Oh, heck no!" when it came to DBW ...

[Manu]

Why does the DBW function only have a CAN output, vs PWM or Stepper?

MS3 is not a safety engineered product. The DBW functionality requires an external safety engineered control box.

James

Hi James,

I read about the DBW external controler and I can't figure if the one you drive with MS3 can fit differents DBW or if it can only use the one it done for ?

Regards,
Manu

[jsmcortina]

It's only a proof of concept at the moment. There is no official DBW controller available.

For anyone contemplating one, I'll remind you - you MUST take safety engineering seriously. Even on the race track, things could go fatally wrong if a DBW controller goes crazy.

James

[suberimakuri]

Having had a cable throttle stick full open mid corner top of third in 400ps rx7, I can tell you it's not fun!

[MWPau]

Im having the same issue that i did with v1.5a4, with a lot of the 128 byte log fields always having a value of 0.
Its definitely not sensor issues or similar.
Im also possibly having an issue with boost target table blending. Yet to confirm this though.

I'm going back to 1.4 as i need to have a rock solid reliable tune ready for an event in a few weeks.

[jsmcortina]

Im having the same issue that i did with v1.5a4, with a lot of the 128 byte log fields always having a value of 0.
Its definitely not sensor issues or similar.
Im also possibly having an issue with boost target table blending. Yet to confirm this though.

MSQ + MSL please.

I'm going back to 1.4 as i need to have a rock solid reliable tune ready for an event in a few weeks.

That's a sensible approach.

James

[MWPau]

MSQ + MSL please.

It was too big to attach, so here it is:
https://drive.google.com/file/d/0B1Qz1B ... sp=sharing

Ive included the raw log file from the SD card, to help with working out if its a FW or TS issue.

[MWPau]

On going back to 1.4.1, boost target blending iw working again.
So there is definitely something buggy with it in v1.5a5.
It seemed like it was pulling values from table1, when they should have been 100% from table2.
I cant confirm that theory though by checking the boost target value in the log, as it was one that was reporting constant 0.

[aidandj]

Love the tool tips on the engine state settings. Gives good instructions on how to find the correct values.

Glad to see the oil pressure shutdown settings in alpha. Looking forward to playing with them.

Thanks!

[jsmcortina]

Im having the same issue that i did with v1.5a4, with a lot of the 128 byte log fields always having a value of 0.

I've investigated.

Your log file shows zeros in TEMP2,3,4,5,6, VOLT5, Accel X, VBATT

I broadcasted CAN data to my ECU. TEMP2,3,4,5,6, VOLT5, VBATT all work and datalog ok for me - they aren't zero.

Accel X is a different matter. I notice that you have a Generic Sensor called "Accel X" which is the exact same name as the accelerometer system. This is confusing TunerStudio. I've emailed Phil for his input. For now rename the unused Accel X and Accel Y in Generic Sensors.

James

[jsmcortina]

Also... there is a log issue. Having analysed the contents of the LOGxxxx.MS3 binary file I can see that only the first 48 fields are being logged, even though the 128 byte format has space for them. I've spotted the code that is responsible and I'll test against your MSQ.

James

[MWPau]

Also... there is a log issue. Having analysed the contents of the LOGxxxx.MS3 binary file I can see that only the first 48 fields are being logged, even though the 128 byte format has space for them. I've spotted the code that is responsible and I'll test against your MSQ.

That sounds promising, thanks James.

Sorry, i should have mentioned that then Generic Sensor inputs that are zero probably should be zero.
Those values are coming from some extra canbus hardware im testing.

By the way, TS tells me that i have used the maximum of 64 (i think it was?) logging fields, even though im not using the full 128 bytes of log data.
Can that be easily expanded so the full 128 bytes can be used?

[jsmcortina]

By the way, TS tells me that i have used the maximum of 64 (i think it was?) logging fields, even though im not using the full 128 bytes of log data.
Can that be easily expanded so the full 128 bytes can be used?

There are only 119 bytes available for logging data and most fields are two bytes each. I checked your data by hand and it looks like you have around 14 bytes free, so at least 7 more fields would be possible if the field selector allowed more entries.

James