MS3 pre-1.5 alpha 2 and 3 released

[jsmcortina]

To announce the release of “MS3 Pre 1.5 alpha 2”

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 the pre-1.5 alpha 1 firmware
(A number of these changes were made in parallel to the 1.4.x code stream.)
Bug fixes:
Generic SW PWM – handle 0Hz.
Subaru 36-2-2-2 VVT could get stuck in a never-sync situation.
EGO was reporting incorrect config error.
Mitigate high-RPM sync-loss noise filter lockout and tweak HEI bypass handling to suit.
dwl_time underflow in ign.c causing incorrect dwell duration with ATDC timing at very low RPMs. *check timing*
Closed-loop boost channel 2 typo fix.
Fix idle bug added when engine states was added.

New / changed features:
Add engine state indictors and tie engine states to idle features, overrun.
Add NipponDenso crosstalk noise filter. On/off settings for now.
Various alternator control
– Alternator load duty input uses more samples for averaging.
– Miata alternator calculates load.
– Alternator tweaks and bug-fixes.
– Change (Ford) frequency alternator control to used time period instead.
– Add “belt snapped” detection to alternator field control.
– Tweak Miata alt load duty code in case it was causing unexplained crash. (It wasn’t.)
Port DBW code from “industrial”, convert to 11bit CAN and test with GM TAC controller. Update DBW CAN messaging to latest proposal.
Add 350Z temp/RPM CAN broadcast. (untested)
Add MAP and EGO to analogue inputs options.
Remove HE351 CAN broadcast option. (Wrong baud.)
Allow SPKI/J on MS3-Pro – PWMout2/3 – need 5V pullup.
Add receiving option for Race Technology DASH2 PRO accelerometer and GPS CAN data.
Fix GPS speed typo. Process GPS data as existing.

Minor / internal:
Add new PPAGE section.
Remove dead code from calc_divider.
Remove debug code from Coyote VVT.
TEXTe0 loader workaround. Copy random_no from application.
Re-work firmware loader to use 1k erase. Required for latest 1.5 code. Check for old monitor.
Tooltip updates.

Known bugs
This firmware cannot be loaded onto early (<=2012) MS3 hardware at this time.

