MS2/Extra pre-3.4 alpha 5 released

[jsmcortina]

To announce the release of "MS2/Extra Pre 3.4 alpha 5" this follows pre-3.4 alpha4

ETA on this 3.4.x code becoming release is 6-12 months.

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-3.4 alpha 4
Bug fixes:
Fix CAN outpc broadcast not sending full dataset if more than 5 groups enabled.
Don't try to broadcast if CAN queue too full.
Fix rotary trailing calculation error (evident near 0deg advance)
3-cyl single-coil - beware of possible side effects
mat_retard actually displays
Workaround for TS 'INVALID' fuel load gauge issue.

Changed features:
Add AEM 3.5 bar, 5.0 bar MAP sensors to known list.
Allow Stepper adapter alt. pins on microsquirt-module.
Fix to oddfire custom angles (accumulate odd_trig_offset)
Allow more pins for Boost output. (UNTESTED)
Kick-start delayed cranking spark.
Kick-start lazy cranking detection.
Basic trigger (next-cyl) doesn't miss a beat on kick-start.
Trigger return doesn't miss a beat on kick-start.
Enable COP watchdog. (Changed sermon.s and flash burners also.)
Rename knock and MAF pins for consistency.

Minor/internal:
Apply the following from 3.3
* Fix missing newline in ini. Fix decimal places on testdwell
* ini - capitalisation and consistency
* - some units standardisation (gives some warnings on old MSQ load)
* - remove GridHeight
* - extend AFR table limits.
Change help file PDF name.

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

Be sure to read the RELEASE-NOTES.txt and README.txt. Especially note that "Not Synced" has been renamed to "Not RPM synced".

The current TunerStudio (2.6.0 or later) is required.

James

[acab]

Allow more pins for Boost output. (UNTESTED)

I can use boost valve on LED14?

[jsmcortina]

With the right driver circuit, that's the idea yes.

James

[acab]

With the right driver circuit, that's the idea yes.

James

Nice!
What about fuel consumption to dashboard?

[jsmcortina]

With the right driver circuit, that's the idea yes.

James

Nice!
What about fuel consumption to dashboard?

You posted that just after I'd released this code. I can take a look another day and send you a test code.

James

[acab]

With the right driver circuit, that's the idea yes.

James

Nice!
What about fuel consumption to dashboard?

You posted that just after I'd released this code. I can take a look another day and send you a test code.

James

No problem. Bu you can show source code of packet before?

[dontz125]

I was a little surprised to see TACHO as a boost pin option for the uSC and uSM. Is a 2222A transistor robust enough to handle both the current and the flyback?

[jsmcortina]

I was a little surprised to see TACHO as a boost pin option for the uSC and uSM. Is a 2222A transistor robust enough to handle both the current and the flyback?

Correct, it isn't. But then the transistor feeding D14 on a V3.0 mainboard isn't either. Nor is the CPU pin JS11.

James

[dontz125]

I was a little surprised to see TACHO as a boost pin option for the uSC and uSM. Is a 2222A transistor robust enough to handle both the current and the flyback?

Correct, it isn't. But then the transistor feeding D14 on a V3.0 mainboard isn't either. Nor is the CPU pin JS11.

James

I don't think those examples are appropriate to the discussion - the MS2 pins aren't selected on whether they can handle the duty, because the end user builds or modifies his own driver circuitry. By that logic, I withdraw my objection to the uSM pin choice, since it also involves a fair bit of DIY.

That said, however, shouldn't the 'ready to roll' uSC only offer those pins that can handle the duty? If a deft end user wants to build an add-on unit he can use the uSM ini, but I would urge the TACHO pin -not- be included in the uSC ini as a boost control option.

[grom_e30]

I just downloaded and had a look through, and for a cased microsquirt for launch control you can choose: flex, spareadc, spareadc2 & remote ports and the same for shift cut but for table switching you can only use flex or remote is there a reason behind this?

[JoseMiguel]

Just to let you know that the 3 cyl single coil works flawlessly

Thanks for the help

[ol boy]

The CAN outmsg settings.... Where do I find how to send a handful of variables out the CAN bus? I'm looking at http://www.msextra.com/doc/general/file ... -03-10.pdf and it shows Group, Group Offset, Total Offset, size and Name. How does this correlate to the 8 outmsg options. All I see is Variable 01 to 16, offset and size.

Thanks Ryan

[jsmcortina]

Outmsg broadcasting is something different.

Look at the CAN realtime data broadcasting instead.

James

[acab]

James, no news about my function with fuel consumption?

[chango de naranjito]

What problem had the rotary trailing before this code? erratic timing?