MS2/Extra pre-3.3.2 beta 3 released

[jsmcortina]

To announce the release of pre-3.3.2 beta 3.

I'm STILL awaiting any feedback on the significant change in pre-3.3.2 beta1 which was a change to the "Toothed wheel" decoder for oddfire and odd cylinder count engines. Megahelp are you out there? Please read your PMs.

Main changes since pre-3.3.2 beta 2
Bug fixes:
Added range checking to flex frequency like MS3.
Restrict possible baud rates to reduce risk of no-comms. (Code from MS3)
Fix egov2 datalogging typo in ini.
Bugfix to normal-AE so MAP-decel cannot trigger if 100% TPS
triggerteeth range
Fix FLEX JS11 config error reversed sense.
Launch could leave fuel-cut on in error if TPS was quickly removed.

New/changed features:
Add boost contol delta from ms3.
Add boost control initial values from MS3.
Boost control, keep valve unpowered (open) until MAP>baro.
Boost control, report actual target instead baro when out of range.
GM bypass handling changed.
GM BYPASS:- Now supports SpkB on Microsquirt.
GM BYPASS:- CPU pin polarity matches main spark polarity - might require re-wiring on MS2 if using JS10
GM BYPASS:- Turn on Bypass output sooner (per user request)
Add PE0/FLEX as a table-switch input option.

Minor/internal:
Add slider to time-based AE
Re-brace normal-AE.
ini tooltip tweak
Tooltip for CL-idle slider.
ini: 'divider' requires power cycle.
Change greying of AFR1/2 on 3D menu.
ini knock units are %

The changes to boost control are discussed http://www.msextra.com/forums/viewtopic ... 34&t=53051

The zip can be downloaded from:
http://www.msextra.com/doc/ms2extra/fil ... 2beta3.zip

EDIT: The latest beta TunerStudio is required from : http://www.efianalytics.com/TunerStudio/beta/

James

[Reverant]

Getting "Conflict with Launch input" if I select any of the remote port inputs. Nothing else is on any of the 0-7 bits.

The same was true with beta 2.

I think this boils down to ms2_extra_init.c, line 1007:

if ((flash4.can_poll != 3) || !(flash4.enable_poll & 0x08) || (flash4.ports_dir & 0x04) || (flash4.ports_dir & 0x40)) {
conf_err = 7;

flash4.can_poll.can_poll = 3 is a deprecated option (ie CAN Board Type: "Generic Board"), it looks like the code should be:

if ((flash4.can_poll != 1) || !(flash4.enable_poll & 0x08) || (flash4.ports_dir & 0x04) || (flash4.ports_dir & 0x40)) {
conf_err = 7;

Comments?

[Reverant]

Confirmed, the fix above works on the bench.

There is also an .ini error for switch tables.

If you select any of the remote ports, for example bit 0, then bit is not used, bit 1 is used. If you select bit 1, bit 2 is used, etc.

If you look at ms2extra.ini, lines 858-865, there is an "INVALID" left at the end of the line for all lines with no comma, this needs to be moved before "Remote Port3 Bit 1" to make it work properly, otherwise its a off-by-one. I did this and again, it works fine on the bench now. Local ports were not affected.

[jsmcortina]

Those both look to be correct observations, fixed for the next release.

James

[acab]

- CPU pin polarity matches main spark polarity - might require re-wiring on MS2 if using JS10

i use js10 for spark A

i need to do something for use js10?

[jsmcortina]

- CPU pin polarity matches main spark polarity - might require re-wiring on MS2 if using JS10

i use js10 for spark A

i need to do something for use js10?

Are you using GM bypass ?

Thought not...

Do not take this one line out of context - IT ONLY APPLIES TO GM BYPASS

James

[acab]

Ohh, sorry.

Can you better make list of new futures ?

[jsmcortina]

Ohh, sorry.

Can you better make list of new futures ?

I edited the first post, hopefully that removes any potential confusion.

James

[Reverant]

Clutch/neutral lockout is hardcoded to use PE0. Any reason why we can't make this configurable? I can help with the code if need be.

[duxthe1]

No problems only praise. I updated to 3.3.2 b3 from an older GSLender code. Holy wow! Not only does it idle better, the AFR is much more stable. Here's the kicker, it runs much better. It feels like it is running in 40 degree cooler weather. Surprisingly it wants more fuel in the boosted part of the map, with absolutely no hard part changes to the setup, just the firmware.

So really I just want to say thanks to the developers, great job. To anybody putting off updating.. DO IT NOW!!!

[slyrye]

No problems only praise. I updated to 3.3.2 b3 from an older GSLender code. Holy wow! Not only does it idle better, the AFR is much more stable. Here's the kicker, it runs much better. It feels like it is running in 40 degree cooler weather. Surprisingly it wants more fuel in the boosted part of the map, with absolutely no hard part changes to the setup, just the firmware.

So really I just want to say thanks to the developers, great job. To anybody putting off updating.. DO IT NOW!!!

please let us have a share of your tune...

[Red_Baron]

When in ITB mode, where do I set the %Baro setpoint and the ITB idle tps% ?

I can't find those settings in the menu

I've found the two curves, the TPS curve and the VE Scaling curve but no %baro setpoint

Cheers
Red Baron

[pigga]

No problems only praise. I updated to 3.3.2 b3 from an older GSLender code. Holy wow! Not only does it idle better, the AFR is much more stable. Here's the kicker, it runs much better.

Hi duxthe1. James encouraged me to upgrade a few days ago. The options of 3.3.2 beta look very promising.
My question: Did you have to do much re-tuning after upgrading from "GSlender's" modded code?
Thanks a lot for sharing your experience(s)!

[slyrye]

I'm having issues with 4G63 CAS setup with this firmware, it's not synching I made composite logs

[jsmcortina]

Are the log and MSQ a matching pair?

The comp log looks like noise filtering was enabled, but the MSQ has it turned off.

What was the last code that worked for you ? I checked the ChangeLog and do not see anything recent that should have altered 4G63 recently.

James

[slyrye]

Are the log and MSQ a matching pair?

The comp log looks like noise filtering was enabled, but the MSQ has it turned off.

What was the last code that worked for you ? I checked the ChangeLog and do not see anything recent that should have altered 4G63 recently.

James

The last firmware that worked for me was Gslender alpha5 but that was on 4G92 mitsu lancer and I believe either CAS has the same trigger pattern. The composite I submitted was for to "log crank/cam" here is the actual log during cranking. Changing the Input capture either "rising or falling" doesn't work as well..

[jsmcortina]

Probably best to run the current stable firmware and start a new topic.

As I said, I'm not aware of any recent 4G63 changes and that is a fairly widely used configuration.

James

[slyrye]

Probably best to run the current stable firmware and start a new topic.

As I said, I'm not aware of any recent 4G63 changes and that is a fairly widely used configuration.

James

Alright... will do thanks James

[slyrye]

I'm afraid it behaves the same as with the Release 3.3.1a
http://www.msextra.com/forums/viewtopic ... 32#p392732

[slyrye]

CONFIRMED!!! that, hiccup sound you're hearing is misfiring!!! it exists mostly on lower tooth CAS 4 or less vanes...! I confirmed this on my 4G63t after modifying the CAS trigger to work as 4/1...!