The firmware zip is available from:
( http://www.msextra.com/downloads/dev/ms3/1-5/alpha-2/ )
EDIT: Now superceded by http://www.msextra.com/downloads/dev/ms3/1-5/alpha-3/

Be sure to read the README.txt and RELEASE-NOTES.txt that are supplied in the zipfile.
Some more information on the dome feature is available is this temporary PDF: http://www.msextra.com/doc/pdf/Dome-sup ... -12-02.pdf

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 2.6.x is REQUIRED.

[AbatelliCristian]

DBW James I love you

question :
1 - how ms read pedal position?
2 - the standard tps calibration is refear to pedal or tps?

My idea
is possible MS read pedal and TPS position from external controller CAN?

Thanks!

Cristian

[jsmcortina]

is possible MS read pedal and TPS position from external controller CAN?

It only works that way. The "DBW" feature implemented here is only the throttle target lookup. It REQUIRES an external safety engineered DBW controller with the pedal, throttle and servo connected.

James

[AbatelliCristian]

Yes, I have my controller and at the moment work. I have safety strategy for error PID or error POT.
I can send CAN DATA TPS and Pedal position to MS for use target MS. This semplify the tune....

[AbatelliCristian]

My idea is:

external controller read all pot (tps and pedal) with indipendent strategy for error or recovery. The controller send data to MS (status, position pot... etc).
MS has the sole task of calculating the target and manage the functions IDLE.

[jsmcortina]

My idea is:

external controller read all pot (tps and pedal) with indipendent strategy for error or recovery. The controller send data to MS (status, position pot... etc).
MS has the sole task of calculating the target and manage the functions IDLE.

Yes, that's what it does.

Just to make it clear here for other readers - the MS3 control code is not implemented in a safety critical manner. We make no promises that the commanded throttle position will be timely or accurate. We take no responsibility for loss or damage that results from the use of this feature.

It is essential that any drive-by-wire controller that operates the primary throttle on a motor vehicle is designed to be safe and is implemented to comply with safety critical standards. Amongst other controls, such a system must tolerate and reject any out of range commands from the MS3.

James

[AbatelliCristian]

Where can I find explanations on CAN addresses and data for DBW?

[arran]

Has the Engine State code been activated in this alpha?
Is that what this text in the release notes refers to:?
"Add engine state indictors and tie engine states to idle features, overrun."

I recall that in alpha 1 the code was present but was in a passive state.

Also, does this code have progressive fuel cut/return under Overrun fuel cut for staged injection now?

Thanks

[jsmcortina]

Also, does this code have progressive fuel cut/return under Overrun fuel cut for staged injection now?

No and it is not on the roadmap.

James

[arran]

You could have let me down gently!

This thread here I first asked the question
http://www.msextra.com/forums/viewtopic ... 9&p=396967
Started almost 2 years ago now. Surely there must be Rotary engined customers who would benefit from not having the car surge every time fuel returns from over run cut? Just a wafer thin change...... It seemed to be something you were considering in that thread.

[muythaibxr]

Engine states code is now active.

When I drove a rotary engine car the secondaries came on/turned off with table based staging, and only progressively at high enough load to be needed based on the staging table. You do not need a special overrun feature with table-based staging.

[ashford]

This firmware cannot be loaded onto early (<=2012) MS3 hardware at this time.

what would be the sympoms of this and is it recoverable? i have one of the first retail batch but don't remember what car it is in

[jsmcortina]

This firmware cannot be loaded onto early (<=2012) MS3 hardware at this time.

what would be the sympoms of this and is it recoverable? i have one of the first retail batch but don't remember what car it is in

Firmware loading will fail.

The firmware is now larger than the size that the early version monitor/boot-loader supports.

Authorised agents such Peter Florance, Jean Belanger and I are able to load an updated monitor that will take the firmware. If this size change impacts a large number of customers, it may be possible to write a "bootstrap loader" like MS2 to support these chips with the older monitor.

James

[muythaibxr]

Engine states code is now active.

When I drove a rotary engine car the secondaries came on/turned off with table based staging, and only progressively at high enough load to be needed based on the staging table. You do not need a special overrun feature with table-based staging.

I must correct myself. Apparently progressive cut doesn't work at all if staging is on.

I'll take a look for 1.5.

Ken

[arran]

Thanks!

Yes I'm using table based staging no probs. Over Run Fuel Cut is enabled, but the Progressive return (and cut) isn't supported in combination with staged injection. Without the "Progressive" function, there is a surge as the car decelerates, and hits the lower threshold where suddenly all the fuel for that bin is commanded.

Arran

[Alfagta]

Hello James,

can you tell us how ms wants to have the pedal position as well as the throttle position over can.
I can define a base idetifier.
How should the message look like?

Best Regards

[muythaibxr]

Thanks!

Yes I'm using table based staging no probs. Over Run Fuel Cut is enabled, but the Progressive return (and cut) isn't supported in combination with staged injection. Without the "Progressive" function, there is a surge as the car decelerates, and hits the lower threshold where suddenly all the fuel for that bin is commanded.

Arran

Are you using eae?

[arran]

No, just accel pump AE

[muythaibxr]

EAE can help with that behavior by cutting fuel faster and bringing it back in faster, rewetting the walls. I have been able to tune out surging behavior that way

[shauer]

Firmware loading will fail.

The firmware is now larger than the size that the early version monitor/boot-loader supports.

Authorised agents such Peter Florance, Jean Belanger and I are able to load an updated monitor that will take the firmware. If this size change impacts a large number of customers, it may be possible to write a "bootstrap loader" like MS2 to support these chips with the older monitor.

James

Is there somewhere I can look to determine if I am effected?

I was a beta tester for MS3/MS3X so I'm pretty sure I may be effected although I cannot remember what year I updated to MS3. Is this a design decision that all new firmware will now be too large to be loaded by the old monitor?

I would really prefer not to need to pull my controller from my car and ship the board off somewhere to have the monitor updated.

Thanks